Registering dotNET DLLs

Microsoft Dynamics GPIn the past when I have needed to manually register DLLs they have been C++ or VB ones which are registered using the regsrver command.

A recent project for a client was done using C# which requires the assembly to be registered using a different command. I am posting this here as a reminder to myself next time I need to do this.

When you register the assembly, you may receive a warning message about registering unsigned assemblies using the /codebase switch which is intended only with signed assemblies. If you trust the origin of the assembly then you can safely register the assembly and ignore the warning.

To register the .NET DLL, open a command prompt and type the following (the highlighted section is the name of the assembly being registered):

%SystemRoot%\Microsoft.NET\Framework\v4.0.30319\regasm.exe reportprinter.dll /codebase

To unregister a .NET DLL type the following:

%SystemRoot%\Microsoft.NET\Framework\v4.0.30319\regasm.exe reportprinter.dll /unregister

The highlighted section is the dll being registered or unregistered.

Error During Build in Visual Studio Tools For Microsoft Dynamics GP

Back in the early years of my career, before I became involved with Microsoft Dynamics GP, I was a trainee developer (admittedly on PICK Databasic) before moving on and learning a little VB6 and then into Microsoft Dynamics GP consultancy.

I’ve kept my hand in enough that I can still do some coding and last weekend, after chatting with a developer in the office who is creating some new screens for GP, I decided to have a little dabble with the Visual Studio Tools for Microsoft Dynamics GP myself. Continue reading