Multiple NET apps under 1 domain

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello everyone -

Newbie here with another dumb question :-)

I want to have several apps under 1 domain - basically the domain root for
general users and then an "admin" folder with a database utility

www.generalusers.com
www.generalusers.com/admin

So the world will go to www.generalusers.com (Default.aspx) and see the
website and maybe fill out a form which is stored in a db.

The admin dba will go to www.generalusers.com/admin/admin.aspx and do
his/her stuff.

But if I set this up ( in 2 different VS 2005 solutions), when I publish the
admin app it erases the generalusers folder. During publish there is a
dialog box that comes up that asks is it ok to erase. If I say 'no' then
the publish fails.

How do I set this up?

There also seems to be a 'precompileapp.config' file which is written to the
domain root which I think will interfere with the generalusers app.

How do I stop the admin publishing from deleting everything in the root
folder?

Many thanks in advance.

Regards,
bruce
 
Looks like you want to create two distinct applications. My personal
preference would be likely to put each one in its own folder and use a
virtual folder inside the main web application to map /admin to the location
for the admin application (also defined as a web application).

See :
http://support.microsoft.com/kb/301392
 
Thanks for the reply Patrice.

Yes I do have 2 apps. I don't have access to IIS. I do my development using
VS 2005 and their local pseudo IIS server.

I have 2 VS solutions which need to be published to the same domain.
I could combine the two ( and sort out all of the connection string possible
namespace collisions).
I was looking for the ability to maintain 2 VS solutions that point to the
same domain - for example
www.main.com for the world
www.main.com/admin/admin.aspx only for DBA

It doesn't look like the publish functionality supports this intuitively. I
dk.
 
My personal preferences would be :
- to use a virtual dir so that each application is in its own physical
directory (and not one as a subfolder in the main one)
- to combine both
- to deploy them NOT using the publish functionality (you could likely use
FTP).

As a side note if you don"t have access to IIS how could you anyway define
the /admin directory as being an IIS application ?

Good luck.
 
Patrice,
Thanks for your reply.
I have bitten the bullet and merged the 2 VS solutions into 1.
I guess I am an old crusty C++ programmer and developed the 2 individual
solutions from habit.

In regards to IIS, I use Visual Studio to display my applications in a
browser.
When I do this a process starts up locally named "Visual Studio Development
Server".
I guess that is acting as IIS.

Regards,
bruce
 
Back
Top