Resolve imports of conflicting methods in ​.NET script libraries

When importing a .NET class script library into an application, the existing script library will be replaced by the importing library. Conflicting script methods will be detected at this time. Conflict detection is based on name space, class name, method name and parameter declaration.

Note: The version or filename or either .dll have no affect on method conflict detection.

Upon import, conflicting methods will be displayed in the Import Script Function Library dialog box:

In this example, the Math::Int32 Add(Int32, Int32) exists in the current library and contains the same class, method name and parameters as a method in the importing library. It is marked "Replace" in the "Proceeding will" column. Proceeding with the import will replace the entire script library in the application with the importing library.

The Math::132 Subtract(Int32, Int32) is marked "Remove" because the importing library does not contain the subtract method. Script method conflict resolution requires replacing the entire script library, which will also result in the removal of this method if it is not in the importing library.

You cannot cancel the import of an individual method that would remove an existing method from the library, as in the example above. You must proceed with all the conflicting methods or cancel the entire import.

Important: Only .NET class library files can be detected as duplicates at time of import. .aaSLIB library and .wdf script extension files will not import if they conflict with methods in the existing library. In this case, no notification of the conflict will be given.