joe_pool_is
Well-known member
In my ASP.NET projects, I use relative paths.
This works for me because I code and test my websites locally, then once they are ready to implement, I FTP them over to our remote server.
Visual Studio hates this, though! It refuses to compile my web application because anything with "../" gets lost. It wants the fully qualified name:
"C:\Documents and Settings\jpool\My Documents\Web Projects\Website500\images\blue.gif"
That may work fine for testing my application at my desk, but whenever I FTP it to the server, that obviously wont work.
Is there a way I can slap Visual Studio so that it will understand the basics that were derived years ago? Maybe there is a setting somewhere burried under the Options menu?
Code:
<a href="../images/blue.gif" alt="">Example</a>
Visual Studio hates this, though! It refuses to compile my web application because anything with "../" gets lost. It wants the fully qualified name:
"C:\Documents and Settings\jpool\My Documents\Web Projects\Website500\images\blue.gif"
That may work fine for testing my application at my desk, but whenever I FTP it to the server, that obviously wont work.
Is there a way I can slap Visual Studio so that it will understand the basics that were derived years ago? Maybe there is a setting somewhere burried under the Options menu?