mibuso.com

DynamicsNAVProtocolHandler v1.0.0.0
Installation: Copy to some folder of your choice, run, activate, close. Try to open some dynamicsnav hyperlink or run page from classic client.
Prerequisities: Microsoft .NET v4.5

Description:
This small app will install itself as dynamicsnav: protocol handler. This protocol is used to run the Microsoft.Dynamics.Nav.Client.exe through hyperlinks. If the hyperlink is triggered by classic client (or development environment for NAV 2013), this app will take the path of the classic client and will try:
1) Find the Microsoft.Dynamics.Nav.Client.exe in same folder. If found, run this clien to handle the URI.
2) Find Microsoft.Dynamics.Nav.Client.exe with same version as the calling finsql.exe in folders and subfolder recuresively, starting from ..\.. (parent of parent) folder from the calling classic client folder. This is based on expecting standard folder structure of installed clients.
3) If the hyperlink was not triggered by finsql.exe, default associated application is used to handle the protocol (the one, which was associated when this app was activated).

Reason:
When you install e.g. NAV 2013 side-by-side with NAV 2009, you can have problems to open e.g. pages from the different clients. Even when you have more builds of same version, you can have this problem, running the correct RTC build from the DevEnv. This app should solve that for you.


Have fun with the NAV!

http://www.mibuso.com/dlinfo.asp?FileID=1443

Discuss this download here.

Newer version is downloadable from my blogs. The version 1.0.1.0 changes:
- Added info bar showing the started client path. Could be disabled in .config file
- Possibility to show dialog box with executed command. Could be enabled in .config file
- Solved some problem when running NAV 2009 RTC when the RTC is already started (the client app crashed).

And additional info: when the handler is activated, NAV "Jump List" will not work on Windows 7/8.

Hello Kine, this sounds really like a great tool, great work!
However is the requirement of .NET framework 4.5 really necesarry? This framework it is still in beta as far as I know.
In my opinion it would be better to compile with a lower framework version if there is no technical requirement to use 4.5.

Of course, it is not necessary. It is just that I used the VS 11 to start the project and now I have problem to switching to 3.5 version of .NET because the references etc. I will try in free time to switch it again (I tried at night, but I reverted back).

Ok, I have find some time and changed the version. There were some issues, but solved in a minute. You can download newer version from my blogs.

Thanks for the fast response, much better this way. We will give it a try.

Hi Kine,

Just tried the 1.0.2.0 version from your blog, but unfortunatly, it does not work. It always gives the error "Same version of RTC was not found". I do use long directorynames, and this client is in C:\Program Files (x86)\Microsoft Dynamics NAV\6_0_32580_0_20120518112742\classic, while the RTC is in C:\Program Files (x86)\Microsoft Dynamics NAV\6_0_32580_0_20120518112742\RoleTailored Client. There are several directories in the C:\Program Files (x86)\Microsoft Dynamics NAV\ with various versions, and I assumed it would be using method 2 from the txtfile to find the correct client. However, it's not working right now... If it would, this could be a great tool...

And are you sure that the clients have SAME BUILD number?

Yes. In this case, they both have build 6.0.32580.0.But also other builds in other directories give the same problem... Could be something with the recursive filefind thingie?

One thing that seems strange: If I start the program to activate or deactivate, I must start it elevated. This isn't done when I try to start the client. Could that be a problem?

I've set ShowMessageBox to True, but it disappears to fast to be able to read anything

The problem for elevation is that it is changing registry. When working just as handler, it is not changing them, only reading, thus no problem with elevation.

Jst now, I am trying to put the project to codeplex site and publish it for everyone. I expect that we will extend it together to create some cool tool for everyone...

https://navprotocolhandler.codeplex.com/

There is the codeplex site for this. The application have slightly different name and versioning from the previous one, which was part of my bigger work.

Is the client exe named "Microsoft.Dynamics.Nav.Client.exe" ? (e.g. may be problem of upper/lower case)...

I think I found the solution to the problem of Poltergeist.
I posted the solution to this issue on codeplex.

Thanks, I have overlooked that. New version released.

DynamicsNAVProtocolHandler v1.1.2.0
Installation: Copy to some folder of your choice, run, activate, close. Try to open some dynamicsnav hyperlink or run page from classic client.
Prerequisities: Microsoft .NET v3.5

Description:
This small app will install itself as dynamicsnav: protocol handler. This protocol is used to run the Microsoft.Dynamics.Nav.Client.exe through hyperlinks. If the hyperlink is triggered by classic client (or development environment for NAV 2013), this app will take the path of the classic client and will try:
1) Find the Microsoft.Dynamics.Nav.Client.exe in same folder. If found, run this clien to handle the URI.
2) Find Microsoft.Dynamics.Nav.Client.exe with same version as the calling finsql.exe in folders and subfolder recuresively, starting from ..\.. (parent of parent) folder from the calling classic client folder. This is based on expecting standard folder structure of installed clients.
3) If the hyperlink was triggered by finsql.exe, default associated application is used to hndle the protocol (the one, which was associated when this app was activated).

Reason:
When you install e.g. NAV 2013 side-by-side with NAV 2009, you can have problems to open e.g. pages from the different clients. Even when you have more builds of same version, you can have this problem, running the correct RTC build from the DevEnv. This app should solve that for you.

http://navprotocolhandler.codeplex.com

Have fun with the NAV!

v1.1.2.0
- Mappings added (mapping between SQL Server and DB and NAV Server and instance)
- refactoring some things inside

v1.1.1.0
- .NET v3.5 used

v1.0.1.0
- Added info bar showing the started client path. Could be disabled in .config file
- Possibility to show dialog box with executed command. Could be enabled in .config file
- Solved some problem when running NAV 2009 RTC when the RTC is already started (the client app crashed).

http://www.mibuso.com/dlinfo.asp?FileID=1443

Discuss this download here.