By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,952 Members | 1,725 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,952 IT Pros & Developers. It's quick & easy.

Web Applicaiton installation uses wrong version of ASP.NET

P: n/a
We recently moved from VS 2003.NET / ASP.NET 1.1 to VS 2005 / ASP.NET 2.0.
The VS solutions for our Web Applications alway include a deployment project
that builds an installation file (MSI file) When we install are VS 2005 /
ASP.NET 2.0 projects on a server the resulting IIS virtual directory always
ends up configured for ASP.NET 1.1. How do we get the applications to
install with the correct version ASP.NET configured?
Apr 26 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a

Open IIS. From the Control Panel / Admin Tools.

Find the directory.

Right click / Properties.

Go to the (new) last tab.

You select the version there.

It ~has to be a virtual directory before the last tab is workable.


"mikes" <mi***@discussions.microsoft.comwrote in message
news:48**********************************@microsof t.com...
We recently moved from VS 2003.NET / ASP.NET 1.1 to VS 2005 / ASP.NET 2.0.
The VS solutions for our Web Applications alway include a deployment
project
that builds an installation file (MSI file) When we install are VS 2005 /
ASP.NET 2.0 projects on a server the resulting IIS virtual directory
always
ends up configured for ASP.NET 1.1. How do we get the applications to
install with the correct version ASP.NET configured?


Apr 27 '07 #2

P: n/a
We know how to correct the problem once the application is installed, what we
really want to know is how to get the application installed without the
manual intervention. We really don't want to rely on the person installing
the application to correct the problem.

Mike

"sloan" wrote:
>
Open IIS. From the Control Panel / Admin Tools.

Find the directory.

Right click / Properties.

Go to the (new) last tab.

You select the version there.

It ~has to be a virtual directory before the last tab is workable.


"mikes" <mi***@discussions.microsoft.comwrote in message
news:48**********************************@microsof t.com...
We recently moved from VS 2003.NET / ASP.NET 1.1 to VS 2005 / ASP.NET 2.0.
The VS solutions for our Web Applications alway include a deployment
project
that builds an installation file (MSI file) When we install are VS 2005 /
ASP.NET 2.0 projects on a server the resulting IIS virtual directory
always
ends up configured for ASP.NET 1.1. How do we get the applications to
install with the correct version ASP.NET configured?


Apr 27 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.