Deployment to shared host?

[Steve Brecher]

VS.NET help on deployment indicates that, while using a deployment project
requires administrative access to IIS, " we recommend deploying your project
[as opposed to just copying it] in most cases, because it allows you to take
advantage of extensive deployment project management features, such as
registration and IIS configuration."

I guess that users of shared web hosts are using copying rather than a
deployment project. What problems might this run into? I.e., what web
application features require "registration and IIS configuration"?

--
For mail, please use my surname where indicated:
st***@surname.reno.nv.us (Steve Brecher)

[Steve C. Orr, MCSD]

Generally nothing .NET requires registration or IIS configuration.
(Of course your web folder needs to be configured as an IIS application, but
that is standard for any web site.)

You'll only run into problems if you need to use old COM components, or if
you need to access the registry or other sensitive shared areas of the
hosted server.

--
I hope this helps,
Steve C. Orr, MCSD
http://Steve.Orr.net

"Steve Brecher" <St***********@see.sig.at.end> wrote in message
news:ON******************@TK2MSFTNGP10.phx.gbl...

VS.NET help on deployment indicates that, while using a deployment project
requires administrative access to IIS, " we recommend deploying your project [as opposed to just copying it] in most cases, because it allows you to take advantage of extensive deployment project management features, such as
registration and IIS configuration."

I guess that users of shared web hosts are using copying rather than a
deployment project. What problems might this run into? I.e., what web
application features require "registration and IIS configuration"?

--
For mail, please use my surname where indicated:
st***@surname.reno.nv.us (Steve Brecher)

[David Waz...]

I think you can also control what files go out when you deploy. for
example, do you want your source code to go out with your project? If not,
deploy instead of copy.
"Steve C. Orr, MCSD" <St***@Orr.net> wrote in message
news:ul**************@TK2MSFTNGP10.phx.gbl...

Generally nothing .NET requires registration or IIS configuration.
(Of course your web folder needs to be configured as an IIS application, but that is standard for any web site.)

You'll only run into problems if you need to use old COM components, or if
you need to access the registry or other sensitive shared areas of the
hosted server.

--
I hope this helps,
Steve C. Orr, MCSD
http://Steve.Orr.net

"Steve Brecher" <St***********@see.sig.at.end> wrote in message
news:ON******************@TK2MSFTNGP10.phx.gbl...

VS.NET help on deployment indicates that, while using a deployment project requires administrative access to IIS, " we recommend deploying your

project

[as opposed to just copying it] in most cases, because it allows you to

take

advantage of extensive deployment project management features, such as
registration and IIS configuration."

I guess that users of shared web hosts are using copying rather than a
deployment project. What problems might this run into? I.e., what web
application features require "registration and IIS configuration"?

--
For mail, please use my surname where indicated:
st***@surname.reno.nv.us (Steve Brecher)

[Felix Wu [MSFT]]

Hi Steve,

Just as Steve C and David said, using deployment project is not required if
the directory on the shared host is already configured and you have no
components to register on the host. "Administrative Access" is required
when using the deployment project is because that with deployment project,
you can create virtual directory and configure the setting when installing
the web application on the host. However, these actions require that you
have administrative access to the IIS.

Regards,

Felix Wu
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

From: "Steve Brecher" <St***********@see.sig.at.end>
Subject: Deployment to shared host?
Date: Sun, 6 Jul 2003 11:52:01 -0700
Lines: 15
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <ON**************@TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: brecher.reno.nv.us 216.82.143.39
Path: cpmsftngxa09.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTN GXA05.phx.gbl!TK2MSFTNGP08
..phx.gbl!TK2MSFTNGP10.phx.gblXref: cpmsftngxa09.phx.gbl microsoft.public.dotnet.framework.aspnet:32570
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

VS.NET help on deployment indicates that, while using a deployment project
requires administrative access to IIS, " we recommend deploying your project[as opposed to just copying it] in most cases, because it allows you to takeadvantage of extensive deployment project management features, such as
registration and IIS configuration."

I guess that users of shared web hosts are using copying rather than a
deployment project. What problems might this run into? I.e., what web
application features require "registration and IIS configuration"?

--
For mail, please use my surname where indicated:
st***@surname.reno.nv.us (Steve Brecher)