Cool! I had heard it was possible, but never seen how, so thanks.
Now, one question, do you know what happens if someone without
the enterprise version of VS.NET tries to open up this this solution?
Paul: Glad I could help out. No idea what happens when you open it with a non-ent. version though. :(
I'd love to know if you ever find out though.
> do you know what happens if someone without
the enterprise version of VS.NET tries to open up this this solution?
I havn't checked myself, but I'm quite sure that it the solution would load, but that the project wouldn't load and instead would appear grayed out. VS.NET is an extensible platform where you can add new project types. For instance, ActiveState has something called Visual XSLT which makes it possible to create a new type of XSLT project in VS.NET. But if somebody without this product tries to open the solution, the project will be unavailable. The Enterprise Template is just another project type. Try to open a solution file in a text editor. You will see some GUID's that most likely identify the project types and the add-ins used to load these projects.
The thing I am trying to figure out is how you can, as an "architect" make a template solution ot be consumed by your development groups. Creating the solution is straightforward, what I am missing is how the developer can consume it, without the possibility of modifying it.