http://joel.fjorden.se/index.php http://joel.fjorden.se/index.php?entry=entry110713-060945
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!]]> http://joel.fjorden.se/index.php?entry=entry110710-201944
Download Code Style Enforcer 3.0.72]]> http://joel.fjorden.se/index.php?entry=entry110707-122916
Download Code Style Enforcer 3.0.71]]> http://joel.fjorden.se/index.php?entry=entry110707-072634
One solution to this is of course to pull, update, merge (if needed) and commit, or the Hg Fetch extension, but what we really wanted was to somehow prevent developers to push change sets into the remote server repository during the build process of that specific project in TeamCity.

After quite a lot of research on Google, I still couldn’t find any existing solution to this, so I started thinking about how we could manage this ourselves. The solution I came up with was to develop a very simple, but yet quite smart, REST service hosted on the same machine as the Hg repositories. The service exposes endpoints for EnablePush/DisablePush together with the name of the target repository. What the service implementation does is then to temporarily change the hgrc file in the repository to disable push, but not for everyone, since the automated build account used by TeamCity for Mercurial still needs Push access (allow_push = Mercurial). In order to enable Push again when the build is completed we then allow everyone with an account in the AD to Push again (allow_push = *).

In order to use the REST service from TeamCity I discovered a very useful plugin called tcWebHooks that allows HTTP POST on TeamCity events like build started and build completed. Here is a configuration example of tcWebHooks for enabling/disabling Hg Push for a specific project and repository using the custom made RIA service.

If you’re interested in the service install package or source code, let me know and I’ll send it to you!]]> http://joel.fjorden.se/index.php?entry=entry110307-211205
Download Code Style Enforcer 3.0.51]]> http://joel.fjorden.se/index.php?entry=entry101212-194531
Download Code Style Enforcer 3.0.43]]> http://joel.fjorden.se/index.php?entry=entry101209-070453
There seems to be some incompatibility issue with this new version of DXCore, but a new version of Code Style Enforcer targeting DXCore 2010 vol 2.3 will be released within the next couple of days!

]]> http://joel.fjorden.se/index.php?entry=entry101117-175156
Right now I'm looking into a more flexible code rule system, where it should be possible to fine tune rules based on a combination of code type (field, method, etc.), visibility (public, private, etc.) and keyword (static, readonly, const, virtual, etc.).

My thought is that it should also be possible to choose the current standard, and easier, configuration of name rules, but that it also should be possible to specify custom regular expressions, probably resulting in the loss of automatic name corrections or suggestions.

The other relatively large implementation feature is to enable Code Style Enforcer to enforce the rules during MSBuild, either inside Visual Studio or through the command-line, e.g. automatic build server. Inside Visual Studio the violations will be added to the Error List tool window as either warnings or errors depending on configuration.

I think and hope these features are something you all have use for, but please let me know if anything else comes to your mind. ]]> http://joel.fjorden.se/index.php?entry=entry101021-204718
Code Style Enforcer 3.0.32 requires the latest version of DXCore, that is 10.1.7.

New Features

• New UI for configuring code rules, utilizing grids to get a uniform view for all different rule types while also making the configuration easier to extend for a future and more flexible rule system.

• Code rules, for a specific solution, are now configurable from within Visual Studio 2010, through Code Style Enforcer -> Properties from the solution node's context menu in the Solution Explorer.

• Code Style Enforcer Configurator converted to a WPF application using the new rule configuration pages.

• Possible to configure different interface implementation rules for properties, methods and events.

Bug Fixes

• Probable prefix, in a name rule violation, was not removed from name when automatically suggesting a new name.

• Loading the default rules did not work when the local rules were the same as the global rules, i.e. the global rules were linked into the solution.

Breaking Changes

• Due to changes in the code rule definitions, any old customized code rules will get backed up and the default rules will instead be loaded, when opening Code Style Enforcer Configurator or a previously Code Style Enforcer activated solution.

Download Code Style Enforcer 3.0.32]]> http://joel.fjorden.se/index.php?entry=entry100901-154014
Code Style Enforcer 3.0.17 Beta

New Features

• Activation/Deactivation of Code Style Enforcer can now be done for the complete solution and for specific projects. The "Active" command is available from the context menu when right-clicking on the solution node or a project node in the Solution Explorer.

• Generate reports functionality added for generating an XML file containing all rule violations for the complete solution. Different XSL style sheets can then be used for a proper presentation of the data. The "Generate Report..." command is available from the context menu when right-clicking on the solution node in the Solution Explorer.

Bug Fixes

• Code Style Enforcer Configurator could crash when trying to save rules to a read-only location.

• The wrong violation description was presented for name rules where no prefix was allowed.

Known Issues (some missing features from the previous releases)

• No user interface for changing the code rules inside Visual Studio, but it can still be done using the Code Style Enforcer Configurator application or manually by editing the XML rule files.

Download Code Style Enforcer 3.0.17 Beta]]>