We recently converted our multiple solutions to use enterprise templates and
since then it has been a frustrating battle with VSS integration :(
1) When doing get latest on the solution it doesn't get any changes to
templates. Have to do that in VSS itself for it to get the latest on the
templates and any new projects within them.
2) Adding a new project to a template doesn't check out the solution and so
doesn't update the list of projects correctly (see 1))
3) Getting latest on a root template sometimes throws up a message asking
whether to unload a project because it has dependencies on another
installation project. Selecting yes will stupidly unload the project for no
reason, selecting no seems to stop VSS from getting latest again until
VS.NET is restarted.
4) Changing solution configurations sometimes asks you to check the template
out for no obvious reason, popping up a message about in-memory changes,
selecting no is the only viable option, or it will lose the info on which
projects are included to build in the configuration (which seems to happen
anyway since we started using templates :/ )
Anyone else had these problems or have a work-around for them?
Simon
Joe Masters - 05 Apr 2005 06:14 GMT
Are enterprise templates a new (Whidbey) feature? You'll need to ask those
questions in one of the beta newsgroups.
Joe
> We recently converted our multiple solutions to use enterprise templates
> and
[quoted text clipped - 25 lines]
>
> Simon
Anonymous Poster - 05 Apr 2005 09:36 GMT
hi Joe,
No, they're part of the Enterprise Architect edition of VS.NET
Simon
> Are enterprise templates a new (Whidbey) feature? You'll need to ask those
> questions in one of the beta newsgroups.
[quoted text clipped - 30 lines]
> >
> > Simon
Joe Masters - 12 Apr 2005 07:49 GMT
Sorry, then. I'm not familiar with them. You may need to call Microsoft
Product Support.
Joe
> hi Joe,
>
[quoted text clipped - 45 lines]
>> >
>> > Simon