<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://forums.asp.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>VS 2005 Web Application Projects</title><link>http://forums.asp.net/1019.aspx</link><description>General discussions of VS 2005 Web Application Projects</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>Re: Debugging a project in a mutiple project/single solution application</title><link>http://forums.asp.net/thread/1539930.aspx</link><pubDate>Fri, 19 Jan 2007 18:41:37 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1539930</guid><dc:creator>ranganh</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1539930.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=1019&amp;PostID=1539930</wfw:commentRss><description>&lt;p&gt;Hi Jalan,&lt;/p&gt;
&lt;p&gt;Fortunately or Unfortunately, it wont work that way.&amp;nbsp; Whenever someone is editing a project, they must ensure that they dont check in until it builds fine completely at their end.&lt;/p&gt;
&lt;p&gt;The corollary is, the source safe data must always&amp;nbsp;contain a working (building) project DLL which when referenced doesnt produce errors.&amp;nbsp; The&amp;nbsp;fortunate part I mentioned is that, people take care before checking-in their code and&amp;nbsp;minimize erraneous check-ins.&lt;/p&gt;
&lt;p&gt;The unfortunate part is, people always need to take latest version before building it themselves so that, they always have a working referenced DLL in their local machine.&lt;/p&gt;
&lt;p&gt;So the summary is, have a working DLL version checked in to source safe and ensure everybody take latests version of all projects (layers?)&amp;nbsp;before trying to build.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Hope this helps.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item><item><title>Debugging a project in a mutiple project/single solution application</title><link>http://forums.asp.net/thread/1539728.aspx</link><pubDate>Fri, 19 Jan 2007 16:09:00 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1539728</guid><dc:creator>Jalan</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1539728.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=1019&amp;PostID=1539728</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We&amp;nbsp;have an asp.net web application (VS 2005)&amp;nbsp;that multiple developers&amp;nbsp;are working on.&amp;nbsp; Inside of our solution we have many projects.&amp;nbsp; Some of these projects have Project References to some of the other projects in the solution.&amp;nbsp; The problem we run into is that when you go to&amp;nbsp;run a project (Project A)&amp;nbsp;with a reference to another project (Project B)&amp;nbsp;and the referenced project contains an error, it will not let you&amp;nbsp;run it.&amp;nbsp; Is there anyway to have&amp;nbsp;it set up so that Project A can build even if Project B is being edited and contains a coding error while still using a Project Reference?&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks in Advance&amp;nbsp;&amp;nbsp; &lt;/p&gt;</description></item></channel></rss>