<?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>Windows Azure Storage Client Library 2.0 Breaking Changes &amp; Migration Guide</title><link>http://blogs.msdn.com/b/windowsazurestorage/archive/2012/10/29/windows-azure-storage-client-library-2-0-breaking-changes-amp-migration-guide.aspx</link><description>The recently released Windows Azure Storage Client Library for .Net includes many new features, expanded platform support, extensibility points, and performance improvements. In developing this version of the library we made some distinct breaks with</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Windows Azure Storage Client Library 2.0 Breaking Changes &amp; Migration Guide</title><link>http://blogs.msdn.com/b/windowsazurestorage/archive/2012/10/29/windows-azure-storage-client-library-2-0-breaking-changes-amp-migration-guide.aspx#10415989</link><pubDate>Fri, 03 May 2013 19:57:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10415989</guid><dc:creator>Monilee Atkinson</dc:creator><description>&lt;p&gt;To answer Stephen B: &lt;/p&gt;
&lt;p&gt;The storage client libraries were updated to use the native MD5 implementation provided by advapi32.dll which is FIPS compliant, whereas the default implementation available in .Net is not certified. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;For more information about Windows Azure Compliance see: &lt;a rel="nofollow" target="_new" href="http://www.windowsazure.com/en-us/support/trust-center/compliance/"&gt;www.windowsazure.com/.../compliance&lt;/a&gt;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10415989" width="1" height="1"&gt;</description></item><item><title>re: Windows Azure Storage Client Library 2.0 Breaking Changes &amp; Migration Guide</title><link>http://blogs.msdn.com/b/windowsazurestorage/archive/2012/10/29/windows-azure-storage-client-library-2-0-breaking-changes-amp-migration-guide.aspx#10415442</link><pubDate>Wed, 01 May 2013 17:47:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10415442</guid><dc:creator>Stephen B</dc:creator><description>&lt;p&gt;When you say &amp;quot;The default MD5 behavior has been updated to utilize a FIPS compliant implementation&amp;quot; can you provide a reference to what is now being used? Or can you point me to a resource that defines what components of Azure are or are not FIPS 140-2 compliant?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10415442" width="1" height="1"&gt;</description></item><item><title>re: Windows Azure Storage Client Library 2.0 Breaking Changes &amp; Migration Guide</title><link>http://blogs.msdn.com/b/windowsazurestorage/archive/2012/10/29/windows-azure-storage-client-library-2-0-breaking-changes-amp-migration-guide.aspx#10375130</link><pubDate>Thu, 06 Dec 2012 06:22:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10375130</guid><dc:creator>Serdar Ozler</dc:creator><description>&lt;p&gt;CloudBlobClient.ListBlobsWithPrefix has been replaced with CloudBlobClient.ListBlobs&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10375130" width="1" height="1"&gt;</description></item><item><title>re: Windows Azure Storage Client Library 2.0 Breaking Changes &amp; Migration Guide</title><link>http://blogs.msdn.com/b/windowsazurestorage/archive/2012/10/29/windows-azure-storage-client-library-2-0-breaking-changes-amp-migration-guide.aspx#10375128</link><pubDate>Thu, 06 Dec 2012 06:04:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10375128</guid><dc:creator>arun</dc:creator><description>&lt;p&gt;Has the ListBlobsWithPrefix method in the CloudBlobClient class been deprecated or replaced in this latest version?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10375128" width="1" height="1"&gt;</description></item><item><title>re: Windows Azure Storage Client Library 2.0 Breaking Changes &amp; Migration Guide</title><link>http://blogs.msdn.com/b/windowsazurestorage/archive/2012/10/29/windows-azure-storage-client-library-2-0-breaking-changes-amp-migration-guide.aspx#10373911</link><pubDate>Mon, 03 Dec 2012 03:57:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10373911</guid><dc:creator>Andrew</dc:creator><description>&lt;p&gt;Any feedback regarding the CloudDrive library being updated to 2.0?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10373911" width="1" height="1"&gt;</description></item><item><title>re: Windows Azure Storage Client Library 2.0 Breaking Changes &amp; Migration Guide</title><link>http://blogs.msdn.com/b/windowsazurestorage/archive/2012/10/29/windows-azure-storage-client-library-2-0-breaking-changes-amp-migration-guide.aspx#10367003</link><pubDate>Thu, 08 Nov 2012 18:47:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10367003</guid><dc:creator>Shailesh</dc:creator><description>&lt;p&gt;The Diagnostics in SDK 1.8 still has a reference to Storage library 1.7, so for all practical purposes need to continue to hold a reference to Storage 1.7 library as well.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10367003" width="1" height="1"&gt;</description></item><item><title>re: Windows Azure Storage Client Library 2.0 Breaking Changes &amp; Migration Guide</title><link>http://blogs.msdn.com/b/windowsazurestorage/archive/2012/10/29/windows-azure-storage-client-library-2-0-breaking-changes-amp-migration-guide.aspx#10365591</link><pubDate>Sun, 04 Nov 2012 05:10:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10365591</guid><dc:creator>Jai Haridas</dc:creator><description>&lt;p&gt;Our client library is signed but not GAC&amp;#39;d - so that should allow you to GAC.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10365591" width="1" height="1"&gt;</description></item><item><title>re: Windows Azure Storage Client Library 2.0 Breaking Changes &amp; Migration Guide</title><link>http://blogs.msdn.com/b/windowsazurestorage/archive/2012/10/29/windows-azure-storage-client-library-2-0-breaking-changes-amp-migration-guide.aspx#10365442</link><pubDate>Sat, 03 Nov 2012 01:31:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10365442</guid><dc:creator>Signed Assemblies</dc:creator><description>&lt;p&gt;I&amp;#39;m trying to use the assemblies from a SSIS scripting task. &amp;nbsp;Any referenced assembly must be GACd. &amp;nbsp;Any chance you will release signed assemblies?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10365442" width="1" height="1"&gt;</description></item></channel></rss>