Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Nav Client Path
AntHillMob
Member Posts: 79
I have an add-in that is quite complex and requires a number of external files. The name of the first is passed to the add-in as a parameter and other files are determined relatative to the path of the first. This may sound unecessarily complex but this is to allow changes to be made without amending the code of the add-in.
All works well if I put the files in a shared directory on the server and store the path to this in a configuration table. This is messy and all clients will need access rights to the shared directory.
The other two ideas I had were to put the files in a directory under the NAV client installation directory. This would work (with the limitation of having to copy the files to each client which is not ideal) but to do this I need to be able to retrieve the Dynamics NAV installation path. APPLICATIONPATH exists but this returns the path to the middle tier installation dircetory which is of no help in the case. So question 1 is is there an equivalent to return the local client installation path?
The other option was to copy the files under a new directory under the service tier directory and use the download function. The problem with this approach is the need to then use an automation object to rename and move the files. This shoudl work but I'm uncomfortable that this may be prone to error.
Any suggestions greatly welcomed.
All works well if I put the files in a shared directory on the server and store the path to this in a configuration table. This is messy and all clients will need access rights to the shared directory.
The other two ideas I had were to put the files in a directory under the NAV client installation directory. This would work (with the limitation of having to copy the files to each client which is not ideal) but to do this I need to be able to retrieve the Dynamics NAV installation path. APPLICATIONPATH exists but this returns the path to the middle tier installation dircetory which is of no help in the case. So question 1 is is there an equivalent to return the local client installation path?
The other option was to copy the files under a new directory under the service tier directory and use the download function. The problem with this approach is the need to then use an automation object to rename and move the files. This shoudl work but I'm uncomfortable that this may be prone to error.
Any suggestions greatly welcomed.
0
Answers
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\fin.exe
RTC is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Microsoft.Dynamics.Nav.Client.exe
subkey "Path" gets you the path without the filename
Thanks for the suggestion.