Skip to main content

Could not load file or assembly or one of its dependencies. An attempt was made to load a program with an incorrect format wcf on iis.

Cat de cunoscuta vi se pare eroarea aceasta? Prima parte din eroare mi s-a parut foarte cunoscuta in prima faza dar totusi e usor enigmatica.
Problema cea mai mare la acest tip de eroare este ca nu ne spune exact care este cauza. Mai jos o sa gasit trei cazuri comune cand aceasta eroare apare
  • Assembly-ul nu poate fi gasit in locatia data. In funcție de setarile proiectului unu sau mai multe assembly-uri nu se gasesc in locațiile specificate.
  • Unu din assembly-uri este compilat pentru o alta arhitectura de procesor. De exemplu incercam sa rulam 3 proiecte care se refera intre ele. Unul din ele este compilat pentru x86, iar restul proiectelor sunt compilate pe o arhitectura de tip x64.
  • Sunt compilate pe versiuni diferite de .NET. Un assembly este compilat pentru .NET 2.0, iar altul pentru .NET 4.0.
Desii toate cazurile au soluții simple, din cauza ca rulam aplicatia din IIS, o parte din erori sunt vagi si apar doar la runtime.
De exemplu daca avem un assembly care contine un serviciu WCF ce refera un assembly compilat pentru o alta arhitectura de procesor nu o sa avem nici o eroare la compilare. Totul o sa fie bine pana cand o sa apelam un operation contract din serviciu. In momentul respectiv o sa ne trezim cu aceasta eroare si nu o sa stim de unde sa o luam.
Voi in ce alte cazuri ati mai avut aceasta eroare?


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…