Can anyone help me with some issues when deploying Web Setup projects?

1) You can specify the relative virtual directory and port number but not
the website to install to. For instance if the IIS web server has 4 web
sites it will pick one (at random? but always the same one, and not always
c:\inetpub\wwwroot / 'default web site'!) and install there, regardless of
what port the site is on (even if a different port is changed which is
unique to another site, it will still install to this original site with the
wrong port number). To get around it we have to temporarily set this
'default' site's home directory to where we want to install, run the install
and then change it back - a far from ideal solution which probably messes up
the uninstall. Even being able to pick the physical path would be useful
(c:\inetpub\wwwroot etc.)

2) How do you create virtual directories NOT pointing to apps within the
install? We use a trick to create a virtual sub-directory to a common
(external) app to get around session issues and have some kind of
reuseability with a relative path. The common app is installed separately
but I can't see how to make a virtual directory to it in the installer
setup?

3) Nasty problem when building an install for multiple projects going into
subdirectories of the main application directory (also applies to non-web
projects). Basically it brings across dependant assemblies for the first
project, but only seems to bring across one dependent assembly for the
others!? This means we're having to make a separate install for each
project, which is going to be a nightmare to maintain. Is there a trick to
getting this to work properly?

4) On the subject of IIS(5), since I upgraded to XP, any manually created
virtual subdirectories dissapear from the IIS tree (though they are there as
trying to add it again reports that it is in use!) This didn't happen on
Win2K. Is there a fix for this bug? Its like it will only display the
originally created virtual directory (made when the VS project was created),
and not any newly created copies of it as subdirectories of another. I'm
using the wizard in IIS to create these 'pointer' directories. Here's an
example of what I mean -

Two asp.net web applications under the web root -

Default Web Site
   |-App1
   |-App2

Add a child virtual directory under App1 also pointing to App2 -

Default Web Site
   |-App1
   |    |-App2
   |-App2

The 'child' App2 dissapears in the IIS tree on XP! (These are also the
things I want to create in the install in item 2) btw)

Thanks,

Simon