Wlecome to the land outside the box.
In ASP.NET 2.0, MS has opted for a non-project website model. When you open
a site, it iterates through the directories and finds everything. The only
possible way I can think of to circumvent this (have not tested the idea) is
to dink with the solution file, as that is where info that used to be in the
project file is now stored (not all information, just the bits that are
absolutely necessary). I am not confident anything WAS left in the solution
file to exclude.
Another option is to purposefully exclude the virtual directory bits (which
is in the solution). The issue here is it renames the files to .exclude.
But, you could go through the discipline of running locally, exclude and
publish. Yes, this would be a pain, but it would work.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
*************************************************
Think outside of the box!
*************************************************
"Angelo Cook" <an********@earthlink.netwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...
how do you prevent the publishing of virtual directories in VS 2005.
I have been using VS2003 and developing websites for years. I have been
using virtual directories for images, icons, styles and scripts. Which in
dot net 1.1 and VS2003 when I copied or published my web sites the virtual
directories were ignored. Now I am trying to convert to VS2005 and dot
net 2.x and now my development environment now sees the virtual
directories and when I publish to my test site, which has the same virtual
directories set up, it insists on copying the files to actual directories.
I know I am missing somthing here.
