Published 1/1/2012 by James in General | Miscellaneous

I'm James Nies, a software developer and web designer currently located in Gillette, Wyoming, USA.  Some time ago (heck, it's probably been a year or two ago) my old blog on the DotNetJunkies.com site disappeared and started redirecting to the Dr. Dobb's Journal site.  Given that I don't blog very often, at the time I let it go...  Well, I'm now getting the urge to start writing again, so I've set up this new blog.

I'll be pulling over archives of past topics to this new site and hopefully will find some new interesting things to share. 

In the meantime, welcome and enjoy!


NArrange is a stand-alone, configurable .NET code beautification tool that automatically organizes code members and elements within .NET classes. It allows developers to easily sort class contents according to their style and layout conventions. NArrange works by parsing source code files into a document object model, arranging the elements, then rewriting the arranged source code.

NArrange helps reduce the amount of time developers spend arranging members within source code files, and when used as part of check-in procedures, can also help reduce source code repository conflicts. With NArrange, developers don't need to worry about where they place a new member definition in a class; they can just type away, and run NArrange prior to compilation. After formatting, the new member will be automatically moved to the appropriate location in the source file. NArrange is not only a great time saver, but it also helps enforce coding style standards across a team when a common configuration file is used.

When projects are converted from VS 2003 to VS 2005, component classes are not automatically split out to have the new designer partial classes (e.g. MyForm.cs and MyForm.Designer.cs).

So, I thought I'd throw together a Visual Studio macro that takes care of this for me...  Note: The macro expects the code view for the class to split to be the active VS document.


The Test Container for User Control Libraries in Visual Studio 2005 is awesome!  However, I noticed that when Visual Studio 2003 class library projects are converted up to 2005, they do not automatically get this debugging functionality when they contain user controls.

After digging around in the VS program files directory I came across the Windows Control Library project template.  It can be found at Microsoft Visual Studio 8\Common7\IDE\ProjectTemplates\CSharp\Windows\1033\WindowsControlLibrary.zip.



Reflection is very useful for dynamic processing. However, if you have to repeatedly reflect on a property, say in a processing loop, you'll soon find that it can lead to performance problems. I ran into this particular problem in developing a rules engine that will be able to validate collections. I thought I would share this snippet of code, since I think it could be used in a variety of situations.

In this article I'll provide a fast, alternative solution for dynamic property access.

James Nies

.NET Ramblings and Visual Studio Adventures