| T O P I C R E V I E W |
| peterchen |
Posted - Jan 18 2010 : 3:42:05 PM
(It's probably more of a Visual Studio quesiton, but that little addin of yours is involved, too  )
When developing an addin, I typically hold down shift when starting the IDE, so it doesn't load addins (so that my addin isn't locked and can be written to).
However, when I go to "AddIn Manager..." and try to enable VAX, it is diabled again when I close and reopen this dialog, and of course all VAX commands remain disabled.
Any suggestions?
How do your developers deal with that?
|
| 2 L A T E S T R E P L I E S (Newest First) |
| sean |
Posted - Jan 21 2010 : 4:50:32 PM
We don't use the shift key technique to copy our addin in place. Building the addin dll does not automatically copy it into the install directory. We exit, copy and then restart.
That said, our addin dll is mostly a shim so it doesn't change very often. It forwards notifications/events/work on to our main dll in significant part to ease development on the IDE while using it at the same time. The debug version of our addin dll has logic to load alternative versions of VA_X.dll in different circumstances (we can be running one version and debugging a different version in another instance of the IDE - using the same addin dll in both).
|
| accord |
Posted - Jan 19 2010 : 03:37:07 AM
If you use Windows 7 and hold shift down to launch a new Visual Studio instance then you can use middle mouse click to achieve this. Hope this helps. |
|
|
