Hi Bill,
From the link below, you can see that Rebuild Solution will "clean" the
solution first, and then build all project files and components.
"Cleaning" a solution or project deletes any intermediate and output files,
leaving only the project and component files, from which new instances of
the intermediate and output files can then be built.
So I think rebuild solution will indeed do as you want.
http://msdn.microsoft.com/library/de...us/vsintro7/ht
ml/vxtskprepareandmanagebuilds.asp
If you still have this problem, can you show me the steps to reproduce this
problem?
For your dll reference problem, VS.net will copy the project "directly"
referred class's dll into its output directory.
For exmaple, If A refers B project(which generates dll B), while B also
refers C project(which also generates dll C). Then when compile project B,
it will copy dll C to its output directory. But when you compile project A,
it only copies dll B not copy dll C to its output directory.(Because dll C
is not directly referred)
Hope this helps,
Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! -
www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--------------------
| From: "Bill Burris" <wb*****@ualberta.ca>
| Subject: Visual Studio bug / limitation
| Date: Fri, 14 Nov 2003 14:45:00 -0700
| Lines: 31
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <uF*************@TK2MSFTNGP10.phx.gbl>
| Newsgroups: microsoft.public.dotnet.languages.csharp
| NNTP-Posting-Host: kzin.phys.ualberta.ca 129.128.162.60
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP10.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.languages.csharp:199468
| X-Tomcat-NG: microsoft.public.dotnet.languages.csharp
|
| When compiling my solution which contains 15 projects (2 Window Apps, 2
| Services, 11 class libraries, C#, MC++, & C++), I was receiving warnings
| about symbols defined in multiple places. Selecting Rebuild Solution did
| not make the problem go away. After selecting Clean Solution, followed by
| Rebuild Solution, the problem went away.
|
| I had always assumed that rebuild meant starting over, recompiling all
code,
| and linking with the recompiled code. It appears that this is not the
case
| with Visual Studio .NET 2003.
|
| It looks like the rebuild process doesn't always bother obtaining the
latest
| versions of dlls, if one already exists in the working directory. If
Class
| A references Class C, B also references C, and D references both A & B,
| Visual Studio sometimes ends up with 2 different versions of class C when
| building D.
|
| Hopefully the VS team at Microsoft will take a close look at how the build
| and rebuild process copies dlls from one project to another, to prevent
this
| mixing of old and new versions of dlls in the same assembly.
|
| In the bad old days, I would build all my C++ code into one big exe. .NET
| has inspired me to split my code up into many small library dlls which I
use
| in more then one application. I am developing the libraries at the same
| time as the applications which use them, so I need to re-compile several
| times a day. Sometimes I waste a lot of time banging my head on the
monitor
| wondering what is causing all the warnings and errors, in code that
| previously compiled without problems.
|
| Bill
|
|
|