http://blogs.msdn.com/b/bethmassi/archive/2009/12/15/migrating-an-outlook-client-to-net-framework-4-in-visual-studio-2010.aspxEarly this year we built a business application for order management for Northwind Traders on the Office and SharePoint platform using Visual Studio 2008 and Office &amp; SharePoint 2007. If you missed them: Architecture of the Northwind Officeen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/bethmassi/archive/2009/12/15/migrating-an-outlook-client-to-net-framework-4-in-visual-studio-2010.aspx#9939657Mon, 21 Dec 2009 17:05:38 GMT91d46819-8472-40ad-a661-2c78acb4018c:9939657Beth Massi<p>Hi Jake,</p> <p>The issue is with any migrated projects into Visual Studio 2010. So the fix is the same regardless of the target. Recreate the project (select the target framework you want) and add your existing files into it. This is fixed for RTM. </p> <p>HTH,</p> <p>-B</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9939657" width="1" height="1">http://blogs.msdn.com/b/bethmassi/archive/2009/12/15/migrating-an-outlook-client-to-net-framework-4-in-visual-studio-2010.aspx#9939391Mon, 21 Dec 2009 02:22:13 GMT91d46819-8472-40ad-a661-2c78acb4018c:9939391Jake Ginnivan<p>That is one annoying bug (wrong language when adding new items).. is there a workaround have it targeting .net 3.5 still?</p> <p>I am running Office 2010 but want to target office 2007, which works, until I close the solution then I cannot add anything :(</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9939391" width="1" height="1">