Multiple project solution newbie question?

  • Thread starter Thread starter Bruce W.1
  • Start date Start date
B

Bruce W.1

I setup a solution with multiple projects (2 of them) just like it says
here:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q307467

The subdirectories will contain real .aspx pages, not just User Controls
or components. They are distinctly different parts of this one web
application.

So where does default.aspx go? Are there three of them or just one?

What does the user see for a URL when they are using a page in one of
the project subdirectories? Do they see the subdirectory in the URL?

And how is browser navigation between the projects normally handled or
controlled?

Thanks for your help.
 
Bruce W.1 said:
I setup a solution with multiple projects (2 of them) just like it says
here:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q307467

The subdirectories will contain real .aspx pages, not just User Controls
or components. They are distinctly different parts of this one web
application.

So where does default.aspx go? Are there three of them or just one?
Click to expand...
Normally you use only one default.aspx

If a user directly types www.yoursite.com/subpath you *know* he is not
entering the site correctly so you simply not write code for such event. (Or
at least a custom 404 page)
So default.aspx is *only* at the place where browsing starts...
that would be for instance http://www.yoursite.com

What does the user see for a URL when they are using a page in one of
the project subdirectories? Do they see the subdirectory in the URL?
Click to expand...
Yes if you program normally, all aspx pages behave just as html pages or
images. So, you see (if you click page properties in IE) where that page
resides including subdirectory.
And how is browser navigation between the projects normally handled or
controlled?
Click to expand...
You just care for 1 thing. Make a page link to another and link back.
<a href="mypage1.aspx">More info</a>
<a href="main.aspx">go back</a>

but a professional way is to add a context sensitive **menu** (see
www.infragistics.com for good ASP.NET menu controls) to each page so
navigating becomes more natural for the user.
 
Egbert Nierop (MVP for IIS) said:
Normally you use only one default.aspx

If a user directly types www.yoursite.com/subpath you *know* he is not
entering the site correctly so you simply not write code for such event. (Or
at least a custom 404 page)
So default.aspx is *only* at the place where browsing starts...
that would be for instance http://www.yoursite.com
Click to expand...
========================================================

Makes sense. So is there a practical way to hide the subdirectory in
the URL? Or maybe most people don't bother?

From a file management perspective the home page is one project. From a
website hierarchy perspective it is the main page.

What if you want your home page (and whatever it does) to be one of the
"projects". Does it make sense to put it in a subdirectory like all the
other projects? If so then just put a redirect from the default page in
the parent directory?

Thanks.
 
Back
Top