Comments for Dan Rigby

Comment on Automatically Cancelling a Failed Build in Visual Studio by Bryan

Bryan — Fri, 27 Jan 2012 17:05:06 +0000

Nice tip, Dan.

Hard to believe that Visual Studio doesn’t have this feature on its own. Aside from the time-savings in the build this prevents an additional 20-30 errors you might get because dependent projects didn’t get the correct assembly. It fails instantly and you get only meaningful errors.

Comment on INotifyPropertyChanged, the Anders Hejlsberg Way by INotifyPropertyChanged, the Anders Hejlsberg Way | Dan Rigby | Rod's space

Wed, 18 Jan 2012 15:50:46 +0000

[...] INotifyPropertyChanged, the Anders Hejlsberg Way | Dan Rigby Like this:LikeBe the first to like this post. This entry was posted in Computers and Internet. Bookmark the permalink. ← What if You Didn’t Have to Commute? – TechTheHalls#fbid=-y_BDs1F-Uu [...]

Comment on INotifyPropertyChanged, the Anders Hejlsberg Way by INotifyPropertyChanged, the Anders Hejlsberg Way | Dan Rigby « itaysagui

Sun, 15 Jan 2012 13:17:32 +0000

[...] Dan Rigby brings in his blog a nice implementation of INotifyPropertyChanged – taken from Andres Hejlsberg: INotifyPropertyChanged, the Anders Hejlsberg Way [...]

Comment on INotifyPropertyChanged, the Anders Hejlsberg Way by INotifyPropertyChanged richtig angewendet « Der faule Programmierer

INotifyPropertyChanged richtig angewendet « Der faule Programmierer — Sun, 15 Jan 2012 09:48:27 +0000

[...] http://danrigby.com/2012/01/08/inotifypropertychanged-the-anders-hejlsberg-way/ Gefällt mir:LikeSei der Erste, dem dieser post gefällt. [...]

Comment on INotifyPropertyChanged, the Anders Hejlsberg Way by Adam Speight

Adam Speight — Sat, 14 Jan 2012 06:50:04 +0000

See my Comment about this on the Channel 9 Show post. (At making this an extension method).
http://channel9.msdn.com/Shows/This+Week+On+Channel+9/TWC9-Jan-13-2012

Comment on INotifyPropertyChanged, the Anders Hejlsberg Way by TimothyP

TimothyP — Tue, 10 Jan 2012 17:19:57 +0000

Normally I use PostSharp to define a [NotifyPropertyChanged] attribute that I can attach to the properties.
But I do like the solution you posted, one to keep in mind, thnx.

Comment on INotifyPropertyChanged, the Anders Hejlsberg Way by Dan Rigby

Dan Rigby — Tue, 10 Jan 2012 14:19:48 +0000

@SimonCropp pointed it out to me on twitter yesterday. I’ve tended to shy away from code weaving approaches because they add additional complexity to the build process (not a a lot, but it’s an extra build step). I’m also not sure what the performance characteristics are for very large projects. Case in point, my current project is 2 million+ lines of code and each build takes roughly 7 minutes presently without code analysis. Code analysis builds take 20 minutes. I’m not opposed to code weaving approaches though. I may be swayed in the future.

Comment on INotifyPropertyChanged, the Anders Hejlsberg Way by Trev

Trev — Tue, 10 Jan 2012 08:51:15 +0000

Dan, have you come across NotifyPropertyWeaver? I found it a few weeks ago http://code.google.com/p/notifypropertyweaver/

Comment on WinMerge: Not Quite Dead Yet by Eduard

Eduard — Sun, 01 Jan 2012 10:03:32 +0000

DiffMerge [1] is ok for my 3-way diff-and-merge needs, along with WinMerge for 2-way diff.

[1] http://www.sourcegear.com/diffmerge/

Comment on Automatically Cancelling a Failed Build in Visual Studio by Surge

Surge — Mon, 24 Jan 2011 19:16:41 +0000

This is a great trick, thanks for posting it. I have had this problem and waiting is not the most productive use of my time.

Comment on Making ReSharper Play Nice With StyleCop by Robbert Hock

Robbert Hock — Fri, 06 Mar 2009 09:57:43 +0000

He Dan,

Thanks for referring to me!

gr,

Robbert

Comment on FxCop 1.36 and StyleCop 4.3 by Dan Rigby

Dan Rigby — Mon, 19 Jan 2009 15:14:20 +0000

There’s a really nice post by the StyleCop authors that talks about the origins of StyleCop and why there are a lot of differences in its rules as compared to common practice and even the to the .NET framework guidelines.

It can be found here: http://blogs.msdn.com/sourceanalysis/archive/2008/05/25/a-difference-of-style.aspx

The main points are that the framework guidelines were written by people on the framework team who mostly have a c/c++ background, so the c# framework conventions tend to flow from that background. StyleCop was not written by anyone in the Visual Studio/ FxCop, or Framework teams and arose separately. As such, they when they were creating the rules, they tried to ask some basic questions about the various stylistic possibilities and would choose a “best” based on those questions and not any any stylistic predispositions inherited from previous languages.

Comment on FxCop 1.36 and StyleCop 4.3 by Scott

Scott — Mon, 19 Jan 2009 14:57:04 +0000

Good references. FxCop and StyleCop are both great tools but the things they flag as issues should be reviewed and not just taken on faith, at least for the first few times either tool is run.

Another thing to watch out for is that some of the StyleCop guidelines contradict the ones in FxCop (and likewise the Framework Design Guidelines). I’m told that they (Brad, Krzysztof, and Jason) are working through those kinds of issues but haven’t seen anything resulting from it yet.