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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…