jnapier
01-26-2006, 08:03 PM
I would just like to say that the strategy used by VisualBuild to locate project files for an asp.net project is very fragile. I think that you should derive a better strategy to locate the project files. I have 2 websites on differnet ports that have a home directory that is the same name. They point to different locations on disk.
The problem is Visual Build's strategy for locating the file. It appears that which ever web site comes first in the IIS metabase will be the one that is used without regard to any port specifications.
If my .sln file references http://localhost:120 it has no bearing on where visual build will look for the file if the there is an http://localhost:109 that maps to a folder with the same name as the one that http://localhost:120 is mapped because whichever site was created first will always match first.
The problem is Visual Build's strategy for locating the file. It appears that which ever web site comes first in the IIS metabase will be the one that is used without regard to any port specifications.
If my .sln file references http://localhost:120 it has no bearing on where visual build will look for the file if the there is an http://localhost:109 that maps to a folder with the same name as the one that http://localhost:120 is mapped because whichever site was created first will always match first.