Thank you for posting.
Regarding on the ASP.NET2.0/VS 2005 's project reference problem, it is
due to the new projectless model for ASP.NET 2.0 application in VS 2005,
there is nothing you've missed. In the new projectless model, there is no
project file for ASP.NET 2.0 application and all the private referenced
assemlies are just put in the "bin" dir, there is not explicit reference
list on them. And for strong-named reference assemblies, they'll be
declared in the web.config's
<compilation><assemblies> .....</ > </> section....
So if you need to make sure your web application get the referenced
assemblies correctly, from source control, we need to keep the private
"bin" dir's content unchanged.
BTW, the ASP.NET dev team does provide a new project model which use the VS
2003 like project style, that still use procompiled main assemblies and
project file. It is still under beta preview, you can find it under the
#Visual Studio 2005 Web Application Projects (RC1)
Hope this helps.
Microsoft Online Community Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no