Skip to main content

Cum sa scriem un xPath cand avem definit si un namespace

Cand vrem sa aplicam un xPath pe un xml ce conține si un namespace lucrurile se complica.
De exemplu daca pornim de la urmatorul xml:
<?xml version="1.0" ?>
<x xmlns="">
Daca dorim sa aplicam un xPath am scrie un cod asemanator cu acesta:
var xmlDoc = new XmlDocument();
var nodes = xmlDoc.SelectNodes(@"/x/y");
Din pacate din cauza ca in xml este definit un namespace, acest lucru nu o sa functioneze. Numarul de noduri returnate va fi mereu 0. Pentru a putea rezvolta aceasta problema trebuie sa adaugam si un namespace, codul rezultat ajungand sa arate in felul urmator:
var xmlDoc = new XmlDocument();
var nameSpaceManager = new XmlNamespaceManager(xmlDoc.NameTable);
var nodes = xmlDoc.SelectNodes(@"/nm:x/nm:y",nameSpaceManager);
Dezavantajul la aceasta solutie este modul in care suntem nevoiti sa scriem xPath-ul. La fiecare nod trebuie sa adaugam "nm". O alta varianta este sa ignoram in totalitate namespace-ul. Acest lucru il putem face cand incarcam documentul.
var xmlDoc = new XmlDocument();
using (XmlTextReader xmlTextReader = new XmlTextReader(path))
xmlTextReader.Namespaces = false;
var nodes = xmlDoc.SelectNodes(@"/x/y");



Popular posts from this blog

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

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.

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…