Code Comments
Programming Forum and web based access to our favorite programming groups.Hi Tom I assume you mean "... does *not* cause all the dll locking issues ...". Microsoft have confirmed that there is a problem with referencing the dll directly, so it is better to do it the way you are doing it. That said, I haven't noticed any significant delay in building my solutions (I have nine projects in the current solution). In fact, I noticed a marked improvement in compile time when I switched to referencing the projects rather than the dlls. I am using VB.NET, which might make a difference, but I wouldn't have thought so. Perhaps someone else can suggest a reason. Charles "Tom" <tsteinke@gmail.com> wrote in message news:c70875a0.0410080916.aa77bf0@posting.google.com... >I did it from the projects Tab with a local copy. The reason being > this does cause all the dll locking issues that you get when you > reference the dll directly. Also the compiler should know what dlls it > needs to build when changes are made. Otherwise I would have to figure > out what assemblies I had to build manualy corrrect? > > "Charles Law" <blank@nowhere.com> wrote in message > news:<uS4D47RrEHA.4008@TK2MSFTNGP14.phx.gbl>...
Post Follow-up to this messageSo I have like close to 20 projects a mixture of C# and C++. When I hit F5 (not even F7) even if I just built it touches every project it take about 15 seconds. This makes it very difficult to debug software. This means there is a 15 sec turn over even if nothing has changed. "Charles Law" <blank@nowhere.com> wrote in message news:<ejRPvBWrEHA.3848@TK2MSFTNGP14.phx. gbl>... > Hi Tom > > I assume you mean "... does *not* cause all the dll locking issues ...". > Microsoft have confirmed that there is a problem with referencing the dll > directly, so it is better to do it the way you are doing it. > > That said, I haven't noticed any significant delay in building my solution s > (I have nine projects in the current solution). In fact, I noticed a marke d > improvement in compile time when I switched to referencing the projects > rather than the dlls. I am using VB.NET, which might make a difference, bu t > I wouldn't have thought so. Perhaps someone else can suggest a reason. > > Charles > > > "Tom" <tsteinke@gmail.com> wrote in message > news:c70875a0.0410080916.aa77bf0@posting.google.com...
Post Follow-up to this messagePowered by vBulletin
Copyright 2000-2006 Jelsoft Enterprises Limited.