tag:blogger.com,1999:blog-9023944205100803414.post917529186764974009..comments2010-03-11T11:07:19.073-08:00Jeff Brownhttp://www.blogger.com/profile/09075745057339916352noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-9023944205100803414.post-92010463507047252072009-12-18T10:20:34.407-08:002009-12-18T10:20:34.407-08:00@Jeff<br />Well, I do have many things I would like to share, but alas! My time does not belong to me. Not now, at least...markellhttp://www.blogger.com/profile/00249008025035595944noreply@blogger.comtag:blogger.com,1999:blog-9023944205100803414.post-31291706093403927232009-12-16T01:11:14.440-08:002009-12-16T01:11:14.440-08:00@markell<br />PostSharp is indeed very cool. :)<br /><br />Why not start your own blog and post the sample there? I&#39;ll bet you have more things you&#39;d like to talk about. Alternately, you could post the sample to CodeProject.com or a similar site.Jeff Brownhttp://www.blogger.com/profile/09075745057339916352noreply@blogger.comtag:blogger.com,1999:blog-9023944205100803414.post-49174449473201678332009-12-16T00:09:24.734-08:002009-12-16T00:09:24.734-08:00Hi Jeff. Do you know about the PostSharp project? It is a very cool thing. Anyway, the reason I mention is because the PostSharp author - Gael Fraiteur has created a custom build task GenerateXmlSerializers which I find much more convenient then invoking SGen. We have the source code of PostSharp so I took the liberty of reusing this task for our purposes. Naturally, when the source code be licensed I will have to obtain a suitable license from Gael. Anyway, I would like to post an msbuild sample code to show how the task is used - where can I do so?markellhttp://www.blogger.com/profile/00249008025035595944noreply@blogger.comtag:blogger.com,1999:blog-9023944205100803414.post-6191422156644774252009-11-12T16:39:37.595-08:002009-11-12T16:39:37.595-08:00Please use the mbunit-user mailing list for questions like this.<br /><br />The new type in MbUnit v3 is Gallio.Framework.Assertions.AssertionFailureException.<br /><br />However, it is generally a bad idea to catch assertion exceptions. In some cases the assertion may already have been logged so catching the exception still results in a failure being seen in the report. What are you trying to test? (Please reply on mbunit-user.)Jeff Brownhttp://www.blogger.com/profile/09075745057339916352noreply@blogger.comtag:blogger.com,1999:blog-9023944205100803414.post-85222852247214462622009-11-12T13:27:20.431-08:002009-11-12T13:27:20.431-08:00Hi, I am having problem migrating my code from MbUnit 2 to MbUnit 3. Obviously, MbUnit 3 does not have exception handler like <br />catch(MbUnit.Core.Exceptions.AssertionException e){throw e;}<br />what&#39;s the corresponding exception assertion in MbUnit3?<br />ThanksChine June 2008http://www.blogger.com/profile/05839015018305601395noreply@blogger.com