hi.
in vs2003, it was possible to have a build configuration where _no_ project was selected. that way, one could simply build a single project inside the solution using the build command.
when the solution was run, however, the ide would still fetch all current versions of all assemblies and copy them to the main projects runtime directory before launching the debugger. thus, it was possible to do a local build of an assembly and still test that assembly using the other code.
vs2005 no longer fetches all current version of all assemblies: in order to do a local change and test that change, its necessary to do a complete build. in my case, this takes about 3-5 minutes. _each_ time i hit 'debug'. this is not exactly very productive. is there any way to persuade the ide to copy the latest versions of all assemblies to the run directory do i really need to build the complete solution each time
WM_THX
thomas woelfer
http://www.die.de/blog
build / debug functionality missing?
Hot Topic
- How to determine if a generic parameter is null or default?
- How to us the FolderBrowserDialog
- Snippet creation - multiple $selected$
- radio button's "selected" event
- Use DllImport attribute to invoke functions in a native DLL
- Number lines
- Threading - ActiveX Events/Objects
- How to connect to microsoft excel workbook?
- Casting to nullable generics
- CallBack from a WIN 32 C++ dll
Visual C#
- Open Command prompt from C# program and run sqlcmd utility
- .NET-BroadcastEventWindow Application Error
- Centralized Snippet control?
- enum Property
- sql connection string
- referencing to C classes in C# application
- ATTRIBUTES
- strings - determining if a string has more than one word?
- IVsaSite vs ICodeCompiler
- turn this algorithm into code...help please
build / debug functionality missing?
CE31572
Hope that helps.
Bob Villa
here's an attempt to describe the problem better.
in vs, you can have different build configurations. these are managed with the configuration manager. as per default, a solution contains a debug and a release configuration.
you can also create your own configuration. as a part of a configuration, you can turn builds for selected projects on or off.
in vs 2003 one could create a solution where all projects had been turned off. the build-button from the toolbar would still invoke a build, but only the project with the currently active editor-window was build. no dependency checking or suchlike. this is a very fast method to do a change incase you know this change is not important to other projects.
however, when you pressed f5, vs2003 would still fetch all current assemblies: even from projects that had been turned off in the build configuration. thus, you could turn off _all_ projects in the configuration so that only a single project was build, but you could still test the changes because vs would copy the most current assemblies to the run directory.
vs 2005 no longer does this. iow: in order to test a change, a full build of the solution is required. this takes a _lot_ of time, especially incase you have a lot of projects in the solution. (i have 41).
so... what i am looking for ist something that vs 2003 did: i want to be able to build only a single project of my solution and still have vs copy the assembly produced to the run directory of the main target.
WM_THX
thomas woelfer
http://www.die.de/blog
justinv
well, 'build only project' is only available for cpp projects, not for cs projects. for .cs, its possible to 'build only selection', but that means other projects are still beeing build incase the current one has dependencies.
and apart from that 'build only project' (or 'build only selection') doesn't help: as soon as i press F5, the ide will build everything anyhow.
just try this yourself: create 40 projects and add them to a solution. (thats what i have over here.): next, try to do any productive work. its impossible, cause you're waiting for stuff to build all the time.
what i want it to do is:
- only build _one_ project. even if there are dependencies on other projects.
- don't build the solution before launching the debugger. only fetch the current dlls.
i have a feeling my explanation is not good enough. should i make a third attempt at descibing the problem
WM_QUERY
thomas woelfer
http://www.die.de/blog
Bindia Hallauer
Well, I am working with Web project. Even following these steps don't show me Debug and Release Build. All I see is Debug Build.
I am using Enterprise Library 1.1 for managing Database Configuration Etc.
In Debug mode, I want to connect to DB server 1 and in Release Mode I want to Convert to DB server 2. Without Debug/Release configuration I can't make this happen programatically.
Anyhelp with be appriciated
Roxana Ungureanu
I am not sure I understood the problem correctly, but there's still a "Build Solution" command in VS 2005. This will build only the dirty projects and if you start a debug session, all the new assemblies are automatically copied over.
Are you saying your projects are all "rebuilt" everytime you hit F5
Jose Cabrera
Hi Thomas –
< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
I don’t have a fix, but rather a suggestion until this gets sorted out: Make the 1 project of current interest into a single solution with a test driver.
Zakspeed63