http://www.dotnetnuke.com/tabid/795/Default.aspxDiscussions of the DotNetNuke core framework.enCommunityServer 2007 SP1 (Build: 20510.895)http://forums.asp.net/thread/1072379.aspxWed, 05 Oct 2005 11:24:18 GMT4c671506-2930-414c-a40b-8bf57ded5924:1072379djbaldwin0http://forums.asp.net/thread/1072379.aspxhttp://forums.asp.net/commentrss.aspx?SectionID=97&PostID=1072379Right Click on Build Support, select properties, then click on the Configuration Manager.&nbsp; Uncheck everything but Build Support and your project.<BR><BR>Start DotNetNuking!<BR><BR>Edit and continue means that you don't have to restart the project like VS 2003, you can edit and continue like VB 6.<BR><BR>I hope this is of some help to you.http://forums.asp.net/thread/1072233.aspxWed, 05 Oct 2005 07:58:07 GMT4c671506-2930-414c-a40b-8bf57ded5924:1072233Espen0http://forums.asp.net/thread/1072233.aspxhttp://forums.asp.net/commentrss.aspx?SectionID=97&PostID=1072233<P>When developing a new module, any change in the code results in <STRONG><EM>all</EM></STRONG> dlls being reloaded/recompiled by DotNetNuke.<BR><BR>Is there any way&nbsp;I can force IIS /&nbsp;ASP / DNN to only update the modified DLL?&nbsp;<BR>(IE: Keep all the dotnetnuke dll's, and only update the MyCompany.*.dll )<BR><BR>What about the edit and continue feature of VS2005 - will this solve the problem?<BR><BR>My current setup&nbsp;really slows down the development process...<BR><BR>Any feedback appreciated</P>