Enabling D365 F&O Extension in Visual Studio for development
Shayan Arshi
Microsoft Dynamics AX 365 F&O | AX 2012 | PowerApps | Azure DevOps| SQL Server | Blogger | Associate Architect at Qatar Free Zone | XSystems LTD
Hello Devs!
This is a very common scenario when it comes to enabling D365 extension within VS, so for that below are list of steps needs to be done to enable extension for development.
Prerequisites:
Visual Studio should be installed before performing below steps.??
Step # 1:
Login to?LCS(Microsoft Dynamics lifecycle services). In the main page after login there is a option of Shared asset library.?
Step # 2:
In the list of sub menus , Select Software deployment package and search for latest Service update.
Step # 3 :
Once you have downloaded it.?Unzip?the folder and search?for?Microsoft.Dynamics.Framework.Tools.Installer?in?ServiceUpdate\DevToolsService\Scripts
Example:
Step # 4 :
Follow the wizard and install?.vsix?file for 2019/2017 or any version to enable D365 extension for F&O.
Note: You should have VS installed before?performing?above?steps.
Finally, once after successful installation you can see extension has been added.
Hope you find this blog helpful!
Technical Analyst at Hitachi Solutions Asia Pacific
5 个月Are you familiar what to put in here
Consultor Funcional y de Desarrollo Power Platform
1 年Hello Shayan,? Thanks for sharing the info. So, I'm new on this and have an error trying to start VS2019 after .vsix execution.? I reviewed the log file and found this: Have you had these types of problems? I restart the VS but it happens again Thanks
Manager Assemblies at ELCEE Group
1 年Thank you Shayan. I tried this with a V10.0.37 Service update and v10.0.38 preview, however VS2022 is not recognized. Do you know anything about support for VS2022 ? It should solve the debugging issues so I am really looking forward to it
Senior Manager IT
1 年This is the msg in the issue log:- Install Error : Microsoft.VisualStudio.ExtensionManager.MissingReferencesException: This extension cannot be installed because the following references are missing: -TestWindow.Microsoft.0771d463-d74d-4e95-aac2-39d3c7ec1f97 (Test Explorer Window)