topic Re: runtime manifest created but will not open in .NET Maps SDK Questions

runtime manifest created but will not open

MikkelHylden — Fri, 25 Sep 2015 18:27:26 GMT

I have the runtime SDK (Full version, not GIT) installed. I can run the action on my window app project to create the deployment manifest, but cannot open it. I get an error message from Visual Studio 2013 saying "Operation could not be completed. Library not registered"

If I open the manifest manually in a text editor, it just shows the main runtime:

{

"version": "10.2.6",

"suppress": [],

"include": {

"ArcGIS Runtime": true

}

I saw other posts indicating that the registry entries may be in the wrong place, but I looked in the registry and they do appear to be in the WOW location, which was listed as correct.

Any ideas on why this is failing?

Thanks,

Mikkel

Re: runtime manifest created but will not open

nakulmanocha — Fri, 25 Sep 2015 20:40:17 GMT

Hi Mikkel,

I have attached a very simple windows desktop project using 10.2.6 .NET runtime. It also has the manifest file. Can you please trying running this project in VS and opening the manifest file? If you cannot open try reinstalling the runtime .NET.

Re: runtime manifest created but will not open

MikkelHylden — Fri, 25 Sep 2015 20:46:28 GMT

That one opens just fine - I see the expected tree view of checkboxes for components to turn on or off.

I'll have to see what is different between the two projects, but at least initially both are windows applications, and include the same 10.2.6 runtime.

Re: runtime manifest created but will not open

MikkelHylden — Fri, 25 Sep 2015 22:38:14 GMT

Just as a follow up - I couldn't see any significant differences between the projects. I loaded my project in the test app solution, and it worked.

Going back to the solution, the difference appears to be that I have an installer project along side my application to build a setup app to build directories, etc. I unloaded that and then the manifest came up ok.

So while I don't understand why an app in a different project would affect it, that seems to have done the trick. I'll have to reload the installer whenever I'm getting ready to do a release, but I think I can work around the issue.