Steve Dunn's Blog

Announcing a new version of the Gleed 2D XNA tool

noreply@blogger.com (Steve Dunn) — Sun, 08 Jan 2012 19:35:00 +0000

I’ve spent some time over the Summer and Autumn of 2011 rewriting the Gleed 2D tool. This is a tool for editing levels for 2D games and is a very popular tool in the XNA community for games running on XBox and Windows Phone.

Most of the changes in the new version are under-the-hood. The biggest change has been to make it have a plug-in architecture. There has also been a few UI changes though; here’s some screen-shots.

The original tool before being re-written:

and here’s the new version:

The main reason for rewriting the tool was that I wanted to add more features to it but found that it wasn’t easy. It wasn’t easy because it was originally written to just handle the basics needed for creating and editing levels.

The features that I wanted to add were for the next version of my game (video here). I wanted to include lighting and shadows and I wanted to design these on the canvas.

Instead of shoe-horning my changes into the original Gleed 2D source, I decided it’d be best to rewrite it and change it to a plug-in based tool.

So, now everything is a plug-in. The basic shapes (rectangle, circle, path) and textures are now plug-ins. Lighting (lights and shadows) is now a plug-in. There’s also a plug-in for simple ‘behaviour’.

Here’s a quick video showing how to use the basic shapes and textures:

Basic shapes and textures

Here’s a short video showing lighting:

Lights and shadows

and lastly, here’s a short video showing simple behaviours:

Simple behaviours

The tool is still currently a bit rough. There’s various bugs that need to be fixed, but none of them stop the tool from doing what it was designed to do. The project is now quick big, so I’m hoping that the community will jump in and add/fix stuff. I’d like to see plug-ins for physics and particle systems.

Feel free to download the source and play around.

A fast way of converting C# enums to strings–and back again.

noreply@blogger.com (Steve Dunn) — Wed, 17 Aug 2011 21:45:00 +0000

I recently needed a fast way of converting lots of enums to strings (and back again). I needed to do it very quickly. ‘Enum.Parse’ just wasn’t fast enough.

I discovered there was no ‘enum mapper’ in C#, so I knocked up this little class. It uses reflection just once when it comes across a new enum.

It’s compatible with .NET 3.5 too.

Handy use of extension method on a bool

noreply@blogger.com (Steve Dunn) — Wed, 11 May 2011 19:41:00 +0000

I don’t like to overuse if/else statements. I really dislike seeing code like this:

if(somethingIsTrue)
{
  DoSomethingWhenTrue( ) ;
}
else
{
  DoSomethingElse( ) ;
}

I just had an idea about using extension methods so I can write this instead:

somethingIsTrue.Branch(
        ( ) => DoSomethingWhenTrue( ),
        ( ) => DoSomethingElse( ) ) ;

… and here’s the extension method:

public static void Branch(this bool @bool, Action left, Action right)
{
  if( @bool )
  {
    left( ) ;
  }
  else
  {
    right( ) ;
  }
}

Nice or not? I think it reads a bit better (for single line expressions anyway).

New version (2.5) of the Code Formatter Plug-in for Windows Live Writer

noreply@blogger.com (Steve Dunn) — Sun, 11 Jul 2010 13:13:00 +0000

A new version of my code formatter plug-in for Windows Live Writer can be found at http://tinyurl.com/3483vwh

Summon Method

noreply@blogger.com (Steve Dunn) — Wed, 14 Apr 2010 11:54:00 +0000

"Summon Method" A method that gets or creates something.

A common question (well, I've seen it asked a few times), is what should I call a method the gets or creates something? Instead of

Foo GetOrCreateFoo()

use:

Foo SummonFoo()

What do you think?

A tool to switch project files between using Visual Studio 2008 and 2010

noreply@blogger.com (Steve Dunn) — Thu, 25 Feb 2010 21:02:00 +0000

Update: the source is now on GitHub

Visual Studio 2010 is almost here. Visual Studio 2010 (the release candidate) is here.

I’ll describe the problem before I describe the tool: You want to use the latest version of Visual Studio but you don’t want it to modify all of your projects and solutions because you’ve got other team members who don’t want to (or can’t) switch to 2010.

A serious problem indeed. If only you could you run a tool to update all of you project files to 2010, do your changes in Visual Studio 2010, then switch all projects back to 2008 format before checking in.

Well, here’s a command line tool to do just that!

It’s very easy to use: run it from the command line, give it a folder name, and tell it whether you want all your projects and solutions under that folder to be either 2008 or 2010 format. For example:

SwitchVsVersion c:\temp\MySolution 2010
SwitchVsVersion c:\temp\MySolution 2008

As a bonus, you can also tell it to change all your target frameworks to either .NET 4 or .NET 3.5. For example:

SwitchVsVersion c:\temp\MySolution 3.5Framework
SwitchVsVersion c:\temp\MySolution 4.0Framework

Binary here. Source code here. Here’s a test solution with lots of different empty projects to try it out on too.

Disclaimer: this is a noddy little tool that may not work properly on your projects and solutions. I’ve tested it on quite a large WinForms solution and it worked fine. I’ve also tested it on quite a variety of projects including C# and VB WinForms, Web Apps, Libraries, WPF Projects, and WPF Libraries. The only one it doesn’t do is C++ projects (which is a coincidence, because I no longer do C++ projects either). Be sure to back up your stuff before you use this tool! Terms and conditions apply.

Update: Thanks for the feedback. As requested, the source is covered under the WTFPL. Do what you want with it:

DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE


This program is free software. It comes without any warranty, to the extent permitted by applicable law. You can redistribute it and/or modify it under the terms of the Do What The Fuck You Want To Public License, Version 2, as published by Sam Hocevar. See http://sam.zoy.org/wtfpl/COPYING for more details.

Updated: Code Formatter Plugin for Windows Live Writer

noreply@blogger.com (Steve Dunn) — Sat, 09 Jan 2010 20:07:00 +0000

This plug-in formats and highlights code. Version 2.0.0.3 can be downloaded here. Keep reading for more info.

As well as a few bug fixes, this release includes the following features:

· Use different formatting engines such as ActiPro (Insert formatted code), and SyntaxHighlighter (Insert highlighted code)
· Dozens of languages, including PowerShell, MSIL, Pascal and XAML
· Live formatting of code using the superb ActiPro code editor. ActiPro very kindly donated the license.
· The ability to output either highlighted text (html) or an image
· WordPress support for the SyntaxHighlighter Evolved plugin

This plugin adds four tools in WLW's tool window:

Tool 1) Code as bitmap

This uses the ActiPro formatting engine to take a snapshot of the code.

You'll see this screen when clicked – if there’s text in the clipboard, it’ll be shown here, or you can copy and paste when the window appears:

This srceen allows you to set the size of the editor window. You can either select common widths from the drop-down or put in your own width - for instance, 465 is the ideal width for my template on Blogger. The buttons on the bottom right allow you to then:

a) insert the image straight into the blog post or
b) have the plugin copy the image or
c) discard it.

The advantage of the option A is that the code is still editable in WLW; the disadvantage - you cannot [yet] apply bitmap effects, such as reflection or drop shadow.

The advantage of option B is that you can apply bitmap effects, but the disadvantage is that code will no longer be editable.

Tool B) Formatted code

This also uses uses the ActiPro formatting engine.

When inserting code, the plugin window will allow various properties of the code to be changed:

When clicking edit code, you'll see the edit source code screen:

Tool C) Highlighted code

This uses the Syntax Highlighter formatting engine. When inserting code, the edit screen will appear in the same way as when you insert formatted code (see above). The only difference is a ‘show preview’ button, which displays this preview window:

To use the SyntaxHighlighter engine, ensure your blog is correctly set-up. For the preview window to correctly display your code, ensure the Settings are correct. Here’s the Settings window:

Tool D) WordPress Formatted

This changes the HTML output to that expected by theSyntaxHighlighter Evolved plugin for WordPress. It’s very similar to using the SyntaxHighlighter engine, but you don’t need to worry about setting up your blog with the correct scripts. Do be aware though, that for the Preview window to work correctly, you still need to set-up this plugin so that it knows where the SyntaxHighlighter brushes and scripts are (the default settings work right now, but if Alex changes the location in the future, you’ll need to update the settings).

To see examples of the output, please see this blog post.

Version 2.0.0.3 can be downloaded here. To use it, extract the binaries to Program Files\Windows Live\Writer\Plugins and run WLW. If you're using a version of WLW prior to Beta 3, then you need to remove it and update! (alternatively, change the directory to \Program Files\Windows Live Writer\Plugins)

Thanks again to all those that left feedback. Please keep it coming. Hopefully the bugs that have been reported have now been fixed.

Problems with CSS and themes when using ASP.NET Forms Authentication

noreply@blogger.com (Steve Dunn) — Sat, 17 Oct 2009 19:25:00 +0000

A while back, I wrote a blog post about how turning on Forms Authentication caused problems with stylesheets and Themes. A lot of people found this post useful but had trouble finding it. One reader suggested I change the title to get more hits. So, I did, and this is it.

ReSharper for Visual Studio 2010

noreply@blogger.com (Steve Dunn) — Mon, 27 Jul 2009 19:48:00 +0000

I don’t know how I missed this for so long, but JetBrains have released a preview of ReSharper for Visual Studio 2010! They say this version is neither 4.5.1 nor 5.0, but a preview build with some of the new 5.0 features enabled.

Looking at the nightly builds, it seems that the first release was 9th July, but there was no news on their blog, which I’ve been checking daily since June (when they said it’d be ready).

Anyway, now I can give Visual Studio 2010 another try. I just couldn’t use it, not even for evaluation, without ReSharper!

Also, let’s not forget that version 4.5.1 for Visual Studio 2005 and 2008 is also now available.

Google Squared and sexy languages!

noreply@blogger.com (Steve Dunn) — Thu, 04 Jun 2009 06:24:00 +0000

Google Squared looks like an interesting tool.

“Google Squared is a search tool that helps you quickly build a collection of facts from the Web for any topic you specify.

Facts about your topic are organized as a table of items and attributes (we call them "Squares" for fun).

Customize these Squares to see just the items and attributes you're interested in.

See the websites that served as sources for the information in your Square.

Save and share Squares with others.”

There’s some interesting results. I searched for ‘programming languages’.

It displays a list of languages, a picture of the language, a description, and what it was influenced by.

I was very surprised to see the Miranda language (apparently influenced by Haskell). Try it yourself: scroll down to Miranda. I must take a closer look at this one!

Another one that might get you excited is Limbo. Scroll down and take a look (but be careful if you’re at work!!). Apparently influenced from Stackless Python. I’d say more like alcohol!

Updated: Tree Trim

noreply@blogger.com (Steve Dunn) — Mon, 25 May 2009 12:45:00 +0000

Tree Trim is a command line tool that trims your source code tree. It removes debug files, source control bindings, and temporary files.

It’s integrated with Windows Explorer: when you right click a folder you’re given the option to clean the folder.

Massive thanks to Scott Hanselman for blogging about it and for providing some great and detailed feedback.

If you’re interested in doing your own Tree Trim plugin, there’s now a Wiki page to take you through the process. If you’d like to contribute your plugin or fix any issues, then take a look at this page.

Updated: Code Formatter Plugin for Windows Live Writer

noreply@blogger.com (Steve Dunn) — Fri, 15 May 2009 21:11:00 +0000

Version 2.0.0.2 of the Code Formatter Plugin can be downloaded here. This has a fix for when the plugin tried to load configuration from the wrong location on disk.

New tool: TreeTrim

noreply@blogger.com (Steve Dunn) — Mon, 13 Apr 2009 11:45:00 +0000

I've recently been working on a tool based on Jeff Atwoods Clean Sources Plus.

It's called TreeTrim. It's a tool that strips out debug files and folders in your source code tree and also zips and emails amongst other things.

One of the BIG requests for CleanSourcePlus (well, amongst the 5 people in the comments section of the tool's page!) is for the tool to make a working copy of your source before it deletes and zips. TreeTrim does this.

It's plug-in based, so if it doesn't do something that you want, you can write your own plug-in, plonk it in the directory, and have the tool run it alongside the other plugins.

The installer and source code is available for download at http://code.google.com/p/treetrim/

ReSharper 4.5 Beta

noreply@blogger.com (Steve Dunn) — Fri, 13 Mar 2009 21:35:00 +0000

Nice

Update to the Code Formatter Plugin

noreply@blogger.com (Steve Dunn) — Thu, 12 Mar 2009 19:44:00 +0000

Version 2.0.0.1 of the Code Formatter Plugin is now available.

New in this version:

Enhanced support for Syntax Highlighter 2x
You can now specify things such as tab size, show ruler, collapse, show toolbar, show line numbers, starting line number, and highlighting specific line numbers.
Configuration screens for the different providers

You can now add and remove languages and generally configure each provider. You can also edit the files manually – they are called SyntaxHightlighter2xConfiguration.xml and ActiProConfiguration.xml. They are located in the Plugins folder.
Preview window for Syntax Highlighter formatted code.

This was added because the Preview tab in Windows Live Writer doesn’t include the scripts and styles used in your blog engine’s templates and hence previewing Syntax Highlighted code means it looks plain. Click the Show Preview button to see this window.

Code Formatter Plugin home-page
Direct download link

IDisposable alerts

noreply@blogger.com (Steve Dunn) — Fri, 06 Mar 2009 20:10:00 +0000

Types that implement IDisposable usually do so for a reason. They probably consume resources that should be released as early as possible.

In a recent project, I came across a very neat idea. In the destructor/finalizer/finaliser of your IDisposable type, do something to alert the consumer that you’re being collected by the Garbage Collector and hence you haven’t been disposed of correctly.

But how does this type know it’s not been disposed correctly? Well, if you follow the IDisposable pattern to the letter (described in the excellent book Effective C# (Item 18), and about 3,000 places around t’internet), in your Dispose method, you’ll call GC.SupressFinalize(this); meaning the Garbage Collector won’t call your finalizer. So if you ever end up in the finalizer, the naughty user hasn’t called Dispose or hasn’t put the construction of your type in a using block.

There’s two bits to this

The constructor:

public MyResourceHungryType( )
{
  _stackTrace = new StackTrace( ) ;
}

The finalizer:

~MyResourceHungryType( )
{
  Debug.WriteLine( _stackTrace.ToString( ) ) ;
}

Then, if the finalizer is ever called, you’ll get a call stack printed up to the point where you created this type – something like:

at Namespace.MyResourceHungryType..ctor()
   at Namespace.MyType.DoSomething()
   at SomeNamespace.SomeMethod()

Handy.

New version of the Code Formatter Plugin

noreply@blogger.com (Steve Dunn) — Fri, 06 Mar 2009 07:21:00 +0000

Version 2.0 of the Code Formatter Plugin for Windows Live Writer is now available.

New in this version is the ability to use different formatting engines – in this version: ActiPro and SyntaxHighlighter 2.0

Also new is the ability to output either formatted code as text or as a bitmap.

A massive thank you to ActiPro for donating the ActiPro Syntax Editor component – the best code editor available!

If you’re reading this in an aggregator, the following code snippets may look unformatted (apart from the bitmap), but if you’re not, then it should be all nicely formatted.

Here’s some output from ActiPro as text:

public int TabWidth
{
  get
  {
      return _content.GetInt(@"TabWidth", 4);
  }
  set
  {
      _content.SetInt(@"TabWidth", value);
  }
}

Here it is again as a bitmap:

and here it is using SyntaxHighlighter 2.0

public int TabWidth
{
  get
  {
      return _content.GetInt(@"TabWidth", 4);
  }
  set
  {
      _content.SetInt(@"TabWidth", value);
  }
}

Please feel free to read more and download it.

Online mind maps in Silverlight

noreply@blogger.com (Steve Dunn) — Thu, 05 Mar 2009 07:16:00 +0000

I’m a big fan of mind maps. I use MindManager, but there’s now an online Silverlight alternative from DropMind.

It’s currently in beta, so there’s a few things that need addressing to make it as nice to use as MindManager (such as keyboard navigation). Despite this, it looks feature packed compared to other online mind mapping tools I’ve tried.

There’s also a desktop version. It has none of the above keyboard problems. It also looks and feels very similar to MindManager:

DropMind

MindManager

It’s nice to see Silverlight apps like this. I’d probably switch to it once all the glitches are resolved. MindManager’s great, but it comes with a lot of fluff I don’t need, like Office integration and RSS features.

Halt, this is StyleCop. You are in violation of SA1201!

noreply@blogger.com (Steve Dunn) — Wed, 04 Mar 2009 16:19:00 +0000

StyleCop has a ~~law~~ rule named SA1201. It says that you should put various parts of your code in the correct order. For the contents of a class this goes like:

Fields
Constructors
Finalizers (Destructors)
Delegates
Events
Enums
Interfaces
Properties
Indexers
Methods
Structs
Classes

Doing all this by hand is tedious, but as with most things, ReSharper (R#) makes it easier!

R# has a couple of features that, when combined, will mean you are fully SA1201 compliant (and, quite possibly well within the 20 seconds compliance window!) Firstly, there is a feature called Code Cleanup:

You can get R# to do various things during code clean-up. One of them is Reorder Type Members. R# does a decent job of moving stuff around by default, but it’s not perfect and doesn’t stop all warnings about SA1201. Thankfully, Reorder Type Members is configurable. The interface is straight XML in the R# Options screen. It’d be nice to have a GUI over it, but as yet (in R# 4.1 and 4.5), there isn’t one. Thankfully, you can’t bugger things up too much as the XML is validated against an XSD before it’s saved.

I was going through a legacy project recently and wanted a way to automatically reorder things, so I modified the R# XML configuration. To get your environment set-up, download the new XML configuration, go to ReSharper/Options and under languages/C# there an entry named Type Members Layout.

Deselect Use Default Patterns check-box and past in the new XML and click OK.

If you want a C# class that contains most of the things that should be reorganised, download it here. Mash it up a bit and then run StyleCop on it to ensure no SA1201 errors.

Hiding your privates from StyleCop

noreply@blogger.com (Steve Dunn) — Tue, 03 Mar 2009 11:55:00 +0000

I like StyleCop but I didn’t like the fact it produced warnings on private fields and methods. I was wrong. Not wrong in that I didn’t like warnings on privates, but wrong that I thought there was no way to tell it to stop it.

Apparently there is. Jason Allor kindly left a comment saying that it can be configured through the StyleCop settings dialog in Visual Studio.

I took a look and initially didn’t find it. I didn’t find it because I assumed there’d be different rules for public and private entities. But there’s not, you can decide at the rule type level:

It’d be nice to have separate rules for public and private. Currently, I’ve turned off all Documentation rules because I don’t like being warned that I haven’t commented private methods. However, I’d still like it to give me all the other great warnings if I do decide to comment a particular private method.

Programs that launch (or should launch) Visual Studio

noreply@blogger.com (Steve Dunn) — Tue, 03 Mar 2009 11:34:00 +0000

Programs such as FxCop provide links to source files that can be clicked and then edited in Visual Studio.

FxCop recently (probably since I went 64bit, but also possibly a side-effect of running Windows 7) started failing when clicking these links. It said:

Could not start Microsoft Visual Studio. Try specifying an alternate source code editor in Application Settings.

Maybe it just looks in \Program Files\Microsoft Visual Studio\[whatever version]. Anyway, I couldn’t see anything in the event log or any local FxCop logs, so I just changed the setting under Tools\Settings to use an explicit path to devenv.exe.

This worked, although it started a new instance of the IDE for every file. To get around that, you need to use the /Edit argument. Here’s what it looks like (click to make it bigger):

There’s other handy switches, some of which I knew about, like building a particular project/solution (to get the full list, run devenv.exe /?). It now uses an existing instance of Visual Studio if one’s present, otherwise it starts one up.

ThoughtWork’s Mingle on X64 machines

noreply@blogger.com (Steve Dunn) — Thu, 26 Feb 2009 10:20:00 +0000

By default, 32 bit applications installed on 64 bit machines are installed into the \Program Files (x86) directory.

Mingle, in particular, Ruby doesn’t like the brackets in this path, hence, when Mingle tries to start, it fails. It writes the following entries to the log file in the program’s directory:

Failed to load Rails: C:/Program Files (x86)/Mingle_2_2/app/controllers/caching/keys.rb:1: Invalid char `\257’ (‘¯’) in expression C:/Program Files (x86)/Mingle_2_2/vendor/rails/activesupport/lib/active_support/dependencies.rb:505:in `load’ C:/Program Files (x86)/Mingle_2_2/config/../vendor/rails/railties/lib/initializer.rb:475:in `load_application_initializers’ C:/Program Files (x86)/Mingle_2_2/config/../vendor/rails/railties/lib/initializer.rb:474:in `each’ C:/Program Files (x86)/Mingle_2_2/config/../vendor/rails/railties/lib/initializer.rb:474:in `load_application_initializers’ C:/Program Files (x86)/Mingle_2_2/config/../vendor/rails/railties/lib/initializer.rb:145:in `process’ C:/Program Files (x86)/Mingle_2_2/config/../vendor/rails/railties/lib/initializer.rb:93:in `run’ C:/Program Files (x86)/Mingle_2_2/config/environment.rb:116 C:/Program Files (x86)/Mingle_2_2/config/environment.rb:1

The solution: change the default installation to just \Program Files. Handy. If you want to use Mingle. On a 64 bit machine.

Problems adding an XBox 360 Media Center Extender

noreply@blogger.com (Steve Dunn) — Tue, 24 Feb 2009 21:53:00 +0000

Skip this if you’re not using a Linksys Wireless N device, Media Center, or an XBox 360!

After my umpteenth Seagate disk packed up yesterday, I’ve just reinstalled Windows 7 X64. I have spent the last couple of hours trying to get an XBox 360 connected to Windows Media Center.

Not too long ago I went through the exact same thing: Start WMC, Start the XBox, type the number on the XBox’s screen into WMC, and get nothing. The last time I did this, it was too late in the day to discover what was wrong or how to fix it – but the next day, everything worked perfectly!

This time, I went through exactly the same ritual. I looked at the Security event log and it said that :

Event 5032 – Audit Failure - Windows Firewall was unable to notify the user that it blocked an application from accepting incoming connections on the network.

After ensuring that I’d allowed Media Center Extenders through the home network (shortly followed by turning the damn firewall off altogether), I started getting (from the Media Center log under Applications and Services Logs in Event Viewer):

Event 538 - Media Center Extender Setup failed as the Extender was detected on the network but the UPnP search for the Extender failed (timed out after 20000ms).

This all seemed very familiar and nothing I was doing was making a difference. It was at this point on my last attempt that I went off to do something else. This time though, the something else’s opening hours hadn’t yet arrived, so I persevered!

In the corner of the screen (remember, this is a fresh install), was the Windows Update icon. I checked to see what it needed to update, and along with the 294 Office 2007 security patches was an update for a Marvell - Network – Wireless-N USB Network Adapter. I wondered if this had anything to do with my Linksys Wireless N USB, and it looks like it does. And after restarting, everything worked great!

The information from Windows Update showed this information:

Marvell - Network - Wireless-N USB Network Adapter

Update type: Optional

DriverUpdate: Marvell Network software update released in October, 2007

More information:
http://winqual.microsoft.com/support/?driverid=20110859

The URL wasn’t much good as it was broken. The driver information from device manager reads:

Marvell Semiconductor, Inc, version 1.00.04.03 – filename MRVW24C.sys.

This replaced the Vista drivers that I downloaded and installed from the Cisco site.

In fact, I’ve just done a search for Marvell Linksys driver, and it showed this page. This shows how to force the driver on Vista/Windows 7 if it doesn’t show up via Windows Update.

I hope some of these keywords will help others with this problem. My heart sank when I searched for the Media Center error and didn’t get 1 single hit! That shouldn’t happen any more!

Tool update: Visual Studio Orphaned Items

noreply@blogger.com (Steve Dunn) — Mon, 23 Feb 2009 11:21:00 +0000

A while back I did a small simple tool to find files on disk that were once part of a Visual Studio project but are now orphaned (removed from the project but still on disk and in your source repository). I’ve just updated it to find obsolete files from Visual Studio 2008 projects. You can download the app or the installer, or the source (or all of them!). The installer adds a right-click context menu action for .csproj files in Windows Explorer.

Available here.

StyleCop

noreply@blogger.com (Steve Dunn) — Sat, 21 Feb 2009 13:44:00 +0000

StyleCop is a tool that looks at your source code and recommends ways to improve readability and consistency. For instance, it tells you to:

Put things in a consistent order in the file – Constructors first, followed by public methods, followed by private methods etc.
Put a blank line after a closing brace. I thought this was a bit anal, but for some reason it makes code much more readable. On a related note, some people swear by having no blank lines in their source. Their reasoning: they can see more on screen without having to scroll and can see more of the method on screen at once. To me, this was like reading a book with no paragraphs. Also, If you’ve got methods that take up a whole screen, they’re probably doing too much and are too complex. I was invited to try it with the reassurance that I’d eventually see the benefit. I declined, but then realised that I had been ‘trying it’ all along - every time I read the code!
Remove unnecessary parenthesis. Reminds of a quote: “Parenthesis (however relevant) are unnecessary.”
Add XML comments to methods, properties, and events.

There’s hundreds of suggestions, mostly good, although there are some issues – here’s mine:

I generally don’t like to comment private methods, but there doesn’t seem a way to tell it to only warn me if I have public methods that are undocumented. I hope this’ll be added to the next version. I don’t like commenting private methods as, if I feel it needs a comment, then the code isn’t self describing and is either a) poorly named, or b) too complex, or c) doing too much.
StyleCop says don’t precede field names with notation. I follow the almost ubiquitous practice of preceding private fields with an underscore. For no other reason than to be able to type underscore + ctrl+space and have intellisense pop-up my private fields.

The good news is that it’s possible to turn off warnings. It’s also very well thought out in how these settings are managed: If you think a certain warning is so ridiculous you never want to see it again, you can put it in the StyleCop.Settings file and put this file at the top of your source tree. If you’ve got a project where it would make sense to turn off a warning just for that project, you can put another StyleCop.Settings file at the project level. More here.

I’m wondering if anybody would be brave enough to integrate this in their CI process! Breaking the build because there’s not a blank line under a brace seems a tad extreme!