Dave’s role in the company is to manage the Support Desk and resolve customer issues along with Martin and Tommy. Dave is also our hardware specialist, looking after and maintaining our internal infrastructure, including our servers and network.
Installing Many Builds of NAV Web Client on a Server
How to install multiple builds, hotfixes or cumulative updates of the NAV web client on a single server
We have customers running many different builds of NAV and of those many of them use the web client. It can be difficult to test development in the web client as while it is easy to create a middle tier using a different build on the same server (I use 2.2 in Gedas's blog here), doing the same thing with the web client is not well documented. However after some research we’ve found it can be done.
The IIS site that NAV creates when you run New-NAVWebServerInstance points at a folder in inetpub, C:\inetpub\wwwroot\DynamicsNAV90 in the example below:
This folder contains what looks like a shortcut, but is actually a symbolic link or junction. When you open it, unlike a shortcut which would just opens the target, a symbolic link looks like you have just opened a folder in C:\inetpub\wwwroot\DynamicsNAV90, but it is actually showing the files in C:\Program Files\Microsoft Dynamics NAV\90\Web Client.
To make the web client use a different build of NAV you need to redirect this symbolic link. This can be done most easily using junction.exe from sysinternals. The whole process of creating the new web client site is as follows:
- Copy “C:\Program Files\Microsoft Dynamics NAV\90\Web Client” and rename it. I’ve called it “C:\Program Files\Microsoft Dynamics NAV\90\Web Client - CU2”.
- Copy the WEB CLIENT folder from the hotfix directories over C:\Program Files\Microsoft Dynamics NAV\90\Web Client - CU2, replacing the files in the destination:
3. Create a new web client instance using the NAV Administration Shell eg “New-NAVWebServerInstance -Server localhost -ServerInstance DynamicsNAV90CU2Test -WebServerInstance CU2Test”
4. Delete the existing junction using “junction.exe -d C:\inetpub\wwwroot\CU2Test\WebClient”
5. Create the new junction pointing at C:\Program Files\Microsoft Dynamics NAV\90\Web Client - CU2 by running C:\temp>junction.exe C:\inetpub\wwwroot\CU2Test\WebClient "C:\Program Files\Microsoft Dynamics NAV\90\Web Client - CU2"
I find their approach to our relationship very professional whilst being refreshingly realistic. We now consider them to be part of our teamLee Crowhurst, Technical Director