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
Thursday, July 7, 2011, 12:29 PM - Code Style EnforcerCode Style Enforcer 3.0.71 rebuilt against new version of DXCore 10.2.9.
Download Code Style Enforcer 3.0.71
Thursday, July 7, 2011, 07:26 AM - GeneralWe use Mercurial and TeamCity as CI server and have been experiencing some problems lately when developers are pushing Hg change-sets to the server when a build is in progress. The problem is that TeamCity first pulls and updates before starting the build and then during the build some files are generated and/or updated, like help files and version files (but also the .hgtags file). Then as the final step in the build process when it’s time for TeamCity to commit and push the changes there will be a problem if a new push has been made since the start of the build process, i.e. we will get an error message like "push creates new remote heads".
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!
Monday, March 7, 2011, 09:12 PM - Code Style EnforcerCode Style Enforcer 3.0.51 rebuilt against new version of DXCore 10.2.5.
Download Code Style Enforcer 3.0.51