Web Setup Patch???

[glenn.owens]

Until now all of my VS2003 asp.net websites have been deployed to the
target server's IIS6+ Default Web Site. Now I need to deploy to a
different website and that seems to present a problem.

Normally, I set up a directory structure to hold the application files
and then create the virtual directory. Now instead of a virtual
directory I've created a new Web sight and registered the IP address
and Host Header information with the DNS server - so far so good.

From VS2003 I created a Web Setup Project and deployed the .msi file to

the correct directory on the target server from VS - works great!

When I execute the .msi to install the website files I find that the
files are created in a subfolder within the specified structure.
Repeating the .msi install procedure creates further subfolders.

I've seen some posts indicating the VS2003 has problems deploying to
anything but the Default Web Site. I've also seen [one] post suggesting
that MS has created a Web Set Patch to address some deployment
issues???

Is there really a problem (or did I just miss something)?? If there's a
problem with deploying to a non-Default Web Site is there a fix/patch
available??

My client is waiting for the website as we speak!!! (so any help would
be greatly appreciated)

Glenn

 

[Scott Allen]

Hi Glen:

Yes, the setup and deployment projects do have a problem when there
are multiple sites running. I'm not aware of any patches for the
problem, but I believe temporarily put the destination web site on a
unique port you'll have a successful installation.

--
Scott
http://www.OdeToCode.com/blogs/scott/

Until now all of my VS2003 asp.net websites have been deployed to the
target server's IIS6+ Default Web Site. Now I need to deploy to a
different website and that seems to present a problem.

Normally, I set up a directory structure to hold the application files
and then create the virtual directory. Now instead of a virtual
directory I've created a new Web sight and registered the IP address
and Host Header information with the DNS server - so far so good.

From VS2003 I created a Web Setup Project and deployed the .msi file to

the correct directory on the target server from VS - works great!

When I execute the .msi to install the website files I find that the
files are created in a subfolder within the specified structure.
Repeating the .msi install procedure creates further subfolders.

I've seen some posts indicating the VS2003 has problems deploying to
anything but the Default Web Site. I've also seen [one] post suggesting
that MS has created a Web Set Patch to address some deployment
issues???

Is there really a problem (or did I just miss something)?? If there's a
problem with deploying to a non-Default Web Site is there a fix/patch
available??

My client is waiting for the website as we speak!!! (so any help would
be greatly appreciated)

Glenn

 

[bruce.armstrong]

FIX: You cannot deploy a Web Setup project to Web sites by using host
headers or IP addresses in Visual Studio 2003 and Visual Studio 2002
Service Pack 1

http://support.microsoft.com/default.aspx?scid=kb;en-us;821335

SessionState wrote a VBS wrapper for it.

http://www.sessionstate.com/Default.aspx?blogID=46

I managed to write a Add-In to implement it as well.

 

[glenn.owens]

Is there something about the new DPCA.dll and/or the vbs script which
forces msi to deploy to the inetpub\wwwroot???

Our installation uses a different directory structure for deployment
(not inetpub...). However, since using the new DPCA.dll and
SessionState's vbs script the msi deploys exclusively to inetpub???

Glenn