Skip to main content

One way to persist objects in isolated storage

In unele cazuri avem nevoie sa stocam date in isolated storage. In cazul in care numarul de date pe vrem sa le stocam nu este foarte mare, putem sa le serializam direct si sa le salvam sub forma unui fisier in isolated storage.
In exemplul de mai jos, datele le-am serializat folosind DataContractSerializer. Din aceasta cauta, clasele pe care vrem sa le salvam trebuie sa fie decorate cu atributul DataContract, iar fiecare proprietate pe care dorim sa o salvam trebuie decorata cu atributul DataMember.
[DataContract]
class Foo
{
   [DataMember]
   public string Name { get; set; }
   public int Age {get; set; }
}
In exemplul dat mai sus o sa salvam doar proprietatea Name.
Mai jos puteti sa gasiti o clasa generica care salveaza un obiect dat. In metodele Save si Load as fi putut sa trimit ca si parametru numele la fisier, dar am ales ca numele de fisier sa se genereze pe baza tipului. Se poate si in alte moduri.
public class IsolatedStorageRepository<TItem>
   {
       public void Save(TItem item)
       {
           using (IsolatedStorageFileStream fileStream = IsolatedStorageFile.GetUserStoreForApplication()
                                                           .OpenFile(GetFileName(), FileMode.Create))
           {
               new DataContractSerializer(typeof(TItem))
                       .WriteObject(fileStream, item);
           }
       }
       public TItem Load()
       {
           IsolatedStorageFile storageFile = IsolatedStorageFile.GetUserStoreForApplication();
           if (!storageFile.FileExists(filename))
           {
               return default(TItem);
           }

           using (IsolatedStorageFileStream fileStream = storageFile.OpenFile(GetFileName, FileMode.Open))
           {
               return (TItem)new DataContractSerializer(typeof(TItem)).ReadObject(fileStream);              
           }
       }

       private string GetFileName()
       {
           string typeName = typeof (TItem).ToGenericFullName();
           typeName = typeName.Replace('<', '_');
           typeName = typeName.Replace('>', '_');

           return typeName;
       }
   }
Metoda ToGenericFullName imi returneaza numele unui obiect. Pentru a vedea implementarea acestei clase puteti sa intrati pe link-ul urmator: http://vunvulearadu.blogspot.com/2012/03/how-to-get-friendly-format-for.html
List<Foo> fooList = new List<Foo>();
// populate list
IsolatedStorageRepository repository = new IsolatedStorageRepository<List<Foo>>();
// Save list
repository.Save(fooList);
// Load list
repository.Load();
Solutia se poate implementa in diferite moduri. Aceasta este doar o varianta.
Enjoy!.

Comments

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(...

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.51 EF 6.0.2 VS2013 It see...

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...