Skip to main content

How to read/write data from Windows Metro Style App

Intr-o aplicatie pentru Windows 8 de tip Windows Metro style app cand avem nevoie sa lucram cu fisiere suntem constransi sa folosim StorageFolder si StorageFile. API este destul de diferit fata de cum ne-am obisnuit pana acuma.
Exista mai multe locatii pe care le putem accesa by default, precum: local folder, roaming folder (direct legat de AD) si temporary folder. Aceste foldere se pot accesa prin urmatoarea modalitate:
StorageFolder localFolderStorage = Windows.Storage.ApplicationData.Current.LocalFolder;
Exista cateva foldere predefinite, pe langa acestea trei pe care le putem accesa folosing clasa statica KnownFolders. Prin intermediul acestei clase avem acces la urmatoarele foldere:
  • Document library
  • Home group
  • Media server devices
  • Music library
  • Pictures library
  • Removable library
  • Video library
Intr-un StorageFolder putem sa accesam fisiere, sa creeam noi foldere si cam toate actiunile pe care le putem face intr-un folder. In exemplul de mai jos creeam un fisier, iar daca acesta atunci facem override.
StorageFolder storageFolder = KnownFolders.HomeGroup;
StorageFile storageFile = storageFolder.CreateFileAsync("Foo.txt", CreationCollisionOption.ReplaceExisting);
In momentul de fata API care il avem disponibil nu ne permite sa verificam daca un fisier sau un folder exista. In cazul in care accesam un fisier care nu exista primim o eroare de tipul FileNotFoundException. O solutie la aceasta problema este sa ne definim un extension method care sa verifice ErrorCode returnat de apelul metodei noastre ( NOTA: tot API-ul care manipuleaza fisiere este async).
var errorCode =storageFolder.GetFileAsync("Foo.txt").ErrorCode
bool fileExist = errorCode != null
        && errorCode.GetType() != typeof(FileNotFoundException);
Operatiile de read si write sunt putin diferite fata de cum ne-am obisnuit noi. Cand deschidem un fisier, obtinem un IRandomAccessStream prin intermediul caruia putem sa scriem sau sa citim date.
using( IRandomAccessStream rs = await storageFile.OpenAsync(FileAccessRead.ReadWrite))
{
    using( DataWriter dw = new DataWriter(rs))
{
    dw.WriteString("FooContent");
    await dw.StoreAsync();
    await dw.FlushAsync();
}
rs.Seek(0);
using( DataReader dr = new DataReader(rs))
{
    string result = dr.ReadString(8);
}
}
Trebuie avut grija la metodele await si cum le manipulam. In rest, odata ce ne-am dat seama cum functioneaza totul este usor de folosit. Din pacate nu tot API-ul cu care ne-am obisnuit noi pentru acces la fisiere este suportat.

Comments

  1. Sau altfel spus, un Windows Phone cu ecran mai mare.. :)
    Si ca si acolo (sau ca la Android si iPhone), primul lucru care lumea il va cauta va fi cum sa scape de walled garden, dovada ca cele mai interesante aplicatii pentru Windows Phone sunt cele sideloaded ..

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP