Enterprise Template Policy Editor

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

STom - 22 Mar 2005 03:42 GMT

Where can I find the VS.Net 2003 Policy Editor for enterprise templates?

STom

Reply to this Message

Steven Powell (MSFT) - 23 Mar 2005 23:53 GMT

STom -

There isn't an official Visual Studio Policy Editor. There was a prototype
of a Policy editor, developed by a third party and published on MSDN that you
can find here
http://www.microsoft.com/downloads/details.aspx?familyid=78041e07-9997-4ee9-8c66
-d64cc322d7ec&displaylang=en

There was some discussion about having a VSIP Editor sample that was a
simple Policy Editor that would have accompanied VS2005, but unfortunately I
believe that work was cut due to time constraints. The policy file schema for
VS2005 is much simpler and the concept of "identification" and "rules" are
separated into two files, allowing you to have a reusable ".vspolicydef" file
that you include in your much simpler policy files for VS2005. You can give
this a try in VS2005 beta2 when it's available in the not-too-distant future.

Steven Powell

> Where can I find the VS.Net 2003 Policy Editor for enterprise templates?
>
> STom

Reply to this Message

STom - 24 Mar 2005 00:09 GMT

Thanks Steven.

I am doing a review of our enterprise templates now and we are concerned
about the supportability of the templates when we go to VS2005. I'm not
exactly sure what caveat to put in to watch out for when it comes out.

Any info you might have would be helpful. Thanks for the pointer.

STm

> STom -
>
[quoted text clipped - 22 lines]
>>
>> STom

Reply to this Message

Steven Powell (MSFT) - 25 Mar 2005 01:27 GMT

STom -

While the term "enterprise templates" won't be seen much in VS2005, the
concepts are still supported as VS Templates & VS Policy. There are some
things you can do when developing VS2003 templates to make them easier to
bring forward to VS2005. The biggest one is around which approach you take to
building your "template". VS2002/2003 supported a couple different
mechanisms: (a) static project prototypes (b) top-level .ETP project with
sub-project wizards (c) top-level wizard that adds sub-projects through
wizards or prototypes (this 3rd approach is the one demonstrated in the
Application Construction Kit whitepaper on MSDN).

The 3rd approach is very easy to migrate to VS2005. The first two will need
to be converted to the 3rd, due to Solution folders replacing .ETP projects.
We'll have a whitepaper providing some guidance around this migration by the
time VS2005 ships.

Are there specific concerns you have? Are there enhancements you'd like to
see (other than a Policy editor) that would add significant value for you?

thanks,
Steven

> Thanks Steven.
>
[quoted text clipped - 31 lines]
> >>
> >> STom

Reply to this Message

Enterprise Template Policy Editor

Free Magazines