We are developing a small Outlook plugin using VS2010 / VSTO.
It’s a new thing for us so we’re wondering what’s possible and what’s not possible in an Outlook plug-in versus our more familiar Winforms stuff. So we’re making small piecemeal changes and checking frequently by running it in Outlook.
At the moment our change/test cycle works like this:
- In the Visual Studio IDE add, change, fix or extend the code in some small way
- F5
- Ding! Warning that Outlook is already running. Lose a life.
- Close Outlook
- F5
- Outlook starts, test the change
It’s the restarting Outlook that makes it so slow.
Is there any way to debug without restarting Outlook? Or, what would be even better, is there any way to debug-and-continue?
If not, is there anything at all we can do to make this bit of dev a touch more fluent/faster?
As far as I’m aware you can’t make code changes and continue debugging. You need to reload Outlook so that it loads in the new DLL. You could always write your own code that monitors a particular DLL and loads it in real-time, eg
Then you can work on your DLL, modify the code and re-load the thing with outlook still running. Probably more hassle than it’s worth though.
Outlook 2007 is very quick to start on my machine (but I’ve got a beefy i5 machine) – it literally takes 2 seconds to open. If your Outlook is really slow to startup, consider doing the following:
Is Outlook itself taking ages to load? (Eg for the initial splash screen to go away) Or is it chugging away after it’s opened?