AX7 Packages not visible in Visual Studio on Azure VM

(0) Share

Report

Posted on by DevinS

On a brand new install from LCS into a new Azure VM, the package metadata is not read by Visual Studio correctly. For example, the Application Explorer has no elements under the root nodes (Base Enums, Tables, etc..), and when creating a new model via the Create Model Wizard, in the step to select referenced packages, there are no packages listed at all (blank).

I suspected it was a problem with the folders in which the metadata files were located. Normally this is C:\Packages, but in the Azure VM, they are located at J:\AosService\PackagesLocalDirectory.

Indeed if I copy the contents of J:\AosService\PackagesLocalDirectory into C:\Packages, Visual studio can now see all of the packages and is working as it should.

So, a couple of questions:

Is it safe to continue to use a copy of the files in C:\Packages?
How do I configure Visual Studio to point to the correct folder in J:\AosService\PackagesLocalDirectory?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

Mea_ 60,284 on at

Like (0)

Report

Hi DevinS,

Please refer to https://ax.help.dynamics.com/en/wiki/access-microsoft-dynamics-ax-7-instances-2/

there is a section that describes how to find web.config with all settings.

Was this reply helpful? Yes No
DevinS on at

Like (0)

Report

Web.config Aos.MetadataDirectory key is pointing to J:\AosService\PackagesLocalDirectory correctly. It does not however effect which folder Visual Studio is pointing to.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Hi DevinS,

I think that simply you must run Visual Studio as administrator. (RUN AS ADMINISTRATOR)

Was this reply helpful? Yes No
DevinS on at

Like (0)

Report

This was exactly the issue. Cheers!

Was this reply helpful? Yes No