From the Microsoft Dynamics AX Blogs: AX 2012 .NET Assembly Deployment; Printer Queues; IL Compile; Grants as a Funding Option

AX 2012 .NET Assembly Deployment: Joris de Gruyter favors deploying the assemblies in AX 2012 over those of AX 2009, as his Dynamics AX Musings blog indicated. He explained AX 2012 improved assembly deployment and referencing, especially for clients. He added, "The assemblies don't need to be copied to the client/bin folder."

He warned users to watch out for,

The development manuals for AX 2012 INCORRECTLY state that the assembly automatically gets downloaded by the client to the client bin folder. This is incorrect. The assemblies get downloaded to %USERPROFILE%\AppData\Local\Microsoft\Dynamics AX\VSAssemblies . The %USERPROFILE% by default on Windows 7 should be C:\Users\username so if your user name is DAXMUSINGS, the assemblies will be in C:\Users\DAXMUSINGS\AppData\Local\Microsoft\Dynamics AX\VSAssemblies . Make a correction in your 2012 development manual!

Querying printer queues from X++: Palle Agermark gave printing tips on his self-titled AX blog. According to Agermark, there is a need to print an X++ report and attached files, such as PDF or Word documents, in one set for clients. He said, "Luckily we can use the .NET library System Printing to query the queue and in particular we can call the Number of Jobs to figure out if the attached documents have been printed."

He also offers a few codes for querying the printer queues, adding what he would do differently in AX 2012.

IL Compile and some things to understand for AX 2012: On his Dynamics AX blog, Brandon George detailed more AX 2012 insights in ...