Welcome to Windows Presentation Foundation (WPF)
Top Tasks :

WPF Community Bloggers

Tuesday, September 04, 2007 - Posts

  • Helping us to code MbUnit

    I want to extend my thanks to the following commerical software projects who have donated a license to each member of the MbUnit team to aid in it's development. JetBrains for the Resharper 3.0 License. Patrick for the NDepend License . Jamie for the TD.Net License . R# and TD.Net need little introduction and indeed NDepend is fast becoming a hot tool. I've only just started putting NDepend to use and the tool blows me away, CQL is a very, very powerful way of adjusting queries across the various metrics that are produced in your code. Patrick is also a nice guy and really knows his stuff, I look foward to seeing how we can worth with Patrick in the future. Read More...
  • MbUnit 2.4.1

    The MbUnit 2.4.1 release was released tonight , this adds some bug fixes and additional functionality on the 2.4.release. In full the following was fixed or added in this release. Bug [ MBUNIT-97 ] - Assembly setup method run after test suites are generated [ MBUNIT-108 ] - Test setup and teardown methods are not run for every execution of a repeated test [ MBUNIT-113 ] - SetUp and TearDown methods not executed for each test in a ProcessTestFixture [ MBUNIT-116 ] - .mbunit project files not associated by Windows to MbUnit GUI [ MBUNIT-126 ] - Assert.AreEqual() should support arrays the way NUnit does [ MBUNIT-128 ] - DirectoryNotFoundException when application exists [ MBUNIT-129 ] - The Assert.Greater overloads behave differently [ MBUNIT-132 ] - GenericAssert.FailIsEmpty & FailIsNotEmpty use the unformatted message [ MBUNIT-134 ] - ThreadedRepeat attribute cause high cpu utilization. [ MBUNIT-146 ] - Problem with AreNotEqual and object[] [ MBUNIT-147 ] - Remove assemblies... menu Read More...
  • xbap distributions problems might be local usersettings related

    Monday morning, our application went live!! Hooray!! All seems to be going well, although one user had problems when starting the application: System.Windows.Markup.XamlParseException: Cannot convert string '0,0' in attribute 'StartPoint' to object of type 'System.Windows.Point'. Premature string termination encountered. Error at object 'LinearGradientBrush_1' in markup file 'PresentationUI;V3.0.0.0;31bf3856ad364e35;component/installationprogress.xaml'. ---> System.InvalidOperationException: Premature string termination encountered. The problem occured even before our application had downloaded. Notice the component/installationprogress.xaml: That's not ours, but belongs to the framework. I have seen these problems from time to time. We tried to fix it by re-installing the framework. (Sometimes, people have 6.715 instead of 6.920). That didn't work. In the end, we simply had to discard the users profile. I made a copy of the profile, so maybe I'll find the time to look into the issue Read More...
  • Let's have some co-op

    Phils latest point is a cracker . Microsoft cannot for a lot of reasons bundle OSS and if they do what harm would it pose to OSS projects left out in the cold. If Microsoft had chosen to not write its own test framework, I fear they would have chosen NUnit over MbUnit simply because it’s more well known or for political reasons. Such a choice would have the potential to hurt a project like MbUnit in the never ending competition for users and contributors. It's worth adding that Charlie and the NUnit guys and me and the MbUnit team are not in this to out do each other. Each project treads a different path and while we have some goals that are the same, each project has different paths. If nothing else the two teams are looking to co-op more on things such as reporting formats to make life easier for our users and applying the frameworks to CI tools etc. A bundle of this kind would have adverse effects on the MbUnit user base as much as a MbUnit bundle would damage NUnit, ZaneBug and CsUnit. Read More...
  • Real-World WPF Start Time Perf Tip - Delay Setting the DataContext

    .NET applications traditionally suffer from slower startup time than native applications, caused by the time to load the .NET framework DLLs, JIT time etc. WPF applications have further things that can slow down cold start-time, the extra PresentationCore, PresentationFramework and WindowBase assemblies that need to be loaded and the start-up of the PresentationFontCache service. Any tips to help improve start time is therefore most welcome. Doug Stockwell recently released an updated version (v1.6 build 2802) of his free RikReader WPF-based RSS Reader, with considerably-improved start time. I've been using RikReader as my primary RSS reader since it was first released, and in previous versions the start time stood out as a blemish on an otherwise excellent app. The performance characteristics of older versions of RikReader were a little different to usual applications, in that the hot start-times were still quite bad (>10 seconds for my list of a couple of hundred feeds), whereas the Read More...

Copyright © 2006 Microsoft Corporation. All Rights Reserved. | Terms of Use | Privacy Statement | Contact Us