So... I was working with a client's application the other day and I got one of the funniest errors I have ever seen in my life.  Gotta love it!

If you ever see this error (or similar) then you really need to think about maybe refactoring a little... Anybody care to guess the complexity of this method?

Error Message:  "No overload for method MethodName takes '125' arguments."

Cyclomatic Complexity:  121 (extremely bad)
Maintenance Complexity:  13,031 (very very bad)

[Stats care of the wonderful tool:  CodeRush]

Ed B.

Just to save you a lot of time and hassle with a BizTalk installation... the computer name has to be 15 characters or less!  I guess only those of us with long names ever run into these kinds of problems :)

Ed B.

Here is a great post by Tim Rayburn on this issue. Here: http://www.timrayburn.net

It's inevitable... members of a development team are going to work really long hours.  Especially around crunch time!!!  We all know how it is!

It's both fun and frustrating to work at an organization who is growing in their software development lifecycle, process framework, and project management processes.  Almost everyone I have talked to describes places that have a less than perfect process in place for effective project management.  Even when there are policies in place, some of the times it's not even followed!

Has this ever happened to anyone?:  A resource is allocated for three different projects at a given time that have a total of nearly 90 hours of work in any given week?  And... that resource is also assigned with application management for production defects?

One of the things that makes a project run smoother is better resource allocation.  The critical path gets affected when resources are being shared between projects and application maintenance.  It's one of the "risks" that should be documented!

WARNING:  I am not a project manager.  This opinion is definitely coming from the development side of things :) I feel so bad for project managers at times.  I know that they care about just making sure that the project has a "green" light at all times and that everything will be finished on time (or early) with no defects!  I'm proud to say that I'm one of the members of the development staff that definitely strives for those same goals.

So... until later... keep being that Super Developer Resource!

Ed B.

So many people think that I work for DevExpress because of how much I rant and rave about CodeRush and Refactor Pro!

I'm telling you... CodeRush and Refactor Pro are definitely two of my most favorite tools!  But I really don't work for DevExpress... I'll blog later on both of them and some of the tools that I use from day to day that are built upon DX Core which is the foundation for both of their products and many other small tools.  If you haven't looked in DX Core (which is free) and you build or will build a Visual Studio add-in then you should definitely give it a shot.

My next plan for a coding tool that I could use from day to day is adding comments to code files in the format that I always use.  There is actually a tool that uses DX Core that does this called CR_Commenter but the bad thing:  It's only for C# code.  I thought about rewriting it for VB developers (and myself.)

Ed B.