Hi Artur, Thank you for the information. I never knew an exe could be debugged this way because I've never needed to do it that way.
What I would like to point out is that for most visual studio and windows users this is a strange way to work. Windows users are used to working almost exclusively through the gui and using devenv or msbuild is normally restricted to running in a batch file or on a build machines as some kind of build for end user or for a verification process. For working with visual studio, I used to have to reboot my machine every day, but now I leave it on because it's much more stable. I find the visual studio icon (normally pinned to the taskbar), start up visual studio, find the solution, build the code, press f5 to launch the debugger, step through and debug it via the watch windows, local registers, callstack etc. Debugging is easy because I can hover over a variable and it tells me it's value, or put it into the watch window. I can also go through structures easily by expanding and contracting the + mark next to the structure in the watch window. It's just a different way of working compared to other OS's. The solution file I posted was not the normal one visual studio uses. Normally a project type is defined and files are added and visual studio performs the build and link using that information. In this case I setup a project in makefile mode and configured it to make debug or release builds. I also included the original source since the other files are not there before a build is initiated. I was still able to place a breakpoint anywhere in the code, step through the code and view the variables and their values. For a normal visual studio user this is closer to what they know.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
