Databases
StackOverflow2013
Postsdbo
POVS2003 Build on Command Line Throw Errors
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POVS2003 Build on Command Line Throw Errors
    text
    copied!<p>I am trying to do an automated build using the command line for Visual Studio 2003. I have the following codes:</p> <pre><code>call "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\vsvars32.bat" Devenv /rebuild debug /project Project1 "C:\Builds\MyApp\Sample.sln" Devenv /rebuild debug /project Project2 "C:\Builds\MyApp\Sample.sln" Devenv /rebuild debug /project Project3 "C:\Builds\MyApp\Sample.sln" </code></pre> <p>In my script above, I build each project individually (like I saw in a tutorial on the internet). But each time I try to build, it throws me a lot of errors about the Microsoft Namespaces not being found. Below are sample error messages I get on the build:</p> <ul> <li><p>Namespace or type 'Data' for the Imports 'Microsoft.Practices.EnterpriseLibrary.Data' cannot be found.</p></li> <li><p>Namespace or type 'Sql' for the Imports<br> 'Microsoft.Practices.EnterpriseLibrary.Data.Sql' cannot be found.</p></li> <li><p>Namespace or type 'Logging' for the Imports<br> 'Microsoft.Practices.EnterpriseLibrary.Logging' cannot be found.</p></li> <li><p>Satellite assemblies could not be built because the main project<br> output is missing.</p></li> </ul> <p>I have tried another method to build but this time it's the entire solution but still it gives me the same errors.</p> <pre><code>call "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\vsvars32.bat" Devenv C:\Builds\MyApp\Sample.sln /rebuild "Debug" </code></pre> <p>Can somebody please tell me what i'm missing? I have over 50 projects in a single solution and it would really help me big time to create an automated build for this.</p> <p>Thanks a lot! Cheers!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload