FW Editor: What are your plans or objectives in the near future?
Michal Brutvan: I have some planned features for CheckAsm and there is also a new free tool in development.

FW Editor: How and when did you start writing the code for CheckAsm? What inspired you the most?
Michal Brutvan: I was the "Installers Guy" in a company and I needed some tool to verify that all the libraries had been installed correctly. There was no tool at that time so I needed to develop one by myself. I got actually inspired a bit by the well-known Dependency Walker (a.k.a "Depends").

FW Editor: Can you tell us more about the most important features from CheckAsm?
Michal Brutvan: The most important feature is that it can show you what is wrong with your assemblies. You can find what is missing, whether you have all versions correctly referenced, and so on. To verify already deployed software, the Directory Scanner feature is present to quickly check all assemblies in a selected directory.

FW Editor: What is your favorite feature from CheckAsm and why?
Michal Brutvan: It is actually a feature that is not much visible to users: I like the online error reporting the most as I learned really a lot while working on that.

FW Editor: Do you plan to improve or change CheckAsm in any way? If yes, how are you going to do that?
Michal Brutvan: There are always some improvements needed. I am getting some feedback from users and I also have to keep the application up to date with the new .NET Framework versions.

FW Editor: How can you describe CheckAsm in just a few words?
Michal Brutvan: It is an analyzer revealing issues with references between .NET assemblies.

FW Editor: Are you offering customer support for CheckAsm users?
Michal Brutvan: When a user experiences an issue/crash, he is asked to send a bug report. A resolution for her issue is usually available within 2 business days.

FW Editor: Would you like to send a message to CheckAsm users?
Michal Brutvan: I know the application is not ideal, but I hope it helps at least a bit :)