When you use the Visual Basic .NET compiler (VBC.exe) to
compile from a command prompt with a response (.rsp) file that references many
assemblies, you may not be able to compile, and you may receive the following
error message (or a similar one):
vbc : Command line
error BC2017 : could not find library
'c:\windows\microsoft.net\framework\v1.0.3705\temporary asp.net
files\vbwebapp\093b8894\b238cf87\assembly\dl\c0d82e1f\043d'
vbc : Fatal
error BC2000 : compiler initialization failed unexpectedly: The filename,
directory name, or volume label syntax is incorrect.
For example,
this problem may occur if you use the following command at a command prompt:
VBC.EXE /@response_file.rsp
NOTE: The
/@ option is not available from the Visual Studio IDE. This option
is available only when you compile from the command prompt. This cannot be
changed programmatically. This problem is more likely to occur with Microsoft
ASP.NET applications because these applications use a command-line compiler.
Back to the top
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Visual
Studio .NET. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
837234 (http://support.microsoft.com/kb/837234/) List of bugs that are fixed in Visual Studio .NET 2002 Service Pack 1
Back to the top
Hotfix information
The English version of this hotfix 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
--------------------------------------------------
04-Apr-2003 06:50 7.0.9687.0 712,704 Vbc.exe
Back to the top
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Visual Studio .NET 2002 Service Pack 1.
Back to the top
Help and Support
