3ds Max .NET SDK Changes

In 3ds Max 2013 as well as the Subscription Advantage Pack for 3ds Max 2012 there were significant enhancements to the exposure of 3ds Max SDK to .NET. Previously only a small subset of the 3ds Max SDK was exposed to .NET mostly in the ManagedServices.dll. Now nearly all of the global functions and classes in the SDK can be accessed directly from .NET using a new assembly Autodesk.Max.dll found in the application folder.

The Autodesk.Max.dll assembly is automatically generated from the 3ds Max SDK header files, so most of the functions and classes in the 3ds Max SDK are mapped to similarly named constructs in the DLL.

Other changes:

• We recommend that SDK users do not write plug-ins that derive from classes in the Autodesk.Max.Plugins namespace. We support custom user actions and tools or utilities loaded by the .NET assembly loader.
• In 3ds Max 2013 some of the classes for creating custom user actions for CUI (e.g. CuiActionCommandAdapter) have been moved to the UiViewModel.dll assembly.
• We no longer recommend referencing the assemblies in the folder "maxsdk\\bin\\assemblies". Instead you should link against the assemblies found in the root folder of the 3ds Max installation. There you can find all of the assemblies and the corresponding XML documentation files used by the Visual Studio object browser and Intellisense.

For more information, see 3ds Max .NET Assemblies.