Last post Apr 04, 2006 12:48 PM by johndund
Mar 30, 2006 10:19 PM|dotNet_Student|LINK
Mar 31, 2006 02:07 AM|ScottGu|LINK
By default the \bin directory isn't there for web application until you publish or deploy one. You can do this by choosing the Build->Publish Web Site option.
Hope this helps,
Mar 31, 2006 02:08 AM|StrongTypes|LINK
To generate an assembly from within Visual Studio 2005, like you did in Visual Studio .NET 2003, you'll need to download and install
Web Application Projects. You create a new website when creating a website and a project
when creating a project such as a class library or Windows application.
Mar 31, 2006 08:21 AM|dotNet_Student|LINK
Thanks Scott and Ryan. Does that mean that my source safe structure will change since we do not have a project file any more (for websites)?
Any articles on using VSS 6.0 with ASP.NET 2.0 will really be helpful. Thanks.
Apr 04, 2006 12:48 PM|johndund|LINK
Your SourceSafe structure shouldn't change too dramatically using either model. The main difference will be the lack of a project file inside your web site if you use the web site model. If you use file based web sites (not web application projects), your
web site will be added in a location relative to your solution (assuming it's on the same drive), so I would recommend having your solution underneath your web site. If you use local IIS webs, it shouldn't matter since they will be added in a non-relative
location regardless; they will be added right under the root of where you chose to add your solution.
One note: if you upgrade a VS2003 solution using either model, I would strongly recommend unbinding your solution (and all containing projects) from source control beforehand, and then re-adding them to a different location in your source control database
Hope this helps. Let me know if you have any more questions.