Microsoft KB Archive/840525

= FIX: You receive an &quot;ALINK error AL1022: Error reading embedded resource&quot; error message when you try to build your project in Visual Studio .NET 2002 =

Article ID: 840525

Article Last Modified on 5/15/2006

-

APPLIES TO


 * Microsoft Visual Studio .NET 2002 Professional Edition
 * Microsoft Visual Studio .NET 2002 Enterprise Architect
 * Microsoft Visual Studio .NET 2002 Enterprise Architect
 * Microsoft Visual Studio .NET 2002 Enterprise Developer
 * Microsoft Visual Studio .NET 2002 Enterprise Developer
 * Microsoft Visual Studio .NET 2002 Academic Edition

-





SYMPTOMS
When you try to build your project in Microsoft Visual Studio .NET 2002, you may receive an error message that is similar to the following:

ALINK: error AL1022: Error reading embedded resource ' ' -- The system cannot find the file specified.

Note The project build is unsuccessful.



CAUSE
This problem occurs when the combined path of all the satellite assemblies is larger than 32,000 characters. When Visual Studio .NET 2002 invokes the Assembly Linker (Al.exe), the command-line command that is passed is truncated to the 32,000 character limit. Therefore, the path of the satellite assembly is not complete and the Assembly Linker cannot read the resource.



Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio .NET 2002 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
No prerequisites are required.

Restart requirement
You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The hotfix version of this English has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version     Size       File name ---  17-Apr-2004  16:00  7.0.9777.0    917,504  Csproj.dll 17-Apr-2004 07:27  7.0.9777.0    176,128  Csprojui.dll 17-Apr-2004 15:39  7.0.9777.0    311,296  Dirprj.dll 17-Apr-2004 15:54  7.0.9777.0  1,400,832  Msvbprj.dll 17-Apr-2004 07:26  7.0.9777.0    180,224  Msvbprjui.dll 17-Apr-2004 09:16  7.0.9777.0    253,952  Visualstudioteamcore.dll 17-Apr-2004 09:14  7.0.9777.0    888,832  Vsavb7dt.dll 17-Apr-2004 09:14  7.0.9777.0    999,424  Vsavb7rt.dll 17-Apr-2004 09:14  7.0.9777.0    794,624  Vsavbproj.dll 17-Apr-2004 15:58  7.0.9777.0  2,981,888  Vsscc.dll



WORKAROUND
To work around this problem, save your project in a shorter path. An example would be to save your Visual Studio .NET project in the C:\VSP\WinApp1 folder instead of the C:\Visual Studio Projects\WindowsApplication1 folder.

Note This workaround may only be a temporary solution. As you add more assemblies to your project, you may reach the 32,000-character limit again and you may receive the error message that is mentioned in the &quot;Symptoms&quot; section.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

