Wednesday, January 23, 2013, 02:49 PM - WPFI use the FluidMoveBehavior in .NET 4 for animating the movement of an item between two different ItemsControls. In WPF however the behavior is not always what you expect, since the item sometimes first visible ends up in the target ItemsControl before the actual animation kicks in.
This is a bug in the behavior when used in WPF and here is a workaround until fixed!
Monday, June 11, 2012, 09:17 PM - WinRTFrustrated about getting this error message when trying to run/debug a Metro style application that worked just a few minutes ago? Well, some blog and forum posts suggest removing the bin and obj folders, but this did not work for me. I finally found out though, that the problem in my case was related to the prerelease NuGet package "MEF for web and Metro style apps".
The problem seems to be with the assembly bindings added to the app.config file. Removing the file completely solves the problem however! You will get compiler warnings of conflicting assembly versions, but at least it works! Until a better solution presents itself...
Friday, February 17, 2012, 09:19 AM - Code Style EnforcerCenito Software AB, the company I now work for, has acquired the rights for Code Style Enforcer. This is very good news since it hopefully means that there will be more time for improvements and new features.
Code Style Enforcer 3.5 is now here, and better than ever. A reworked and more flexible rule system is now in place, where it is possible to override rules for specific code types based on modifiers and visibility. For example, we might want some specific name rule for parameters marked as ref or out, or we require public visibility on static methods, but any visibility on instance methods.
A new default name rule override has been added to the standard rules, namely that methods marked with the async keyword must have “Async” as suffix.
Please give this new version a try and let me know if there are any issues with this new rule system, or any other issues for that matter.
Be sure to use DXCore 11.2.7 or later, since the new rule system is dependent on this release.
• A redesigned and more flexible rule system supporting more granular name and visiblity rules based on not only the code type, but also on modifiers and visibility.
• The separate rule configurator application has been removed and both local and global rule configurations can now be made within Visual Studio instead (Tools menu --> Code Style Enforcer). This also solves the problem where the configurator application stopped working for each new release of DXCore.
• Code rules can now be saved upon change even if rule files have become readonly, e.g. by using TFS in offline mode.
• Due to changes in the code rule definitions, any old customized code rules will get backed up and the new default rules will instead be loaded, when opening the Global Code Rules Options dialog in Visual Studio or a previously Code Style Enforcer activated solution.
Download Code Style Enforcer 3.5.17
Wednesday, July 13, 2011, 06:09 AM - Windows Phone 7I recently upgraded my Windows Phone 7.0 project to 7.1 (Mango), by simply changing the Target Windows Phone Version setting in project properties.
After that I wanted to utilize the SavePictureToCameraRoll feature, but this call always throw an InvalidOperationException simply stating, "An unexpected error has occured.".
Trying the same thing in a new project worked like a charm, so after some digging and file comparisons I found that the WMAppManifest.xml file is not "upgraded" when changing the target version to 7.1, and in order to be able to call this method the ID_CAP_ISV_CAMERA capability must be added.
I hope this can save someone else's time!
Sunday, July 10, 2011, 08:19 PM - Code Style EnforcerCode Style Enforcer 3.0.72 rebuilt against new version of DXCore 11.1.5.
Download Code Style Enforcer 3.0.72