What's New: Visual Studio Tools for Developers in Microsoft Dynamics AX 2012

Article
11/29/2021

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This page lists the new and enhanced features for Visual Studio Tools available in Microsoft Dynamics AX 2012.

Microsoft Dynamics AX now provides an integrated development experience with Visual Studio. Visual Studio Tools for Microsoft Dynamics AX (Visual Studio Tools) is a set of tools and functionality that support development for Microsoft Dynamics AX in .NET managed code. Visual Studio Tools contains tools and functionality from both the MorphX and Visual Studio development environments.

What is new or changed?

This feature has changed considerably since Microsoft Dynamics AX 2009. In addition to the new features that have been added, support for managed code has been integrated into Microsoft Dynamics AX in various ways.

New features have been added to the tools for modeling business application elements in Visual Studio. You can now add Visual Studio projects to Microsoft Dynamics AX and they are stored in the same model store as X++ code. You can view Visual Studio projects from either the Application Explorer in Visual Studio or the Application Object Tree (AOT) in MorphX. Reporting projects created in Visual Studio are stored in granular and customizable elements in the AOT. Source control is available for application projects from either the AOT or Visual Studio. The following sections describe the components that comprise Visual Studio Tools.

Application Explorer
Managed Code Business Logic
Proxies
Managed Code Event Handlers
Deployment
Cross-Reference Tool Support for Managed Code
Code Upgrade Tools Support for Managed Code

Application Explorer

What can you do?	Microsoft Dynamics AX 2009	Microsoft Dynamics AX 2012	Why is this important?	Where can I find more information?
The Application Explorer displays a view of the AOT within the Visual Studio IDE.	Model View enabled developers to view, create, edit, and delete models in a reporting project.	View, open for edit, and delete code elements in the model store whether they are managed code or X++ elements Edit reports and Enterprise Portal Web controls Add managed code projects to the model store Edit managed projects that have been added to the AOT (model store) View X++ code	Enables you to see all objects in the model store from the Visual Studio IDE.	Application Explorer

Managed Code Business Logic

What can you do?	Microsoft Dynamics AX 2009	Microsoft Dynamics AX 2012	Why is this important?	Where can I find more information?
You can write business logic in .NET languages and manage this code in Microsoft Dynamics AX just as you would with X++ classes.	Feature not available.	You can save .NET class library projects to the model store. You can customize these managed code projects using the various layers. You can build managed code projects in Visual Studio and they are automatically deployed if configured to do so.	Developing code that integrates with Microsoft Dynamics AX is now possible in Visual Studio. The full development and deployment scenario is supported for managed code.	Visual Studio Development for Microsoft Dynamics AX Getting Started with Visual Studio

You can write business logic in .NET languages and manage this code in Microsoft Dynamics AX just as you would with X++ classes.

Feature not available.

You can save .NET class library projects to the model store.
You can customize these managed code projects using the various layers.
You can build managed code projects in Visual Studio and they are automatically deployed if configured to do so.

Developing code that integrates with Microsoft Dynamics AX is now possible in Visual Studio. The full development and deployment scenario is supported for managed code.

Visual Studio Development for Microsoft Dynamics AX

Getting Started with Visual Studio

Proxies

What can you do?	Microsoft Dynamics AX 2009	Microsoft Dynamics AX 2012	Why is this important?	Where can I find more information?
Allows you to add an X++ class or table to your project in Visual Studio so it can be accessed by managed code.	Feature not available.	When you add an X++ class or table to a project by using the Application Explorer, a proxy for that class is created internally by the system. After the proxy is created, that type is then available as a strong type and features like IntelliSense are available.	You can easily add X++ objects to your Visual Studio project and write managed code that accesses those objects.	Visual Studio Development for Microsoft Dynamics AX Walkthrough: Adding an X++ Object to a Visual Studio Project

Allows you to add an X++ class or table to your project in Visual Studio so it can be accessed by managed code.

Feature not available.

When you add an X++ class or table to a project by using the Application Explorer, a proxy for that class is created internally by the system. After the proxy is created, that type is then available as a strong type and features like IntelliSense are available.

You can easily add X++ objects to your Visual Studio project and write managed code that accesses those objects.

Visual Studio Development for Microsoft Dynamics AX

Walkthrough: Adding an X++ Object to a Visual Studio Project

Managed Code Event Handlers

What can you do?	Microsoft Dynamics AX 2009	Microsoft Dynamics AX 2012	Why is this important?	Where can I find more information?
You can create a managed code event handler for an instance method of an X++ class.	Feature not available.	The event handler subscribes to the X++ event and can be called before the method begins or after the method completes. You can handle events raised only by a class in the Classes node in the AOT.	You can now create event handlers in managed code as well as X++. This means you can write .NET code to handle class events.	Walkthrough: Creating an Event Handler in Visual Studio
You can create a managed code event handler for an X++ delegate.	Feature not available.	The event handler subscribes to the X++ delegate, and the code runs when the delegate fires.	You can now create event handlers in managed code as well as X++. This means you can write .NET code to handle delegate events.	Walkthrough: Creating an Event Handler in Visual Studio

Deployment

What can you do?	Microsoft Dynamics AX 2009	Microsoft Dynamics AX 2012	Why is this important?	Where can I find more information?
The deployment functionality enables you to automatically deploy managed assemblies (DLLs) that you create in Visual Studio to Microsoft Dynamics AX.	Feature not available.	Managed code assemblies are automatically deployed to the location that you specify: client, server, Reporting Services or Enterprise Portal. You can specify where the assembly is deployed by setting project properties in Visual Studio. After you deploy an assembly, you can then see the managed code classes via IntelliSense and call the managed code from X++.	Deployment happens automatically to the locations you specify.	Deploying Managed Code

Cross-Reference Tool

What can you do?	Microsoft Dynamics AX 2009	Microsoft Dynamics AX 2012	Why is this important?	Where can I find more information?
The Cross-reference Tool in Microsoft Dynamics AX lets you see the relationships between elements and now supports managed code that that has been added to the model store.	Feature not available.	In order to see cross-references for a Visual Studio project, you must first add the project to the model store by using the Application Explorer. After you add a project to the model store, the project and its cross-reference information are updated every time you build the project.	Managed code is now supported by the Cross-reference Tool in MorphX. This means you can see the same cross-reference information for both X++ and managed code. For example, when you access the Cross-reference Tool from a report, you can see what the report data source.	Cross-References and Visual Studio Projects Walkthrough: Using the Cross-Reference Tool with Visual Studio Projects

The Cross-reference Tool in Microsoft Dynamics AX lets you see the relationships between elements and now supports managed code that that has been added to the model store.

Feature not available.

In order to see cross-references for a Visual Studio project, you must first add the project to the model store by using the Application Explorer. After you add a project to the model store, the project and its cross-reference information are updated every time you build the project.

Managed code is now supported by the Cross-reference Tool in MorphX. This means you can see the same cross-reference information for both X++ and managed code. For example, when you access the Cross-reference Tool from a report, you can see what the report data source.

Cross-References and Visual Studio Projects

Walkthrough: Using the Cross-Reference Tool with Visual Studio Projects

Code Upgrade Tools

What can you do?	Microsoft Dynamics AX 2009	Microsoft Dynamics AX 2012	Why is this important?	Where can I find more information?
Microsoft Dynamics AX supports layer-based customizations for managed code. Therefore, the tools that enable developers to find and resolve conflicts that result from those customizations also support managed code. The code upgrade tools enable developers to detect and resolve conflicts between two versions of Microsoft Dynamics AX.	Feature not available.	The conflict detection and resolution tools enable developers to find conflicts and compare customizations in different layers. These tools are available in the MorphX IDE and include the following: Detect code upgrade conflicts tool - Reports conflicts in both X++ and managed code that has been added to the model store. Compare tool – Enables you to compare both X++ code and managed code in two layers and resolve any conflicts.	The code upgrade tools that are included with Microsoft Dynamics AX support managed code development. Therefore, the same code upgrade process can be used for code whether it originates in MorphX or in Visual Studio. These tools are used to detect and resolve code conflicts when upgrading to a new version of Microsoft Dynamics AX, installing customizations, or installing new modules developed by a VAR or partner.	Upgrade Support for Managed Code

Microsoft Dynamics AX supports layer-based customizations for managed code. Therefore, the tools that enable developers to find and resolve conflicts that result from those customizations also support managed code. The code upgrade tools enable developers to detect and resolve conflicts between two versions of Microsoft Dynamics AX.

Feature not available.

The conflict detection and resolution tools enable developers to find conflicts and compare customizations in different layers. These tools are available in the MorphX IDE and include the following:

Detect code upgrade conflicts tool - Reports conflicts in both X++ and managed code that has been added to the model store.
Compare tool – Enables you to compare both X++ code and managed code in two layers and resolve any conflicts.

The code upgrade tools that are included with Microsoft Dynamics AX support managed code development. Therefore, the same code upgrade process can be used for code whether it originates in MorphX or in Visual Studio.

These tools are used to detect and resolve code conflicts when upgrading to a new version of Microsoft Dynamics AX, installing customizations, or installing new modules developed by a VAR or partner.

Upgrade Support for Managed Code

Share via

What's New: Visual Studio Tools for Developers in Microsoft Dynamics AX 2012

What is new or changed?

Application Explorer

Managed Code Business Logic

Proxies

Managed Code Event Handlers

Deployment

Cross-Reference Tool

Code Upgrade Tools

See also

Additional resources