Change Website from File to Http

[GaryDean]

We created a "File" website on XP and transferred it over to server2003.
Now we want to change it to an HTTP site. Without creating a new project
and importing everthing, it there a way to convert it? the properties show
file:///C:/Inetpub/wwwroot /etc. but it can't be changed to HTTP. It's got
to be somewhere in some configuration file.

--
Regards,
Gary Blakely

[Brian Williams]

Why would you want to change it to HTTP?
What is the Server 2003, a QA Server or Production Server?

You could simply create an empty http project with the same name and copy
the files into it. I don't really see the point, if you are simply
publishing the website for QA or Production just use the Publish Website
menu. If you have several developers working on the same code, you will
probably want to leave it as a file project.

Regards,
Brian K. Williams


"GaryDean" <Ga******@newsg roups.nospamwro te in message
news:eD******** ******@TK2MSFTN GP03.phx.gbl...

We created a "File" website on XP and transferred it over to server2003.
Now we want to change it to an HTTP site. Without creating a new project
and importing everthing, it there a way to convert it? the properties
show file:///C:/Inetpub/wwwroot /etc. but it can't be changed to HTTP.
It's got to be somewhere in some configuration file.

--
Regards,
Gary Blakely

[bruce barker]

websites don't have project files. just adda vdir pointing to the file
dir, drop the site from the solution, then add the site from iis.
-- bruce (sqlwork.com)

GaryDean wrote:

We created a "File" website on XP and transferred it over to server2003.
Now we want to change it to an HTTP site. Without creating a new project
and importing everthing, it there a way to convert it? the properties show
file:///C:/Inetpub/wwwroot /etc. but it can't be changed to HTTP. It's got
to be somewhere in some configuration file.

[Steven Cheng[MSFT]]

Hello Gary,

For changing a "file" based ASP.NET 2.0 web project to http/IIS hosted web
project, you do not need to create a new project. What you need to do is
put your web application into IIS(in a certain application virtual
directory) and use VS 2005 to open that web project(through IIS/http path).
The detailed steps are as below:

1. In your server's IIS, create a new virtual directory and link it to your
original file web project's main directory(you can also use the "webshare"
tab in file explorer to link your web project folder into IIS). Make sure
the virtual directory is created as "applicatio n virtual directory" which
contains an application name.

2. After the virtual directory(link to your file project folder) has been
created, check the ASP.NET specific settings to make sure they suit ASP.NET
2.0 application. For example, the ASP.NET version number, the application
pool(make sure you use a separate application pool from other ASP.NET 1.x
web application).

3. After the IIS application virtual directory has been configured, you can
launch VS 2005 and open the web project from IIS as below:

** file --open website...

** in dialog's left view, select "Local IIS" panel, in the right view,
select the application virtual directory you created above and open it.

Hope this helps.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

=============== =============== =============== =====

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.

[GaryDean]

Your posting a reply and not answering the question. Why would you want to
do that?

--
Regards,
Gary Blakely
"Brian Williams" <wi*******@adel phia.netwrote in message
news:uD******** ******@TK2MSFTN GP04.phx.gbl...

Why would you want to change it to HTTP?
What is the Server 2003, a QA Server or Production Server?

You could simply create an empty http project with the same name and copy
the files into it. I don't really see the point, if you are simply
publishing the website for QA or Production just use the Publish Website
menu. If you have several developers working on the same code, you will
probably want to leave it as a file project.

Regards,
Brian K. Williams


"GaryDean" <Ga******@newsg roups.nospamwro te in message
news:eD******** ******@TK2MSFTN GP03.phx.gbl...

>We created a "File" website on XP and transferred it over to server2003.
Now we want to change it to an HTTP site. Without creating a new project
and importing everthing, it there a way to convert it? the properties
show file:///C:/Inetpub/wwwroot /etc. but it can't be changed to HTTP.
It's got to be somewhere in some configuration file.

--
Regards,
Gary Blakely

[GaryDean]

Thanks for the reply but...
"drop the site from the solution" uh, what do you mean?

--
Regards,
Gary Blakely
"bruce barker" <no****@nospam. comwrote in message
news:uH******** *****@TK2MSFTNG P04.phx.gbl...

websites don't have project files. just adda vdir pointing to the file
dir, drop the site from the solution, then add the site from iis.
-- bruce (sqlwork.com)

GaryDean wrote:

>We created a "File" website on XP and transferred it over to server2003.
Now we want to change it to an HTTP site. Without creating a new project
and importing everthing, it there a way to convert it? the properties
show file:///C:/Inetpub/wwwroot /etc. but it can't be changed to HTTP.
It's got to be somewhere in some configuration file.

[Brian Williams]

Gary,

Are you the Newsgroup monitor?
I did post an answer to the question just after my question. I am genuinely
curious of the reason. I an quite aware that I don't know everything and
find reading and answering questions to be a great way to learn.

Regards,
Brian K. Williams

"GaryDean" <Ga******@newsg roups.nospamwro te in message
news:u0******** ******@TK2MSFTN GP03.phx.gbl...

Your posting a reply and not answering the question. Why would you want
to do that?

--
Regards,
Gary Blakely
"Brian Williams" <wi*******@adel phia.netwrote in message
news:uD******** ******@TK2MSFTN GP04.phx.gbl...

>Why would you want to change it to HTTP?
What is the Server 2003, a QA Server or Production Server?

You could simply create an empty http project with the same name and copy
the files into it. I don't really see the point, if you are simply
publishing the website for QA or Production just use the Publish Website
menu. If you have several developers working on the same code, you will
probably want to leave it as a file project.

Regards,
Brian K. Williams


"GaryDean" <Ga******@newsg roups.nospamwro te in message
news:eD******* *******@TK2MSFT NGP03.phx.gbl.. .

>>We created a "File" website on XP and transferred it over to server2003.
Now we want to change it to an HTTP site. Without creating a new
project and importing everthing, it there a way to convert it? the
properties show file:///C:/Inetpub/wwwroot /etc. but it can't be changed
to HTTP. It's got to be somewhere in some configuration file.

--
Regards,
Gary Blakely

[Steven Cheng[MSFT]]

Hello Gary,

I think Bruce means the "Solution" which contains your ASP.NET 2.0 Web site
project. For ASP.NET 2.0 website project, VS2005 by default hide the
"Solution" node in solution explorer(for ASP.NET web application). You can
show the solution node as below:

1. choose tools--->options menue

2. In the options dialog, select "projects and solutions" node in left
view, and check the "always show solution" option in the right panel.

For change an existing file based web project to http/IIS hosted one, you
can refer to my previous reply, I pasted the steps here also:

=============== ======
1. In your server's IIS, create a new virtual directory and link it to your
original file web project's main directory(you can also use the "webshare"
tab in file explorer to link your web project folder into IIS). Make sure
the virtual directory is created as "applicatio n virtual directory" which
contains an application name.

2. After the virtual directory(link to your file project folder) has been
created, check the ASP.NET specific settings to make sure they suit ASP.NET
2.0 application. For example, the ASP.NET version number, the application
pool(make sure you use a separate application pool from other ASP.NET 1.x
web application).

3. After the IIS application virtual directory has been configured, you can
launch VS 2005 and open the web project from IIS as below:

** file --open website...

** in dialog's left view, select "Local IIS" panel, in the right view,
select the application virtual directory you created above and open it.
=============== ========

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

[GaryDean]

my attempt to answer your "why would you want to do that" with "why would
you want to do that" was my attempt to discourage people on forums from
answering questions with "why would you want to do that". It weakens the
effectiveness of the forum: people see an answer posted so they may tend not
to look at "an answered question" that really isn't answered. BTW, see the
thread from Steven Cheng for the correct answer.

--
Regards,
Gary Blakely
"Brian Williams" <wi*******@adel phia.netwrote in message
news:uZ******** ******@TK2MSFTN GP06.phx.gbl...

Gary,

Are you the Newsgroup monitor?
I did post an answer to the question just after my question. I am
genuinely curious of the reason. I an quite aware that I don't know
everything and find reading and answering questions to be a great way to
learn.

Regards,
Brian K. Williams

"GaryDean" <Ga******@newsg roups.nospamwro te in message
news:u0******** ******@TK2MSFTN GP03.phx.gbl...

>Your posting a reply and not answering the question. Why would you want
to do that?

--
Regards,
Gary Blakely
"Brian Williams" <wi*******@adel phia.netwrote in message
news:uD******* *******@TK2MSFT NGP04.phx.gbl.. .

>>Why would you want to change it to HTTP?
What is the Server 2003, a QA Server or Production Server?

You could simply create an empty http project with the same name and
copy the files into it. I don't really see the point, if you are simply
publishing the website for QA or Production just use the Publish Website
menu. If you have several developers working on the same code, you will
probably want to leave it as a file project.

Regards,
Brian K. Williams


"GaryDean" <Ga******@newsg roups.nospamwro te in message
news:eD****** ********@TK2MSF TNGP03.phx.gbl. ..
We created a "File" website on XP and transferred it over to
server2003 . Now we want to change it to an HTTP site. Without creating
a new project and importing everthing, it there a way to convert it?
the properties show file:///C:/Inetpub/wwwroot /etc. but it can't be
changed to HTTP. It's got to be somewhere in some configuration file.

--
Regards,
Gary Blakely

[GaryDean]

Steven,
thanks again for your help. I think your help alone has been worth the
price of my msdn subscription!
That worked very well. What we were missing was "in dialog's left view,
select "Local IIS". we were apparently blind to that left view.
--
Regards,
Gary Blakely
"Steven Cheng[MSFT]" <st*****@online .microsoft.comw rote in message
news:YO******** ******@TK2MSFTN GHUB02.phx.gbl. ..

Hello Gary,

For changing a "file" based ASP.NET 2.0 web project to http/IIS hosted web
project, you do not need to create a new project. What you need to do is
put your web application into IIS(in a certain application virtual
directory) and use VS 2005 to open that web project(through IIS/http
path).
The detailed steps are as below:

1. In your server's IIS, create a new virtual directory and link it to
your
original file web project's main directory(you can also use the "webshare"
tab in file explorer to link your web project folder into IIS). Make sure
the virtual directory is created as "applicatio n virtual directory" which
contains an application name.

2. After the virtual directory(link to your file project folder) has been
created, check the ASP.NET specific settings to make sure they suit
ASP.NET
2.0 application. For example, the ASP.NET version number, the application
pool(make sure you use a separate application pool from other ASP.NET 1.x
web application).

3. After the IIS application virtual directory has been configured, you
can
launch VS 2005 and open the web project from IIS as below:

** file --open website...

** in dialog's left view, select "Local IIS" panel, in the right view,
select the application virtual directory you created above and open it.

Hope this helps.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

=============== =============== =============== =====

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no
rights.