https://www.infopathdev.com:443/forums/41.aspxIf you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/25529.aspxWed, 09 Jan 2008 22:21:14 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:25529Greg Collins0https://www.infopathdev.com:443/forums/thread/25529.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=25529<p>Maybe this article will help:</p> <p><strong>Visual Studio Debugging: &quot;Unable to Attach to Application&quot; Error<br /></strong><a href="http://www.infopathdev.com/blogs/greg/archive/2005/03/29/Visual-Studio-Debugging_3A00_-_2200_Unable-to-Attach-to-Application_2200_-Error.aspx">http://www.infopathdev.com/blogs/greg/archive/2005/03/29/Visual-Studio-Debugging_3A00_-_2200_Unable-to-Attach-to-Application_2200_-Error.aspx</a></p>https://www.infopathdev.com:443/forums/thread/25520.aspxWed, 09 Jan 2008 21:41:23 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:25520abcolson0https://www.infopathdev.com:443/forums/thread/25520.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=25520<p>Does anybody know why InfoPath 2003 (a .Net 1.1 application) defaults to using the most recent .Net version installed like an ASP.NET application does?</p> <p>This is the behavior I am seeing.&nbsp; I am developing a manged code form in Visual Studio C# 2003.&nbsp; Rules are not working and neither are defaults after a recent installation of .Net 2.0/3.0.&nbsp; After using ProcessExplorer and FusLogVW I see that after installing the .Net 2.0/3.0 upgrades InfoPath defaults to using the&nbsp;.Net 2.0 framework.&nbsp; Can anyone explain this?</p> <p>Tony</p>