<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/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>Visual Studio 2010 solution build process give a warning about indirect dependency on the .NET Framework assembly due to SSIS references</title><link>http://blogs.msdn.com/b/jason_howell/archive/2010/08/18/visual-studio-2010-solution-build-process-give-a-warning-about-indirect-dependency-on-the-net-framework-assembly-due-to-ssis-references.aspx</link><description>Here’s how I saw the problem… Install SQL Server 2005. Afterwards, Install SQL Server 2008. (Integration Services or Management tools features are enough usually) Install your favorite new tool Visual Studio 2010. Create or Open a solution for your C#</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Visual Studio 2010 solution build process give a warning about indirect dependency on the .NET Framework assembly due to SSIS references</title><link>http://blogs.msdn.com/b/jason_howell/archive/2010/08/18/visual-studio-2010-solution-build-process-give-a-warning-about-indirect-dependency-on-the-net-framework-assembly-due-to-ssis-references.aspx#10385465</link><pubDate>Wed, 16 Jan 2013 10:22:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10385465</guid><dc:creator>Veeresh</dc:creator><description>&lt;p&gt;Warning	1	The following assembly has dependencies on a version of the .NET Framework that is higher than the target and might not load correctly during runtime causing a failure: AjaxControlToolkit, Version=4.1.60919.0, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e. The dependencies are: System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35; System.Web.Extensions.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35; System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089; mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089; System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089; System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089; System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089; System.Xml.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089; System.Core, Vers.... You should either ensure that the dependent assembly is correct for the target framework, or ensure that the target framework you are addressing is that of the dependent assembly.		&lt;/p&gt;
&lt;p&gt;---------------------------------------&lt;/p&gt;
&lt;p&gt;Y im gettig this Error&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10385465" width="1" height="1"&gt;</description></item><item><title>re: Visual Studio 2010 solution build process give a warning about indirect dependency on the .NET Framework assembly due to SSIS references</title><link>http://blogs.msdn.com/b/jason_howell/archive/2010/08/18/visual-studio-2010-solution-build-process-give-a-warning-about-indirect-dependency-on-the-net-framework-assembly-due-to-ssis-references.aspx#10363969</link><pubDate>Tue, 30 Oct 2012 11:53:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10363969</guid><dc:creator>Felice Pollano</dc:creator><description>&lt;p&gt;Thanks a lot, you and this other guy:&lt;a rel="nofollow" target="_new" href="http://pblee.net/post/2011/10/14/MicrosoftSqlServermsxml6_interopdll-cause-VS2010-cannot-compile-.aspx"&gt;pblee.net/.../MicrosoftSqlServermsxml6_interopdll-cause-VS2010-cannot-compile-.aspx&lt;/a&gt; saved my day. I think MS should provide some hotfix for replacing that dll with the beta framework linked in.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10363969" width="1" height="1"&gt;</description></item><item><title>re: Visual Studio 2010 solution build process give a warning about indirect dependency on the .NET Framework assembly due to SSIS references</title><link>http://blogs.msdn.com/b/jason_howell/archive/2010/08/18/visual-studio-2010-solution-build-process-give-a-warning-about-indirect-dependency-on-the-net-framework-assembly-due-to-ssis-references.aspx#10254087</link><pubDate>Fri, 06 Jan 2012 19:22:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10254087</guid><dc:creator>Jim Espaillat</dc:creator><description>&lt;p&gt;If you don&amp;#39;t have a clean installation of SQL 2008, and can&amp;#39;t spare a machine to make a new one, you can also use the SQL 2008 installation utility to get a fresh copy of Microsoft.SqlServer.msxml6_interop.dll&lt;/p&gt;
&lt;p&gt;You need to do the first two steps Jason outlines above to get rid of the existing 2005 copy of Microsoft.SqlServer.msxml6_interop.dll. &amp;nbsp;Then run the installation tool in repair mode (select &amp;quot;Maintenance&amp;quot;, then &amp;quot;Repair&amp;quot;). &amp;nbsp;When the tool prompts you for an instance, just select &amp;quot;shared features only&amp;quot; so it doesn&amp;#39;t take too long. &amp;nbsp;The repair tool won&amp;#39;t find an old copy of msxml6_interop.dll, so it will put a new (non-beta) copy into the GAC. &amp;nbsp;It will also put back the registry entry to protect the file, so you don&amp;#39;t have to restore the registry keys either (I deleted the one renamed in Step 1 once I verified everything was working)&lt;/p&gt;
&lt;p&gt;Everything compiled cleanly after that. &amp;nbsp;HTH&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10254087" width="1" height="1"&gt;</description></item><item><title>re: Visual Studio 2010 solution build process give a warning about indirect dependency on the .NET Framework assembly due to SSIS references</title><link>http://blogs.msdn.com/b/jason_howell/archive/2010/08/18/visual-studio-2010-solution-build-process-give-a-warning-about-indirect-dependency-on-the-net-framework-assembly-due-to-ssis-references.aspx#10149457</link><pubDate>Mon, 04 Apr 2011 10:44:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10149457</guid><dc:creator>Kavya</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve the latest version of Microsoft.SqlServer.Msxml6_interop dated 29/11/2010 18:17:26. it still doesn&amp;#39;t work. Can you please help?&lt;/p&gt;
&lt;p&gt;My scenarios is same as building against .net3.5 in vs2010. If I change it to .net4, it works. But I can&amp;#39;t change it due to business requirements. The Microsoft.SqlServerManagedDts version is 10.0.0.0 dated 10.06/12/2010 08:17:06.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10149457" width="1" height="1"&gt;</description></item><item><title>re: Visual Studio 2010 solution build process give a warning about indirect dependency on the .NET Framework assembly due to SSIS references</title><link>http://blogs.msdn.com/b/jason_howell/archive/2010/08/18/visual-studio-2010-solution-build-process-give-a-warning-about-indirect-dependency-on-the-net-framework-assembly-due-to-ssis-references.aspx#10142639</link><pubDate>Thu, 17 Mar 2011 14:33:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10142639</guid><dc:creator>Peter Alvin</dc:creator><description>&lt;p&gt;I solved the problem (for SQL Server 2005) by building my project against .Net version 4 instead of 2.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10142639" width="1" height="1"&gt;</description></item><item><title>re: Visual Studio 2010 solution build process give a warning about indirect dependency on the .NET Framework assembly due to SSIS references</title><link>http://blogs.msdn.com/b/jason_howell/archive/2010/08/18/visual-studio-2010-solution-build-process-give-a-warning-about-indirect-dependency-on-the-net-framework-assembly-due-to-ssis-references.aspx#10098397</link><pubDate>Tue, 30 Nov 2010 15:54:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10098397</guid><dc:creator>Excellent explanation of the issue.</dc:creator><description>&lt;p&gt;I&amp;#39;m a seasoned *nix programmer, but a mere babe in the MS world. This article has just saved me a LOT of time. Now I just need to find a machine with the &amp;#39;good&amp;#39; 2008 DLL on it, as all of ours, so far as I can tell, were upgraded from 2005 and therefore don&amp;#39;t have the DLL in the 100/Binn folder. Thanks &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10098397" width="1" height="1"&gt;</description></item><item><title>re: Visual Studio 2010 solution build process give a warning about indirect dependency on the .NET Framework assembly due to SSIS references</title><link>http://blogs.msdn.com/b/jason_howell/archive/2010/08/18/visual-studio-2010-solution-build-process-give-a-warning-about-indirect-dependency-on-the-net-framework-assembly-due-to-ssis-references.aspx#10069165</link><pubDate>Wed, 29 Sep 2010 09:21:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10069165</guid><dc:creator>Pietro</dc:creator><description>&lt;p&gt;Thank you! Your workaround made my day! My situation was slightly different: I had a Visual Studio 2008 project targeting .NET 3.5 which referenced a SSIS 2005 dll (Microsoft.SQLServer.ManagedDTS.dll version 9.0.242.0) and I have never installed SQL 2008. Migrating to Visual Studio 2010, I initially made it target the .NET 4.0 framework, but then decided to undo this change and the project wouldn&amp;#39;t compile anymore. I used the DLL linked in &lt;a rel="nofollow" target="_new" href="https://connect.microsoft.com/VisualStudio/feedback/details/551532/cannot-build-project-in-2010-when-project-has-reference-to-ssis-2008-dlls-sqltask-manageddts-etc?wa=wsignin1.0#details"&gt;connect.microsoft.com/.../cannot-build-project-in-2010-when-project-has-reference-to-ssis-2008-dlls-sqltask-manageddts-etc&lt;/a&gt; as the &amp;quot;good&amp;quot; one&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10069165" width="1" height="1"&gt;</description></item><item><title>re: Visual Studio 2010 solution build process give a warning about indirect dependency on the .NET Framework assembly due to SSIS references</title><link>http://blogs.msdn.com/b/jason_howell/archive/2010/08/18/visual-studio-2010-solution-build-process-give-a-warning-about-indirect-dependency-on-the-net-framework-assembly-due-to-ssis-references.aspx#10067227</link><pubDate>Fri, 24 Sep 2010 09:31:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10067227</guid><dc:creator>Richard</dc:creator><description>&lt;p&gt;Many thanks! Spent most of yesterday trying to sort this out, so very happy to find your solution. n.b. On my &amp;quot;good&amp;quot; install the dll wasn&amp;#39;t in ...\100\DTS\Binn, so I copied it out of the GAC instead. &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10067227" width="1" height="1"&gt;</description></item></channel></rss>