The following methods are now obsolete. National Instruments supports these methods but recommends that you update files to reflect these changes to ensure compatibility with future versions of TestStand.

Although you can use the DotNetModule.ClearUnmappedConstructorArgumentValues , DotNetModule.GetConstructorMetadataToken , DotNetModule.GetMetadataToken , DotNetModule.LoadConstructorPrototypeFromMetadataToken , and DotNetModule.LoadPrototypeFromMetadataToken methods, they might not return exactly the same results as in previous versions of TestStand because of the significant changes made to the underlying DotNetModule data structure and architecture of the .NET Adapter in TestStand 2010. Most of the common usages of these methods work as expected. However, if you use these methods to modify or specify a DotNetModule programmatically, you might need to modify the various settings on the DotNetModule in a different order than in previous versions of TestStand to obtain the expected result.

National Instruments recommends specifying the module settings in the following order:

• DotNetModule.SetAssembly
• DotNetModule.ClassName
• DotNetModule.CreateObject
• DotNetModule.SpecifyHostByExpression
• DotNetModule.RemoteHost
• DotNetModule.ClassReference
• DotNetModule.DisposeObject
• DotNetModule.MemberName
• DotNetModule.MemberType
• DotNetModule.MemberFlags
• DotNetModule.LoadConstructorPrototypeFromMetadataToken
• DotNetModule.LoadPrototypeFromMetadataToken
• DotNetModule.ConstructorParameters
• DotNetModule.Parameters

Consider using the current API for specifying .NET code modules by adding DotNetCalls to the DotNetModule.Calls collection and using the DotNetCall interface to specify the members you want to call.