VC++ 2005 (Express Beta Edition) Build/Rebuild

[Guest]

I have been obtaining the following error in the output window of the IDE:

1>mt.exe:general error c101008d:Failed to write the updated manifest to the
resource of file "..\debug\test.exe". The process cannot access the file
because it is being used by another process. 1>Project : error PRJ0002 :
Error result 31 returned from 'C:\Program Files\Microsoft Visual Studio
8\VC\bin\mt.exe'. 1>Build log was saved at
"file://c:\VC2005\test\test\Debug\BuildLog.htm"
1>test - 1 error(s), 0 warning(s)
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

This happens when I try to build my solution. It happens randomly - I can't
detect
any particular pattern. It is of course incorrect because the solution is
built and
appears to work fine. Retrying the Build/Rebuild usually solves the problem.

I am using Windows XP Home Edition. This is rather annoying because I can
never be sure when my compilation has errors or not. I would think this needs
to fixed urgently. Another buggy product....

 

[Brian Muth]

I am using Windows XP Home Edition. This is rather annoying because I can
never be sure when my compilation has errors or not. I would think this needs
to fixed urgently. Another buggy product....

Windows XP Home edition is buggy?

Brian

 

[Guest]

No. Please read this within context. The heading refers to VC++ 2005 and the
post refers to a compile issue within VC++ 2005. I think I made it
sufficiently clear. I added my system runs XP Home for clarification of the
problem.

 

[gabe garza]

If you really want to stay "within context" post this to the beta newsgroup
not to the microsoft.public.dotnet.languages.vc newsgroup.
The issue you pointed out, which by the way I've exprienced in Visual Studio
6.0 when compiling C++ programs, has nothing to do this newsgroup.

Search for microsoft.public.vstudiobeta to see all the available beta
newsgroups or even search for beta.
I think microsoft.public.vstudiobeta.visualc.ide might be a better newsgroup
to post this question.

FYI
Think about the question you post, we can help if it doesn't require Visual
Studio source code changes since we don't have access to that code.
If you're having a problem with your code, then we can help out since you
can post your code and others can review and point out or fix a problem.

Use this to report bugs
http://lab.msdn.microsoft.com/productfeedback/

Use this newgroup to help solve issues you're having with your code.

 

[Ioannis Vranos]

FYI
Think about the question you post, we can help if it doesn't require Visual
Studio source code changes since we don't have access to that code.

?

 

[Ioannis Vranos]

I have been obtaining the following error in the output window of the IDE:

1>mt.exe:general error c101008d:Failed to write the updated manifest to the
resource of file "..\debug\test.exe". The process cannot access the file
because it is being used by another process. 1>Project : error PRJ0002 :
Error result 31 returned from 'C:\Program Files\Microsoft Visual Studio
8\VC\bin\mt.exe'. 1>Build log was saved at
"file://c:\VC2005\test\test\Debug\BuildLog.htm"
1>test - 1 error(s), 0 warning(s)
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

This happens when I try to build my solution. It happens randomly - I can't
detect
any particular pattern. It is of course incorrect because the solution is
built and
appears to work fine. Retrying the Build/Rebuild usually solves the problem.

I am using Windows XP Home Edition. This is rather annoying because I can
never be sure when my compilation has errors or not. I would think this needs
to fixed urgently. Another buggy product....

I am sorry if this makes you to not feel well, however if you do not want to see any bugs
of the VC++ Express Beta 2, then uninstall and do not use it. It is a technology preview
and is not aimed for production code.

Even C++/CLI standard has not been finished yet, and even the current draft hasn't been
implemented completely yet (for example there are still Dispose() definitions in the
Forms). Even .NET 2 is Beta and is not ready yet! Not even SQL Server 2005, which this
release makes use of. SQL Server 2005 is still Beta.


Beta 1 was even worst, it did not even implement String handles properly and crashed.

Once again, *the program is not ready for production code*. So if you want to program for
..NET, the current .NET version is 1.1 and the VS that makes use of it, is VS 2003.


If there is something that you don't understand, please tell.

 

[gabe garza]

Instead of asking a question regarding a program he's writing in C++ with
Visual Studio 2005, he's asking about why he's getting a "file in use"
error. This has to do with Visual Studio 2005, it has nothing to do with a
program that he's writing using Visual Studio 2005.

In order to figure out his problem, the company that has access to the
source code for Visual Studio 2005 has to find that issue. I gave the link
to where he needs to post that bug and mentioned, post questions to
newsgroups where we can help.