Re: Odd problem with Visual Studio

From: Ken Allen (kendrhyd_at_sympatico.ca)
Date: 04/28/04 

Date: Wed, 28 Apr 2004 07:01:08 -0400

You have mis-understood the problem. It is not the compilation that is
failing, but the transfer of the compiled assembly into the target
directory. I can do this once, but then one of the target files gets
'locked' and I cannot delete it until I exit the IDE!

I have put more detail in another posting.

-Ken

"Frans Bouma [C# MVP]" <perseus.usenetNOSPAM@xs4all.nl> wrote in message
news:xn0dhk37f3eryh001@msnews.microsoft.com...
> Ken Allen wrote:
>
> > I have been developing a suite of assemblies over the past couple of
weeks,
> > and this afternoon somethign started misbehaving.
> >
>
> I assume you have a solution with projects A, B and C, and A references B
> and C. Furthermore B and C reference both some given assembly. What I
> sometimes see in this scenario is that B or C fail to compile due to this
> error. If I first compile B and then C it's ok. You could try to set only
one
> of the references to copy local is true and the other to copy local is
false.
> This might solve the conflict.
>
> Another solution (no pun intended) is the separation of some projects into
a
> separate solution and reference the assemblies from the main solution, not
> the projects.
>
> Frans.
>
> --
> Get LLBLGen Pro, the new O/R mapper for .NET: http://www.llblgen.com
> My .NET Blog: http://weblogs.asp.net/fbouma
> Microsoft C# MVP

Relevant Pages

  • Re: Odd problem with Visual Studio
    ... but then one of the target files gets ... setting which is not possible and compile fails (sometimes you get very weird ... >> I assume you have a solution with projects A, B and C, and A references B ... >> separate solution and reference the assemblies from the main solution, ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Oddity with protected internal and derivation
    ... How did you compile those then? ... It's true that you cannot do circular references in C#, ... you cannot verify much until all the referenced assemblies exist. ... that there's no problem with circular references. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Setting References - What Happens Behind The Scenes?
    ... << Simply it indicate to the compiler to include those assembly at compile ... Studio and I set a reference to two other assemblies: ... each of the two references described above? ... it changes depending of the version/type of project. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Changing References based on compile configuration
    ... I should also have mentioned that all our assembly references are Copy ... so we never lock anything in the assembly libraries while running. ... of the directory that holds the assemblies, ... References based on the Compile configuration? ...
    (microsoft.public.vsnet.general)
  • Re: asp.net assembly best practices question...
    ... > user control assemblies. ... > |> Thanks for your response Jojobar, ... you can find that the image or other resource files in the asp.net ...
    (microsoft.public.dotnet.framework.aspnet)
Loading