I have good news and bad news. The good news is: you don't have to recode the
entire application. The bad news is: in VS2003, you can't use .ETP files in
the Professional sku.
What you can do is create a new solution, then do an "Add existing..." to
add the projects that are in your current application to that new, empty
solution. Clear the policy file property for each project in the solution.
Then hand off the solution to your client.
The even better news: VS2005 will support policy in the Professional SKU
(referred to as "VS Policy"). And the special ".ETP" projects will be
replaced by "Solution Folders" that are supported in all SKUs. When you
switch to VS2005, you won't see references to "Enterprise Templates" as such,
but the functionality is still there under the names "VS Templates" and "VS
Policy".
Hope this helps...
[quoted text, click to view] "Aspwebwizard" wrote:
> We built an application using VS.net 2003 Enterprise version using the
> Enterpise templates. However, our client is using VS.Net 2003 Professional
> version and need to make his own changes. He is not able to open the
> solution we created in VS.Net 2003 Prof since he gets the following pop-up
> error message :
>
> "The application for project C:\VSProjects\project1.etp' is not installed.
> Make sure the application for the project type (.etp) is installed "
>
> How do we go about resolving this ? Client is not willing to purchase the
> Enterprise version.
> Do we have to recode the entire application to allow recompiling on the Prof
> version ? This would be a big problem.
>
> Thanks for any suggestions and help.
>
>
>
>