Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Solved - NAV2017 - Debugger - Manifest.xml
RemcoRausch
Member Posts: 6
Hi,
We are currently implementing NAV2017 (NAV2013 upgrade) and have installed 10.0.15601.
We installed the latest version because, with the first version, we had a problem using the debugger but unfortunately the latest install has not resolved this.
The problem with the debugger is that the code window shows the following error:
"Resource 'manifest.xml' is missing in the control add-in resource."
Now I know when you write custom libraries you get this file, wrap it all up in a zip file and then import it into the control add-ins within NAV.
With the debugger though I don't have access to this and I presumed this should have all been preinstalled with NAV.
Does anyone know how I can register whatever component is used by the debugger?
Below is a screenshot of the debugger.
Grateful for any help.
Remco
We are currently implementing NAV2017 (NAV2013 upgrade) and have installed 10.0.15601.
We installed the latest version because, with the first version, we had a problem using the debugger but unfortunately the latest install has not resolved this.
The problem with the debugger is that the code window shows the following error:
"Resource 'manifest.xml' is missing in the control add-in resource."
Now I know when you write custom libraries you get this file, wrap it all up in a zip file and then import it into the control add-ins within NAV.
With the debugger though I don't have access to this and I presumed this should have all been preinstalled with NAV.
Does anyone know how I can register whatever component is used by the debugger?
Below is a screenshot of the debugger.
Grateful for any help.
Remco
0
Best Answer
-
RemcoRausch
Member Posts: 6
Hi,
Managed to resolve this by deleting the Microsoft.Dynamics.Nav.Client.CodeViewer addin from the NAV2013 db before doing the upgrade to NAV2017.
Thanks,
Remco0
Answers
Managed to resolve this by deleting the Microsoft.Dynamics.Nav.Client.CodeViewer addin from the NAV2013 db before doing the upgrade to NAV2017.
Thanks,
Remco