http://elegantcode.com/2010/01/03/comparing-bytes/?utm_source=rss&utm_medium=rss&utm_campaign=comparing-bytes Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://elegantcode.com/2010/01/03/comparing-bytes/comment-page-1/#comment-52365 Sean Timm Mon, 04 Jan 2010 07:42:29 +0000 http://elegantcode.com/2010/01/03/comparing-bytes/#comment-52365 True, Tim. In my case, I needed to do the comparison inside of production code, so shipping the test assemblies wouldn't be an option. :) Definitely the way to go for unit tests, though. True, Tim. In my case, I needed to do the comparison inside of production code, so shipping the test assemblies wouldn’t be an option. Definitely the way to go for unit tests, though.

]]> http://elegantcode.com/2010/01/03/comparing-bytes/?utm_source=rss&utm_medium=rss&utm_campaign=comparing-bytes Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://elegantcode.com/2010/01/03/comparing-bytes/?utm_source=rss&utm_medium=rss&utm_campaign=comparing-bytes Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://elegantcode.com/2010/01/03/comparing-bytes/comment-page-1/#comment-52365 Sean Timm Mon, 04 Jan 2010 07:42:29 +0000 http://elegantcode.com/2010/01/03/comparing-bytes/#comment-52365 True, Tim. In my case, I needed to do the comparison inside of production code, so shipping the test assemblies wouldn't be an option. :) Definitely the way to go for unit tests, though. True, Tim. In my case, I needed to do the comparison inside of production code, so shipping the test assemblies wouldn’t be an option. Definitely the way to go for unit tests, though.

]]> http://elegantcode.com/2010/01/03/comparing-bytes/comment-page-1/#comment-52365 Sean Timm Mon, 04 Jan 2010 07:42:29 +0000 http://elegantcode.com/2010/01/03/comparing-bytes/#comment-52365 True, Tim. In my case, I needed to do the comparison inside of production code, so shipping the test assemblies wouldn't be an option. :) Definitely the way to go for unit tests, though. True, Tim. In my case, I needed to do the comparison inside of production code, so shipping the test assemblies wouldn’t be an option. Definitely the way to go for unit tests, though.

]]> http://elegantcode.com/2010/01/03/comparing-bytes/?utm_source=rss&utm_medium=rss&utm_campaign=comparing-bytes Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://elegantcode.com/2010/01/03/comparing-bytes/comment-page-1/#comment-52365 Sean Timm Mon, 04 Jan 2010 07:42:29 +0000 http://elegantcode.com/2010/01/03/comparing-bytes/#comment-52365 True, Tim. In my case, I needed to do the comparison inside of production code, so shipping the test assemblies wouldn't be an option. :) Definitely the way to go for unit tests, though. True, Tim. In my case, I needed to do the comparison inside of production code, so shipping the test assemblies wouldn’t be an option. Definitely the way to go for unit tests, though.

]]> http://elegantcode.com/2010/01/03/comparing-bytes/comment-page-1/#comment-52362 Tim Van Wassenhove Mon, 04 Jan 2010 06:56:33 +0000 http://elegantcode.com/2010/01/03/comparing-bytes/#comment-52362 Atleast MSTEST and NUnit have a class CollectionAssert with an AreEqual method which does teh following: Verifies that specified collections are equal. Two collections are equal if they have the same elements in the same order and quantity. Elements are equal if their values are equal, not if they refer to the same object. Atleast MSTEST and NUnit have a class CollectionAssert with an AreEqual method which does teh following: Verifies that specified collections are equal. Two collections are equal if they have the same elements in the same order and quantity. Elements are equal if their values are equal, not if they refer to the same object.

]]>