Sevket Seyalioglu

Dear developers,

Please do something good for yourselves and me & learn workflows which will make life so great for all of us.
Go through the learning videos from here: http://msdn.microsoft.com/en-us/VS2010TrainingCourse_IntroToWF

Your humble AVP of Technology

ILSpy seems to be a very good alternative to old .NET Reflector which is not free anymore.

You can find more details @ http://wiki.sharpdevelop.net/ilspy.ashx

I can’t believe that Microsoft’s static code analysis throws error or warning to “CA1062: Validate arguments of public methods” when using code contracts which is nicely described @ http://msdn.microsoft.com/en-us/magazine/ee236408.aspx  and http://msdn.microsoft.com/en-us/devlabs/dd491992 or even better described here

They presented this MSDN magazine and haven’t they tested this before making it that public.
I don’t want to give up my rule but what is my choice? Supress

Here are the links to this issue in the community

http://geekswithblogs.net/terje/archive/2010/10/14/making-static-code-analysis-and-code-contracts-work-together-or.aspx
http://connect.microsoft.com/VisualStudio/feedback/details/488341/code-contracts-dont-affect-ca1062-validate-parameter-before-usage

Here we go,

After so much name discussion, finally project name is clear.

1. It needs to be on the cloud (Azure)
2. It needs to be clean (Green)
3. It needs to be unique

There are few very strong QA Automation frameworks available which are watir, watin and selenium so far  that I’ve seen quite promising.
All of those have one thing in common. They are all free unlike extremely expensive IBM Rational or HP QTP.

What makes the selection is some factors but most of all, experience of the users with them.
I consider the following to be some killer decisions.

1. Ability to have different execution plans based on different scenarios
1. Ability to have X many scripts
2. Based on scenario execute Y many of them (Y < X) automatically. Such as after every nightly build.
2. Proper reporting
3. Speed
1. By nature of the framework to be able to run fast
2. To be able to execute X many scripts simultaneously
3. To be able to execute same script in Y many browsers simultaneously
4. Support for web browsers (as many as possible)

Looking forward for your inputs

This is really interesting for unit testing. A new approach called approval testing. Well not too interesting but nicely done approach.

Requires some thinking over this.
And wondering really how this will work with TFS automated builds (unit testing integrated mode)

Plus there is more in ASP.NET unit testing or we shall more say results testing.
I am posting this because it is interesting concept. I don’t really approve changing the base code to do testing.

Ohh yes, check this framework for more details here: http://approvaltests.sourceforge.net/

I think it is time to test developers if they are up to date with proper design patterns.

And a question to all;

Do developers need to know design patterns or architects & leads would be enough to know?
(Here I am presenting this question to companies who has large number of teams, not for companies with less than 15 developers)

Well,

I am sure, many of you had frustrating experience from time to time.
How bad it is to be in situation where a developer causes the whole release to be delayed unnecessarily!
Or one mistake by a developer causes all developers/development teams to suffer?
Or even worse, how a developer cause a huge live bug!

None of those are fun to have and indeed very much frustrating.

What shall we do?
Someone shall take the responsibility because I hate to hear sorry after sorry!

We shall penalize the developer also?
Even better, the TEAM that developer belongs to be penalized so they will be more careful next time!

But what is the solution? How do we penalize a tech team?

Of course not with money!
And firing is also not a problem.
– LOL
I have a solution which works perfectly!

I simply force the whole team to do one of the following in order for them to be allowed to be checking in.

• Fix some code analysis rules (I change the warnings to “errors”). Build fails if we have erroneous rule failures (VS 2010 code analysis or fxcop 10.0)
• Enforce to write more unit tests to increase code coverage rate.

Thanks to TFS 2010 Gated Check-ins.

• Each check in is controlled by gated check-ins
• Check-in fails if
• Solution does not build
• There are errors in code analysis rules
• A Unit Test Fails
• Code coverage rate is below last coverage value (we’ve customized build template in order to achieve this)
• If they need to be penalized I enforce them to cover 1% more code with unit tests
• Here is an example result:
  

That is our solution and results are improved code quality.
I thank Microsoft for TFS 2010 and automated builds.
And thanks to Serdar for implementing  build template modification.
It will be a bit odd but I thank myself for the innovation here and getting deep into the capabilities which can be controlled.

It has been some time since I’ve posted regarding my CMS work.
It is going well and here are the achievements so far..

I am moving the contents to the defined template zones with admin preview options.

The challenge:  Properly placing contents at where we really want them to be and saving this setting per each page.

I’ve been interviewing several candidates throughout the week and here is the frustrating observation.

Many candidates

1. Don’t know unit testing
2. The ones who know don’t know code coverage
1. Many hear the phrase from me only
3. Some use it for site monitoring rather than code health check
4. The architect level experienced ones can’t do simple web project
1. Not asking too much, just have form, validate data, save into database and show on another page (list of data from database)