Hi!
Directory browsing was turned off in UltiDev version of Cassini as a security measure. Unfortunately you will not be able to use directory browsing.
The general suggested good practice is this: in most cases the difference between relative links behavior in IIS and Cassini is caused by user's (incorrect) assumption that the application will always run in a non-root virtual folder. The best way to verify if application's links are set correctly is to deploy your ASP.NET application in IIS root and see if links are working.
To work around your specific issue you could try a couple of things:
- Make "c:\dir1" your app's physical folder under Cassini, and launch the application using http://localhost:<port>/dir2/app.aspx. This will allow your application to reference upper-level folder in links if you need it.
- Update relative URLs in your app to make sure they don't go to levels above current application's location. For example, if you specified physical folder for your app as "c:\dir1\dir2", and you want page "c:\dir1\dir2\app.aspx" to have a link to a "c:\dir1\dir2\dir4\file.ext" file, then you should be able to use relative link like href='dir4/file.ext' or href='./dir4/file.ext'. If you use a link like href='/dir4/file.ext' with the leading forward slash - it may work in Cassini, but in IIS it will work if your app is in IIS root folder, because leading "/" means "from the root of the web server" and thus points to different places depending whether or not your app is in the root (as it's usually in Cassini) or not (as it's usually in IIS).
Best regards,
UltiDev Team.
Please donate at
http://www.ultidev.com/products/Donate.aspx to help us improve our products.