Best Practices for Class Declarations [AX 2012]
Updated: December 6, 2011
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
|
Property |
Rules |
|---|---|
|
Name |
Prefix: Module short name, for example InventUpdate. Infix: Logical description of action performed or type of contents, for example InventUpdate. Follow the general Naming Conventions. Avoid naming classes that are the basis for a subsystem hierarchy with a Base suffix if the class is intended for use in public APIs. This practice follows the design guidelines for the .NET Framework. For more information, see Base Classes for Implementing Abstractions.
If you try to create a class with a name that has already been used for a class in the previous version of Microsoft Dynamics AX, you will get an error. |
Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. Get your copy at the MS Press Store.
Tip