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.

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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…