I am implementing a new project type using VS.NET Whidbey Beta 1 and VSIP
2005 Beta 1. I have implemented an ATL object supporting IVsPackage and
IVsProjectFactory. I'm just trying to bring up a small prototype, so I'm not
using a satellite DLL. Everything *appears* to be registering correctly,
according to the docs and comparison with BscPrj. I've implemented a project
file template and a .vsdir file, as well as a project type icon, and I've set
up my resources similar to BscPrj.
I want to see my package interact with VS, then implement the rest of the
functionality incrementally. For example, I haven't implemented Add New
Item or any of the project hierachy support.
I'm expecting to be able to see my project type when I run devenv /setup
/rootsuffix exp followed by devenv /rootsuffix exp, but it doesn't appear.
(1) Have I implemented enough of a package to expect VS to load it?
(2) If not, what's the minimum required?
(3) Is it likely I've just messed up my registry script?
(4) How can I debug this?
thanks
--Don
chris - 15 Nov 2004 10:39 GMT
What I usually do is add ATLTRACE statements to interesting entrypoints (in
your case that would be the DLL functions, class factory etc) and include
__FUNCTION__ to see which functions are called in what sequence. Very useful
it to run DbgView
from SysInternals to collect debug messages. There are also tracing options
in ATL to see what QIs have been done, so you can find missin ginterfaces.
Good Luck,
Jan
> I am implementing a new project type using VS.NET Whidbey Beta 1 and VSIP
> 2005 Beta 1. I have implemented an ATL object supporting IVsPackage and
[quoted text clipped - 18 lines]
> thanks
> --Don