Shawn Mehaffie wrote
Not sure what you are wanting to know. Why are you creating Child Portals and accessing them in VS 2008. The only reason you would not to run DNN under VS to run under VS is becuase you are developing modules. And for that you do not need to create Child Portals. If not developing modules, or custmizing the core code (highly not recommended) I would run the site under IIS, so it is more like how the site will run in the real world.
This is correct. I am developing modules.
But I also study how thing work.
My question was not about child portals whatsoever!
The main point is that I do not understand:
Why is a need and dependence on HTTPAlias in database?
Why to keep them in database?
For ex., I copy the content of DNN website and I cannot launch as WSP it because its (directory) name is taken from HTTPAlias in Portalalias table of database. This is unclear - why?
I deleted the record in table PortalALias corresponding to parent portal alias and now I launch copied DNN websites from МЫ цшtwiut aditional ado of editing the database first.
Now, where is the code that prevents such direct use of application name from browser Request ?
I just want to change the default name and its construction.
Similar questions about where is the code adding port numbers?