Failed Command Line Build

[Matt]

I have a large solution with approx 20 individual projects. This
compiles fine via the UI, but fails when compiling using devenv.exe
via the command line - this happens with visual studio .net 2002 and
2003 on several machines. The error is:

"Runtime Error R6025 - pure virtual function call" in a dialog box
headed "Microsoft Visual C++ Runtime Library". I am trying to compile
a C# solution.

Any help/suggestions?

 

[William Stacey [MVP]]

Have you tried it with just csc.exe instead of devenv? Create a cmd file
(like a build script) that includes all the references and outputs, etc.

 

[mikeb]

I have a large solution with approx 20 individual projects. This
compiles fine via the UI, but fails when compiling using devenv.exe
via the command line - this happens with visual studio .net 2002 and
2003 on several machines. The error is:

"Runtime Error R6025 - pure virtual function call" in a dialog box
headed "Microsoft Visual C++ Runtime Library". I am trying to compile
a C# solution.

Any help/suggestions?

Try breaking the solution into several solutions with fewer projects in
each. I have experienced problems in VS 2002 with solutions containing
more than 15 projects (I think that's the number) crashing a devenv
command line build.

I don't recall seeing the same message as you, and I don't know whether
my problem exists in VS 2003, but it still might be worth a shot for you.

 

[Guest]

Thanks for the two suggestions, I had thought of those but

1) Splitting the solution into smaller, sperate solutions defeats the point of having an enterprise-size development tool, and is working around the problem as oppose to it being a fix

2) Compiling the several hundred csharp files with all their references it truly unmanageable

Thanks for the suggestions, but any other ideas?

 

[mikeb]

Thanks for the two suggestions, I had thought of those but:

1) Splitting the solution into smaller, sperate solutions defeats the point of having an enterprise-size development tool, and is working around the problem as oppose to it being a fix.

Agreed.

2) Compiling the several hundred csharp files with all their references it truly unmanageable.

Thanks for the suggestions, but any other ideas?

You can open a support incident with MS - they may have some sort of
hotfix or a better workaround (I really don't know).

You might want to evaluate "NAnt" to perform your builds. I don't have
experience with the tools, but it seems to get pretty good word of
mouth. I believe that there's a NAnt add-on that can drive builds from
VS.NET .sln and .*proj files, so the automated build process can be
driven from the same files that developers use to perform interactive
IDE builds.

Even though it's pre-release, It might also be worth looking at MSBuild
which is the tool being used in Whidbey. It appears to use many of the
ideas from Ant/NAnt.

 

[William Stacey [MVP]]

The references will not be the problem. You can use a response file and
include all your references in one file. IIRC references don't really cost
anything/much so you can have more then you need. You can even use things
like *.cs so you don't need to specify seperate c# files. You may need to
play a little to get this working perfect for you, but I would create a
buildX.bat file that included any pre/post build stuff and the call to
csc.exe in the middle. As I see it, if devenv (devenv.com is console,
devenv.exe is gui) is not working for you for command line builds then you
have two options, keep building using the gui or do something like I have
shown here. HTH.

--
William Stacey, MS MVP

Thanks for the two suggestions, I had thought of those but:

1) Splitting the solution into smaller, sperate solutions defeats the

point of having an enterprise-size development tool, and is working around
the problem as oppose to it being a fix.