Skip to main content

Config class to XML

Nu de mult m-am jucat cu un feature de la Castle Project care permite persistarea fișierelor de configurare sub forma unor fisiere XML. Solutia data de ei este foarte usor de folosit. Daca combinam si cu Ioc oferit de Castle Project atunci metoda de persistare a datelor este aproape perfecta.
Si totusi, exista momente cand nu avem nevoie nevoie de o solutie atat de complexa. Dorim sa salvam intr-un fisiere de configurare doar cateva date pe care apoi sa le putem incarca. Am putea folosii app setings, in care putem pune in format key/value oricate date, dar nu recomand. Avem la indemana o solutie mult mai simpla si care ne ofer acces la date printr-un mecanism mult mai sigur.
Daca ne aducem aminte, exista o clasa numita XmlSerializer, de care uitam ca exista. Cu ajutorul ei putem sa serializam si sa deserializam obiecte.
Iata si o parte din codul care serializeaza si deserializa un obiect intr-un string:
        /// <summary>
/// Serializeaza obiectul data in format xml ca si un string.
/// </summary>
private string SerializeToXMLString<T>(object obj)
where T : class
{
using (MemoryStream mem = new MemoryStream())
{
new XmlSerializer(obj.GetType()).Serialize(mem,obj);
return new ASCIIEncoding().GetString(mem.ToArray());
}
}

/// <summary>
/// Deserializeaza obiectul dintr-un string in format XML intr-un obiect.
/// </summary>
private T DeSerializeFromXMLString<T>(string xmlString)
where T:class
{
byte[] bytes = Encoding.UTF8.GetBytes(xmlString);
using (MemoryStream mem = new MemoryStream(bytes))
{
return (T)new XmlSerializer(typeof (T)).Deserialize(mem);
}
}

Se poate scrie un API pe langa aceasta care sa incarce sau sa salveze obiectul dintr-un fisier dat.

Comments

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 …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…