Microsoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.
The series index for this series of posts is here and will automatically update as posts go live.
Before Microsoft Dynamics GP 2018 RTM, or any of the related additional products, can be installed there is one prerequisite which cannot be handled by the installer process. This is the .NET Framework 3.5 feature which is installed using the Add Roles and Features Wizard available via Server Manager on Windows Server or using Turn Windows features on or off accessible via Program and Features on Windows.
If the PC or server you’re planning to install Microsoft Dynamics GP 2018 RTM onto has an Internet connection, then the .NET can be installed simply by using the wizard. However, if, for whatever reason, you don’t have an Internet connection available, the install process isn’t quite that smooth.
On both server and PC you can do an offline install and I have blogged about this previously:
- Offline install on Windows.
- Offline install on Windows Server.
Both of the above posts were for previous versions of Windows, but both are still relevant for the later versions.
In 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.
In the last post I took a look at how to install the .NET Framework 3.5 while the server is not connected to the Internet. At the same time I installed the server I was also installing a Windows 8 client as well and needed to install the .NET Framework 3.5 on it as well. Being client software I expected the process to work, if not better than, then the same as the one on Windows Server 2012.
Continue reading “Offline Install Of dotNET 3.5 On Windows 8”
I recently encountered a problem trying to install the .NET Framework 3.5 in a virtual machine on my test server which is not connected to the Internet (I wish it was but I am currently renting and don’t have a broadband connection). I am used to dealing with Windows Server 2008 R2 where the install just happens, but in Windows Server 2012 the Add roles and features wants to download the install files from the Internet.
In this post I’m going to do a step by step guide to installing the .NET Framework 3.5 on Server 2012 when there is no Internet connection available; many to serve as a reminder to me next time I try to do this.
The first step is to open Server Manager and click on Add roles and features;
Continue reading “Offline Install Of dotNET 3.5 On Windows Server 2012”