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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users. This information might be useful in the future when we need to decide where we want to keep and manage our users. Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

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.51 EF 6.0.2 VS2013 It see

Cloud as a Story - Vunvulea Radu

Search This Blog