Install .Net 3.5 offline

Issue: One cannot install SQL Server required for Dynamics AX without .Net 3.5 on a server with limited internet access

Description: One of the obvious requirements for installing Microsoft Dynamics AX is SQL Server which in turn requires the .Net Framework 3.5 to be installed as one of Windows features. However both the Windows feature installer as well as the download versions of .Net Framework 3.5 require an active intenet connection to Window Update servers even if you have the Windows install files. If you do not have this connection due to some reason like a corporate proxy etc installation can be big problematic.

There is hope though. One can force the installation from the Windows disk using the following technique.

1. Insert your Windows installation disk into your computer or mount the disk image.
2. Open a command window running with Administrative privileges
3. Enter the following command: “Dism.exe /online /enable-feature /featurename:NetFX3 /All /Source:E:\sources\sxs /LimitAccess” replacing “E:\” with the path or drive of your windows install disk
4. Press enter and .Net 3.5 will install.

Many thanks to Reza Faisal for saving us many hours with your article on this, it has saved myself and my colleagues much frustration. View the article here:


10. My checklist for debugging X++ code

As part of my series on “Things new X++ Developers Should know”. I have been writing a few basic howtos and checklists for new X++ Developers. These are really meant to be simple step by step guides to get new developers more productive by exposing the little secrets of the AX development that sometimes take years before discovering.

Today’s post is a checklist of things you need to have in place to ensure that you can debug X++ code.

  1. Enable debugging for your user. In an AX development window click on the tools menu item, then click options. Click on the development fast tab. Under debug mode set the option to “When Breakpoint”Enable_AX_Debugging
  2. Ensure your user is part of the local “Microsoft Dynamics AX Debugging Users” user group. On the machine which you are running the debugger on Edit your users and groups.
    Expand the “Groups” section and double click on “Microsoft Dynamics AX Debugging Users”. Click “Add” and enter your domain name and click ok.
    2015-05-25_1546You will need to restart your user session by logging off and back on again
  3. Ensure the server is enabled for debugging (needed for serverside code). Open up the Microsoft Dynamics AX Server configuration console from Windows administrative tools. On the “Application Object Server” tab enable “Enable breakpoints to debug X++ code running on this server” and “Enable global breakpoints”
    Enable server breakpoints
  4. Enable client debugging options (optional/advanced for business connector debugging). In the Microsoft Dynamics Client configuration console in Windows administrative tools enable the following: “Enable user breakpoints to debug code in the Business Connector and Enable global breakpoints to debug code running in the Business Connector or client.
  5. Ensure the debugger is installed on the client machine. Run the Microsoft Dynamics AX installer and ensure the “Debugger” (found under development tools is installed)
  6. If your code is running in CIL:  You can either follow the steps listed on MSDN or for simple debugging (i.e. logic errors) set your user to not run business logic in CIL via your user options form:
  7. Finally and most obviously you need to create breakpoints. You can do this in three ways.
    1. Navigate to the line of code that you want to debug. Press F9
    2. Navigate to the line of code and press the “Red circle” on your toolbar.2015-05-26_1502
    3. Finally you can physically type “debug” in your code to create a breakpoint. However this will enable it for all users in the system, not just for yourself.

I hope this checklist will help somebody stuggling with their debugging in AX. Please let me know if there are additional tips for debugging that this list may be missing.

For some additional details on debugging see MSDN: