In your plugins project properties set the startup item to external program and point that to OM. Now when you hit debug in VS it will start OM automatically with the debugger attached.
I'm trying to see how to set up OM to allow me to debug a .dll/plugin while developing. Unfortunately, I do not know if it's possible. Here's the scenario...
I write out a portion of the program and build the dll. Running OM and trying the program, it crashes somewhere. Unfortunately even with the debug log, it's still a guess in the coding where the crash actually happened, and then figure out why? Is it possible to set up an active debugging sessions, so I can debug/test/etc while developing. I'm growing ever tired of trial and error and wasted time .
It would be the same as actively debugging a standalone formed app from withing visual studio - but it is possible with a .dll?
With a quick glance around the express version of 2010 and using a class library (.dll) project, the startup object list is blank. I'm not at home so I'm not sure if the pro/ultimate/whatever version I have there is different. With a quick google search, the majority says class libraries can't be changed. Only have express 2010 at work so that could be a reason, but can the forms projects be set to run at an external program? Maybe I can just switch it over to forms to debug and switch back to class library to release? Sorry if it's easy, I'm bored at work though !?In your plugins project properties set the startup item to external program and point that to OM. Now when you hit debug in VS it will start OM automatically with the debugger attached.
Correct about the limitations of express version, in fact attaching to a process was removed in 05+ versions of express.
However, there is a workaround to it. Find your project folder, and inside find the xxx.csproj and open it with notepad. Insert these lines:
When using VS, just click the debug and it will open OM. However, I think you still must build the .dll and place it in the correct directory first, and when debugging, I can't change anything because the assembly isn't loaded... Maybe the pro version will fix that when I try tonight. I'll update then!Code:<PropertyGroup> <StartAction>Program</StartAction> <StartProgram>C:\Program Files\openMobile\Open Mobile.exe</StartProgram> </PropertyGroup>