Skip to main content

Fuslogvw.exe - assembly binding logger

How many time did you had problems with your references of a project in .NET? Not very often but when this occurs you can spend a lot of hours trying to find what is the problem. Invalid version of assembly, incorrect path to your assembly can cause these problems.
Errors like the following can have the same source:

  • Could not load file or assembly 'xxx, Version=yyyy, Culture=neutral, PublicKeyToken=zzz' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
  • This assembly is protected by an unregistered version …

In these cases a great tool can be used to see the loading stack of each assembly. The name of the tool is Assembly Binding Log Viewer (Fuslogvw.exe). It is preinstalled if you have Visual Studio already installed.
This tool will log all the assembly bindings from all the processes that are running on the given computer. Based on this information we can see the exact problem of the binding, the path from where the assembly is loading and much more.
You can start the program using “fuslogvw.exe” command from VS command prompt. Don’t forget to run it as an Administrator.
You should know that all the logs are written in Internet Explorer temporary file folder. Because of this if the temporary folder of the IE is corrupt that you may have problem running this application. In the case you don’t see any kind of information, that you should clear the temporary folder of IE.
Also, don’t forget to click on the “Refresh” button. The UI is not automatically updated when new logs are available.
In the end, for a developer this tool can be very useful and you should try it.


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…