
Signature
Sean Hederman
http://codingsanity.blogspot.com
AFAIK, it is not possible to add property pages to the Project property
window, only to the Options page of the IDE, which is not per-project. Maybe
with VSIP packages, but not with add-ins.

Signature
Carlos J. Quintero
MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
You can code, design and document much faster.
http://www.mztools.com
> I'm writing an add-in that will have a set of properties it exposes on a
> per-project basis. Obviously it'd be more intuitive if it just slotted
> into the IDE's project properties. Anyone have any resources or pointers
> on how to do this?
Sean Hederman - 08 Feb 2005 13:30 GMT
Bugger! Well, a ToolWindow it'll have to be.
Thanks.
> AFAIK, it is not possible to add property pages to the Project property
> window, only to the Options page of the IDE, which is not per-project.
[quoted text clipped - 4 lines]
>> into the IDE's project properties. Anyone have any resources or pointers
>> on how to do this?
Carlos J. Quintero [.NET MVP] - 08 Feb 2005 16:56 GMT
If the window is modal, as I suppose, then you don?t need a toolwindow, a
.NET form shown modally will suffice.

Signature
Carlos J. Quintero
MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
You can code, design and document much faster.
http://www.mztools.com
> Bugger! Well, a ToolWindow it'll have to be.
>
> Thanks.
Sean Hederman - 08 Feb 2005 17:48 GMT
True enough. I've been debating with myself as to how to present these
options. The form properties are different for each project, and it's not a
very commonly accessed set of properties (for a licensing system). Another
idea I've been looking at is to use an Extender, and extend the project
properties in the Property Grid. I quite like that idea right now, I must
admit. I'm looking through docs and samples right now.
> If the window is modal, as I suppose, then you don?t need a toolwindow, a
> .NET form shown modally will suffice.
>
>> Bugger! Well, a ToolWindow it'll have to be.
>>
>> Thanks.