Options

Solved - NAV2017 - Debugger - Manifest.xml

RemcoRauschRemcoRausch Member Posts: 6
edited 2017-05-04 in NAV Three Tier
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

t5s6j98b0rsw.png

Best Answer

  • Options
    RemcoRauschRemcoRausch Member Posts: 6
    Answer ✓
    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,

    Remco

Answers

  • Options
    RemcoRauschRemcoRausch Member Posts: 6
    Answer ✓
    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,

    Remco
Sign In or Register to comment.