I'm getting just a little difficulty attempting to wrap my mind around site structures. I've a significant large asp.internet site, that:

Admins can easily see a person list, Each user might have many accounts, as well as for each account might have many products.

I'm able to otherwise this could happen like a breadcrumb trail of editing a specific item.

User List > Mr Bob > Accounts > BOB77 > Products > Item32 > Edit

  • User List = All of the customers
  • Mr Bob = A person the administrator has selected in the User List
  • Accounts = A listing from the user's accounts
  • 12BOB = The administrator has selected the account named 12BOB
  • Products = A listing from the products a merchant account consists of
  • Item32 = The product the administrator selected
  • Edit = The experience the administrator really wants to do

I'm able to picture how this could seem like whether it was using ASP.Internet MVC using the URL, however i am unsure how you can map this out using Webforms, as well as in the physical filesystem.

This is exactly what I've thought up about how exactly I'm speculating the physique would seem like. Will this need to use session variables to attain things i am attempting to do?

  • /Customers/User/Edit.aspx <- for editing a person
  • /Customers/User/View.aspx <- for viewing a person
  • /Customers/User/Accounts/Default.aspx <- for viewing all accounts
  • /Customers/User/Accounts/Account/View.aspx <- for viewing a merchant account
  • /Customers/User/Accounts/Account/Edit.aspx <- for editing a merchant account
  • /Customers/User/Accounts/Account/Products/Default.aspx <- for viewing all products within an account
  • /Customers/User/Accounts/Account/Products/Item/Edit.aspx <- for editing a product

How can i find out more relating to this type of setup inside a web application? Or, can someone point me in direction of an available project which has this type of layout?


This appears simple, however when you wish to construct the logical structure and you are thinking about every element towards the structure, it might be very unclear.

This is actually the url format I emerged with. This uses query strings rather than Session variables. Query strings are utilized as parameters.

By using this format I could create a sitemap provider which construed the values from the querystring and changed what they are called of nodes for your page.

  • User/Edit.aspx?UserID=11111
  • User/Account/Default.aspx?UserID=11111
  • User/Account/Edit.aspx?UserID=111&AccountID=54353
  • User/Account/Item/Edit.aspx?UserID=3333&AccountID=43243&ItemID=432432

I really hope this can help you, if you're in a similar situation as to the I had been.