I usually configure "Debugging" tab from inside the active project
properties to use a binary which is built by ant. Running the process
with VS attached all the time makes a thread behavior, memory
violation addresses, etc, more or less reproducible from launch to
launch.

On Tue, Mar 11, 2008 at 3:19 PM, Gregory Shimansky
<[EMAIL PROTECTED]> wrote:
> Simon Chow said the following on 11.03.2008 15:14:
>
> > I am not very familiar with vs.net. Is there guide for doing this?
>  > Should I use the executable file generated from ant build or
>  > vs.netsolution/project build for debugging?
>
>  I don't think that using project you can build a fully functional
>  runtime. Usually I open the project just for files/symbols lookup and
>  specify executable and command line options in the debug properties.
>  Then I start debugging _without_ rebuilding the project.
>
>  More often I use just-in-time debugging feature. When a process crashes
>  or hangs I attach MSVC to it from the crash dialog or using task manager.
>
>  --
>  Gregory
>
>



-- 
With best regards,
Alexei

Reply via email to