Ah I see,
Based on this explanation
"
2) All files contained within the project are defined within a project file
(as well as the assembly references and other project meta-data settings).
Files under the web's file-system root that are not defined in the project
file will not be logically considered part of the web project. You will
also now be able to define classes and types anywhere in the project
structure (there is no longer a need to define them under app_code).
"
since the project file is back with the ASP.NET Web project, I'd understand
that it would be so.
--
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
http://blogs.aspadvice.com/joteke
I'd understand that yes
"Mark Rae" <(E-Mail Removed)> wrote in message
news:ePT4J1A$(E-Mail Removed)...
> "Teemu Keiski" <(E-Mail Removed)> wrote in message
> news:es8LTyA$(E-Mail Removed)...
>
>> Hmm...isnt that what they fixed for the VS2005 RTM, where you can exclude
>> files from a project (which was broken in beta 2?
>
> In the release version if you exclude a file such as Web.config, it gets
> renamed to Web.config.exclude, so the whole thing stops working.
>
> In VSNET2003, you excluded a file so that it wouldn't get deployed with
> the solution every time - e.g. images, PDFs etc - but they were not
> renamed so that the project would still continue to work because the files
> themselves were still physically on the hard disk...
>