Re: error CS0016: Could not write to output file - build problems - vs.net
From: Quinn Wilson (Quinn.Wilson_at_nygard.com)
Date: 05/27/04
- Previous message: Jeff Mason: "VB Form forgets it is one"
- In reply to: Quinn Wilson: "error CS0016: Could not write to output file - build problems - vs.net"
- Next in thread: Francisco J Lopez: "Re: error CS0016: Could not write to output file - build problems - vs.net"
- Reply: Francisco J Lopez: "Re: error CS0016: Could not write to output file - build problems - vs.net"
- Reply: Dan: "Re: error CS0016: Could not write to output file - build problems - vs.net"
- Messages sorted by: [ date ] [ thread ]
Date: 27 May 2004 10:27:51 -0700
anyone?
Quinn.Wilson@nygard.com (Quinn Wilson) wrote in message news:<43724709.0405200857.7b1b086f@posting.google.com>...
> MS please provide a solution to this.
>
> Windows 2000 / Visual Studio 7.0.9466 / .Net Framework v1.1.4322
>
> I have a solution ( based on the MS Commerce Server International
> Retail Site Reference ) which contains 12 projects. (7 VB and 4 C#)
>
> If I open the IDE, click [Build / Rebuild Solution], my compile is
> successfull. If I click [Build / Rebuild Solution] again, the compile
> dies on one of the C# projects.
>
> Performing main compilation...
> error CS0016: Could not write to output file
> 'd:\onlinestore\Components\obj\DebugAll\Microsoft.CommerceServer.Retail2002.Components.dll'
> -- 'The process cannot
> access the file because it is being used by another process. '
>
> and no subsequent compile attempts will succeed. My only solution thus
> far has been to exit the IDE, delete the "obj" directory of the
> offending project, ( Depending on the build order it is not always the
> same but it is always a C# project / never VB. ) rebuild the solution
> from the commandline "devenv /build debugall
> d:\onlinestore\Retail2002.sln"
>
> I have followed the direction in QB313512
> I do not have projects that are compiled to the same output folder. I
> have only project references, and none of the references to these
> projects are marked with "Copy Local" as false. (I should note that
> this wasn't always a problem. I suspect that I reached the 64kb limit
> mentioned in the KB article and began experiencing these issues. )
>
> I have resorted to managing the build process manually using the
> Configuration Manager to enable and disable the projects I'm working
> on, but if I have to make a change to any of the C# projects I am
> forced to reopen the IDE.
>
> If anyone has any suggestions. I am open to anything. If it means
> reworking my solution, that's fine. I would prefer to continue my
> builds within the IDE but this is increasingly more painfull.
>
> Frustrated
- Previous message: Jeff Mason: "VB Form forgets it is one"
- In reply to: Quinn Wilson: "error CS0016: Could not write to output file - build problems - vs.net"
- Next in thread: Francisco J Lopez: "Re: error CS0016: Could not write to output file - build problems - vs.net"
- Reply: Francisco J Lopez: "Re: error CS0016: Could not write to output file - build problems - vs.net"
- Reply: Dan: "Re: error CS0016: Could not write to output file - build problems - vs.net"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|