Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Keep Components Up To Date
Message
From
18/08/2009 09:06:22
 
 
To
18/08/2009 08:14:36
Timothy Bryan
Sharpline Consultants
Conroe, Texas, United States
General information
Forum:
ASP.NET
Category:
Other
Miscellaneous
Thread ID:
01418468
Message ID:
01418634
Views:
46
>>
>>IIRC, ff you choose 'Build' then only projects that have changed are rebuilt ('Rebuild' recompiles them all). And, of course, it's easy to set up a configuration that suppresses the build of specific applications (though there's not much point in this case since it defeats the object). But I also prefer keeping the 'control' project out of the solution - mainly to remove the temptation to start adding functionality that's only relevant to the projects that reference it in the current solution :-{
>
>I also like to keep my used projects out of my solution for the reasons you said. I wonder now about when the dll is actually copied. If I have a reference to the dll in the folder where the control is and "Copy Local" set to true; what happens if I rebuild the control project and then later come to the main solution and rebuild it. Does it pick up the new version of the dll? I always assumed it did, but now have doubts. I guess I could test that easy enough.

Hi,
AFAIK, the current version gets copied across during a build.
Previous
Reply
Map
View

Click here to load this message in the networking platform