Hi Becca,
The Solution Extender addin sample out on
http://www.microsoft.com/downloads/details.aspx?familyid=3ff9c915-30e5-430e-
95b3-621dccd25150&displaylang=en might be of interest.
From a VSIP package, you could use the EnvDTE automation model and simply
use the DTE.Solution.Globals object to persist custom properties to the
SLN.
Allen Denver has some info on his blog on how to retrieve the EnvDTE.DTE
object from your package on
http://blogs.msdn.com/allend/archive/2004/03.aspx.
Sincerely,
Ed Dore [MSFT]
This post is 'AS IS' with no warranties, and confers no rights.
becca - 04 Jan 2006 16:36 GMT
> The Solution Extender addin sample out on
> http://www.microsoft.com/downloads/details.aspx?familyid=3ff9c915-30e5-430e-
> 95b3-621dccd25150&displaylang=en might be of interest.
I can't get this add-in to work. I added the .reg file to the registry
through regedit, and it said it worked, but nothing shows in the add-in
manager and I can't see the solution props.
> From a VSIP package, you could use the EnvDTE automation model and simply
> use the DTE.Solution.Globals object to persist custom properties to the
[quoted text clipped - 3 lines]
> object from your package on
> http://blogs.msdn.com/allend/archive/2004/03.aspx.
I'm attempting to do this, but my project has an error when its trying to
register the dll (in a post-build custom event). I don't think the two are
related, as this happened sometimes before, but any ideas as to common
reasons why it won't register? The path names of the dll and tool look ok.
Thanks.
becca - 04 Jan 2006 20:52 GMT
I still haven't gotten the addin to work, but I did get the other option
(with DTE.Solution.Globals) to work.
I'm still having problems getting the debugger to work though, there is some
problem where it can't load symbols so it won't actually help me debug,
although the whole thing runs. Any suggestions?