DEV environment for both NAV 2009 and NAV 2013

alex9

What is the best practice regarding installing NAV 2009 and NAV 2013 versions in the same environment, for upgrade and development purposes?

Does it make sense to install everything (clients and mid-tier services) on the same box? I think, it should not be any conflicts for clients, or…?

And what about mid-tiers? Do we need separate machines to run NAV2009 and NAV2013 servers?

ara3n

I use virtualbox.

kine

It is better to separate them. E.g. just because DynamicsNAV protocol is used with both clients and could be hard to open correct version of NAV through hyperlink.

deV.ch

We have all on Clients the same machine (of course middle tier and database seperated), the only thing is as kine said the URI "DynamicsNAV:", this only works for the latest installed RTC Client by default.
Which means if you need this often for example for running pages from DEV Environment, or Reports, you need to handle it somehow.
Most simple wayi s by using 2 .reg files which register the right client before using the command.
More experienced way is to write a handler for this, or use one of them that are available, for eg. the one done by kine
http://dynamicsuser.net/blogs/kine/archive/2012/05/18/dynamicsnav-protocol-handler.aspx

mdPartnerNL

Do you know which registry key to export and import.

deV.ch

oh sorry forgot to post it:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\DYNAMICSNAV]
@="URL:Navision Protocol"
"URL Protocol"=""

[HKEY_CLASSES_ROOT\DYNAMICSNAV\DefaultIcon]
@="C:\\Program Files (x86)\\Microsoft Dynamics NAV\\60_R2\\RoleTailored Client\\Microsoft.Dynamics.Nav.Client.exe,0"

[HKEY_CLASSES_ROOT\DYNAMICSNAV\Shell]
@=""

[HKEY_CLASSES_ROOT\DYNAMICSNAV\Shell\Open]
@=""

[HKEY_CLASSES_ROOT\DYNAMICSNAV\Shell\Open\Command]
@="C:\\Program Files (x86)\\Microsoft Dynamics NAV\\60_R2\\RoleTailored Client\\Microsoft.Dynamics.Nav.Client.exe \"%1\""

Copy this to a new file, call it somehow with extension ".reg", Change the path according to your installation.