Failed to scan .NET information for assembly

Article:TECH14048  |  Created: 2006-05-24  |  Updated: 2007-04-17  |  Article URL http://www.symantec.com/docs/TECH14048
Article Type
Technical Solution


Problem



Failed to scan .NET information for assembly.

.NET 1.1 is installed and the assembly was added from a local drive.


Environment



Wise for Windows Installer 6.2
Development operating system: Windows XP
Target operating system: Windows XP

Cause



The problem is the version attribute of the assembly itself which is 1.0.5000.0 (even though the file version number stamped on the .dll and viewed in the Properties of the file is 1.1.4432). This can be seen by either looking at the file in C:\Windows\Assembly or by adding system.dll from a local system drive to a .wso application project.

What was found was that the error could only be generated if the file (system.dll) was sourced from a mapped or UNC drive. If the original source of the file is a local hard drive, the error is not received. Further, the error is only seen if the internal attribute version is less than 1.1.4432. The error could not be reproduced when testing against one of our Altiris assembly files with a version attribute of 6.0.2074.

Solution



When the problem is that the version attribute of the assembly itself is 1.0.5000.0, even though the file version number stamped on the .dll and viewed in the Properties of the file is 1.1.4432, then the workaround is to have them located in a local system drive at design and compile time.

Legacy ID



22926


Article URL http://www.symantec.com/docs/TECH14048


Terms of use for this information are found in Legal Notices