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
- 268 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
[NAV2016] Run object from development envirnoment not reusing opened RTC client anymore in Update 5?
davorp
Member Posts: 17
I just installed NAV 2016 CU5 (build 45243) and now when I run an object directly from the development environment it no longer opens in an RTC client connected to the same instance, but is always starting up a new RTC client, which is rather annoying when doing development.
Did anyone else notice a similar problem?
Here are the fact as I know them:
1. I have multiple NAV installations, 2009/6.0, 2013/7.0, 2013R2/7.1, 2015/8.0 and 2016/9.0 on the computer (Win8.1) and all were working ok last week.
2. Running a Page from NAV 2016 dev. env. was opening in current RTC client while I had 2016 CU2 installed (build 43897)
3. Running a Page from NAV 2016 CU5 dev. env. is not opening in currently opened RTC client anymore
4. Running a Page from NAV 2015 dev. env. (CU12 build 42951) is also not opening in currently opened RTC client anymore (but was working last week)
5. Running a Page from dev. env. is still working as expected from NAV 2013/2013R2 (both are much older builds)
Can someone please confirm if this is still working for them with their installation of NAV 2016 with cumulative update 3 or greater?
Did anyone else notice a similar problem?
Here are the fact as I know them:
1. I have multiple NAV installations, 2009/6.0, 2013/7.0, 2013R2/7.1, 2015/8.0 and 2016/9.0 on the computer (Win8.1) and all were working ok last week.
2. Running a Page from NAV 2016 dev. env. was opening in current RTC client while I had 2016 CU2 installed (build 43897)
3. Running a Page from NAV 2016 CU5 dev. env. is not opening in currently opened RTC client anymore
4. Running a Page from NAV 2015 dev. env. (CU12 build 42951) is also not opening in currently opened RTC client anymore (but was working last week)
5. Running a Page from dev. env. is still working as expected from NAV 2013/2013R2 (both are much older builds)
Can someone please confirm if this is still working for them with their installation of NAV 2016 with cumulative update 3 or greater?
0
Comments
For reusing an already opened RTC client when running an object from development environment you need to have a certain .dll library file registered on the system.
The file in question is Microsoft.Dynamics.Nav.Client.WinForms.dll located in Roletailored Client installation directory.
The file should get registered during installation. However I did an uninstall of NAV 2016 CU2 before installing NAV 2016 CU5 and I suspect this somehow messed things up.
After manually registering .dll using regasm.exe I can now again run objects from development environment in the currently opened RTC client.
I opened command prompt as Admin and executed:
c:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe "c:\Program Files (x86)\Microsoft Dynamics NAV\90\RoleTailored Client\Microsoft.Dynamics.Nav.Client.WinForms.dll" /tlb
This solved the problem for NAV 2015 as well as NAV 2016.
The following link was helpful debugging this issue (although it deals with problems related to side-by-side running of NAV2013/NAV2013R2)
Installing Microsoft Dynamics NAV 2013 R2 side-by-side with Microsoft Dynamics NAV 2013
So, back to business as usual now