Designing an App for ISP style hosting

[Autofuzz]

I'm trying to make a dotnet app (asp.net with VB code behind/vb.net
webservices and components etc) that needs to be hosted like in an ISP
environment on Windows 2003.

The whole product will probably look like this :
- MyServer1 -
- App1
- App2
- App3
- MyServer2 -
- App1
- App5
- App9

Where 'MyServer' is an abstraction for a company who has licenses for
various Apps (apps would be individual applications in the product
suit)
Each application would have a bunch of asp.net and vb.net dll's and
webservices associated with it, and obviously App1 in MyServer1 will
be exactly the same as App1 in MyServer2.
My question is how should the binary artifacts be layed out in such a
situation? should I have copies(side by side) of the entire
application repeated for every new MyServer? Or have one single
directory for all the artifacts and somehow map multiple MyServers to
it? Can Asp.net pages reside in a side by side manner like the dll's
might?

Any references to writing enterprise grade dotnet apps in a ISP type
situation would be very helpful too.
Thanks,
Auto