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

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...