How to: Debug X++ Code Running in .NET Business Connector [AX 2012]
This topic has not yet been rated - Rate this topic
Updated: December 16, 2011
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
The Microsoft Dynamics AX development environment enables you to create a .NET-connected application and integrate with Microsoft Dynamics AX. By using .NET Business Connector, you can call X++ methods and access data from a .NET-connected application.
Microsoft Dynamics AX requires that you set breakpoints through the client and the debugger. You need to enable setting break points in the client configuration, and then enable debugging in the .NET Business Connector configuration. For more information about debugger, see Microsoft Dynamics AX Debugger.
There are two modes to debug .NET Business Connector code; interactive and non-interactive. An example of using the interactive mode is integrating Microsoft Excel with Microsoft Dynamics AX. For more information, see How to: Enable the Debugger. An example of using the non-interactive mode is integrating with Enterprise Portal. The following steps provide information to debug X++ code from the .NET-connected application using the non-interactive mode.
Prerequisites
To complete following procedures, you will need:
Microsoft Dynamics AX installed with a developer license file
Client, server and .NET Business Connector on the same computer
The Microsoft Dynamics AX developer is in the Windows admin group
Procedures
Setting the Configuration Settings to Enable Debug
In this section, you will set the configuration settings to enable your X++ code to be debugged from a .NET-connected application. The settings are in the Microsoft Dynamics AX Configuration and Server Configuration windows.
To set the configuration settings
From the Start menu, point to Administrative Tools and then click Microsoft Dynamics AX Configuration.
Click the Manage button and then click Create configuration.
Give the Configuration a name like DebugClientOption and click OK.
Click the Developer tab, select Enable user breakpoints to debug code in the Business Connector or select Enable global breakpoints to debug code running in the Business Connector or client.
Note
Breakpoints are user specific. If you set a breakpoint, only the intended session will break for that breakpoint even if other users execute that code while the breakpoint exists. A global breakpoint will break on any breakpoint for any session running on the machine.
Click the Configuration Target: dropdown and select Business Connector (non-interactive use only).
Click the Manage button and then click Create configuration…
Give the Configuration a name like DebugNonIntOption and click OK.
On the Developer tab, select Enable user breakpoints to debug code running in the Business Connector or select Enable global breakpoints to debug code running in the Business Connector or client.
Click OK to apply changes and close window.
The following steps are only required if you want to debug X++ code that runs on the AOS server, if your code is client only code, for example Business Connector or desktop client, then the following steps are not required. This can be critical in production scenarios because applying the configuration changes require re-starting the server.
To set the configuration settings for code that runs on the AOS server
From the Start menu, point to Administrative Tools and then click Microsoft Dynamics AX Server Configuration.
Click the Manage button and then click Create configuration.
Give the Configuration a name like DebugServerOption and click OK.
On the Application Object Server tab, select Enable breakpoints to debug X++ code running on this server.
Click OK to apply changes and close window. You will be prompted to restart the service.
Enabling Debug in Microsoft Dynamics AX
The next step is to enable debug in the Microsoft Dynamics AX application.
To enable debug in Microsoft Dynamics AX
From the System administration navigation pane, click Common > Users.
Click the user that you want to debug, on the Action Pane, click Options.
In the Options window, click the Development link. In the Debug section, for the Debug mode field, click When Breakpoint.
Click Apply and close the Option and User windows.
Setting Breakpoints in Microsoft Dynamics AX
The following section describes how to set breakpoints in your X++ code.
To set breakpoints in Microsoft Dynamics AX
In the Application Object Tree (AOT), locate the method that you want to debug, right-click the method and click Edit.
Use F9 to include a breakpoint in your X++ code. For more information about breakpoints, see Using Breakpoints.
Invoking the Breakpoints in X++
Now that you have the configuration settings applied and Microsoft Dynamics AX enabled to break when you debug, the final step is to run the .NET-connected application. In this section you will run the application that will cause the breakpoint to occur.
To run the application
Start the .NET-connected application that uses the Microsoft.Dynamics.BusinessConnectorNet assembly. This will load the breakpoints for the current user.
Click Tools > Debugger.
Run the application that will cause the breakpoints to occur. When a breakpoint is encountered, Microsoft Dynamics AX will connect to an existing debugger process and displays the output in the Microsoft Dynamics AX Debugger window. For more information about how to use the Debugger, see Microsoft Dynamics AX Debugger.
Disabling the Debug Settings
When you are finished debugging the X++ code you must disable the debug settings. The following section describes the steps to remove the breakpoints and reset the configuration settings.
To disable the debug settings
In the AOT, locate the method that you set breakpoints in, right-click the method and click Edit.
Use F9 to remove a breakpoint, or use Ctrl+F9 to disable the breakpoint.
Click Tools > Options.
In the Options window, click the Development link. In the Debug section, for the Debug mode field, click No.
Click Apply and close the Option and User windows.
Set the configuration settings back to the previous configurations. From the Start menu, point to Administrative Tools and then click Microsoft Dynamics AX Configuration.
Click the Configuration drop down menu and click the previous or Original configuration.
In the Application Object Server Instance dropdown, select Local client.
Click the Configuration drop down menu and click the previous or Original configuration.
Click OK to apply changes and close window.
From the Start menu, point to Administrative Tools and then click Microsoft Dynamics AX Server Configuration.
Click the Configuration drop down menu and click the previous or Original configuration.
Click OK to apply changes and close window.
Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. get your copy at the MS Press Store
How to: Debug X++ Code Running in .NET Business Connector [AX 2012]的更多相关文章
- Change the environment variable for python code running
python程序运行中改变环境变量: Trying to change the way the loader works for a running Python is very tricky; pr ...
- How to implement long running flows, sagas, business processes or similar
转自:https://blog.bernd-ruecker.com/how-to-implement-long-running-flows-sagas-business-processes-or-si ...
- How to Debug Enterprise Portal Code in Dynamics AX 2009
转载 To set up debugging for pages1. Log into the server that is running the AOS.2. Open the Microsoft ...
- Why we made vorlon.js and how to use it to debug your JavaScript remotely
Vorlon.js is powered by node.JS, socket.io, and late-night coffee. I would like to share with you wh ...
- Build 2017 Revisited: .NET, XAML, Visual Studio
For the next couple months we're going to revisit Build 2017, each post focusing on different aspect ...
- How to debug .NET Core RC2 app with Visual Studio Code on Windows?
Simone Chiaretta (http://codeclimber.net.nz/archive/2016/05/20/How-to-debug-NET-Core-RC2-app-with-Vi ...
- HOW TO REMOTELY DEBUG APPLICATION RUNNING ON TOMCAT FROM WITHIN INTELLIJ IDEA
This post would look into how to tackle and debug issues in scenarios where they only occur in produ ...
- Visual Studio Debug only user code with Just My Code
Debug only user code with Just My Code By default, the debugger skips over non-user code (if you wan ...
- Debug with jdb
原文地址: http://www.javaworld.com/article/2077445/testing-debugging/debug-with-jdb.html Q: How do you u ...
随机推荐
- Linux配置Docker
Centos6.8 1.查看自己的内核 [1].uname [root@host79 ~]# uname -r 2.6.32-642.el6.x86_64 [2].查看CentOS版本信息 CentO ...
- SpringBoot logback 配置文件自定义属性
添加自定义属性类 package com.cus.config; import ch.qos.logback.core.PropertyDefinerBase; import org.springfr ...
- 2016年 实验五 Internet与网络工具的使用
实验五 Internet与网络工具的使用 [实验目的] 本实验目的在于掌握 Telnet.FTP.Email的工作机理,并会在 Internet 上熟练使用相关工具软件. [实验条件] ⑴.个人计算机 ...
- firstBlog
第一篇博客 markdown语法的学习 基本语法 标题与段落 在文字前面加1-6个#号来表示来代表一级标题到六级标题 一级标题 五级标题 列表 对于无序列表,可以使用字符-,+和*作为列表的标记 - ...
- golang 爬取百度贴吧绝地求生页面
package main import ( "github.com/antchfx/htmlquery" "io" "net/http" & ...
- Seaborn中几种作图方式
趋势 sns.pointplot - 点图 ,比折线图好使 sns.lineplot - 折线图最适合显示一段时间内的趋势,多条线可以用来显示多个组中的趋势. 关系 - 可以使用许多不同的图表类型来理 ...
- python 操作conf配置文件方法
参考文章链接:https://blog.csdn.net/qq_23587541/article/details/85019610
- 一口气看完45个寄存器,CPU核心技术大揭秘
序言 前段时间,我连续写了十来篇CPU底层系列技术故事文章,有不少读者私信我让我写一下CPU的寄存器. 寄存器这个太多太复杂,不适合写故事,拖了很久,总算是写完了,这篇文章就来详细聊聊x86/x64架 ...
- 一键开启win10全局utf8,编码问题说拜拜
在windows下开发,开发环境的配置是一个很头大的问题,而编码问题是另一个令人头大的问题,常常出现的中文乱码令人痛不欲生,其原因就在于windows默认的编码并不是现在很普遍的utf8格式,本文就来 ...
- concurrenthasmap
concur'renthashmap java1.7 hashMap在单线程中使用大大提高效率,在多线程的情况下使用hashTable来确保安全.hashTable中使用synchronized关键字 ...