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

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