project setup strategy

[EO]

I have an existing site with 1,500+ .htm pages to convert to .net.

Problem: The entire (non .net) site is currently at the root level of the
web for both development and production. However, asp.net/visual studio
insists on virtual directories. But a multitude of links in the existing
site are root relative links. So images and css files don't load when I look
at the page (through a browser or vs.net) in a virtual folder.

I have the application set to disable partent paths. That doesn't help.

I have no problem with writing the .net code to reference ~/path to get
application root relative addressing, which makes the dot net pages happy on
both development & production. I still can't get meatball html to display
root relative images on my development virtual web.

What to do?

-Ernest Ostrander

[Ken Cox [Microsoft MVP]]

Is this article of any help?
How To Create or Open a Visual Studio .NET Project in the Root Web

"Visual Studio .NET provides a new way to create and open a project that is
located in the root Web. This article describes this new procedure. As in
Microsoft Visual InterDev 6.0, it is convenient to create and open a project
in the root Web when you are working with Web applications that serve as the
root of a Web server. The pages for the application are stored in the root
Web and in the subdirectories of the root Web, but they are not stored in
subWebs. "

http://support.microsoft.com/default...b;en-us;303845

"EO" <[e-mail]> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

I have an existing site with 1,500+ .htm pages to convert to .net.

Problem: The entire (non .net) site is currently at the root level of the
web for both development and production. However, asp.net/visual studio
insists on virtual directories. But a multitude of links in the existing
site are root relative links. So images and css files don't load when I
look at the page (through a browser or vs.net) in a virtual folder.

I have the application set to disable partent paths. That doesn't help.

I have no problem with writing the .net code to reference ~/path to get
application root relative addressing, which makes the dot net pages happy
on both development & production. I still can't get meatball html to
display root relative images on my development virtual web.

What to do?

-Ernest Ostrander