M
moondaddy
I have a simple sample site I'm building in asp.net 2.0. I created a master
page and a default.aspx content page in the project's root directory. Then
I created a subfolder called content and added some aspx pages in the
'content' folder. when these pages were created I referenced the master
page so everything should be linked up OK. Now, back on default.aspx I
added a linkbutton and referenced one of the aspx pages in the 'content'
folder. When I run the project and click on that link button, I get the
error:
Cannot use a leading .. to exit above the top directory.
It seems odd that something as straight forward as this wont work. This
site will ultimately run on a shared server so I can't tweak IIS. I'm sure
there's million or so web sites under the same circumstance where they too
can't tweak IIS, but need to have content organized in various folders.
What's a good work-around for this?
btw: I saw some other similar postings and the response they got was to map
the url at runtime via code. This seems like a step backwards since MS is
boasting code reduction and RAD tools. Certainly, there must be a better
way...
page and a default.aspx content page in the project's root directory. Then
I created a subfolder called content and added some aspx pages in the
'content' folder. when these pages were created I referenced the master
page so everything should be linked up OK. Now, back on default.aspx I
added a linkbutton and referenced one of the aspx pages in the 'content'
folder. When I run the project and click on that link button, I get the
error:
Cannot use a leading .. to exit above the top directory.
It seems odd that something as straight forward as this wont work. This
site will ultimately run on a shared server so I can't tweak IIS. I'm sure
there's million or so web sites under the same circumstance where they too
can't tweak IIS, but need to have content organized in various folders.
What's a good work-around for this?
btw: I saw some other similar postings and the response they got was to map
the url at runtime via code. This seems like a step backwards since MS is
boasting code reduction and RAD tools. Certainly, there must be a better
way...