by Serge Baranovsky

New version of CodeIt.Right is almost out. We have a beta build 1.1.08198 for you today. Please download and give it a try, let us know what works and what doesn't. This is pretty big release that includes .NET 3.5 support, Guidelines document template generation, new command line version parameters and more. Please share your feedback in the forums.

If you get an unhandled error dialog, please enter your email address so we could let you know when we resolved the issue or if we need to contact you for more details in our troubleshooting.

For the .NET 3.5 support we have made major changes to our parsing engine - please report all issues you encounter with the Beta.

Major changes in the v1.1 Beta:

Download build 1.1.08198 here - http://submain.com/download.aspx?product=codeit.right-beta 

Note: Even though 1.1.08198 is a stable Beta it's Beta nevertheless. Proceed with care.

Technorati Tags: CodeIt.Right, Coding Guidelines, Naming Conventions, Best Practices, .NET, NET

by Serge Baranovsky

This CodeIt.Right rule update includes fixes as well as 3 new security rules.

New rules:

• Do not declare read only mutable reference types (Security)
• Seal methods that satisfy private interfaces (Security)
• Secure GetObjectData overrides (Security)

These rules are included with the default profile and you will only need to follow the wizard to merge them into your custom profiles.

Fixes:

• Rule "Do not override operator equals on reference types" incorrectly triggered violation for the "Equals" method. Now this rules only reports violation for the operator "==" override.
• Fixed "If the type is a generic type, CIR adds the apostrophe-count string to the class name for the deserialization constructor"
• Fixed "If there is no explicit default parameterless constructor, adding the deserialization constructor causes errors in all derived classes that called the parameterless constructor"

As a reminder, this set of rules is distributed using the Rule AutoUpdate feature which triggers 15 minutes after you start Visual Studio. If you turned the feature off, you can manually start the update wizard from the CodeIt.Right/Help & Support/Update Rules menu.

Technorati Tags: CodeIt.Right, Coding Guidelines, Naming Conventions, Best Practices, .NET, NET

by Serge Baranovsky

Another CodeIt.Right rule update. Next stop, release of CodeIt.Right, is targeted at February 1. Yes, that's the end of this week, better hurry to take advantage of the pre-release pricing ;)

New CodeIt.Right rule posted:

• Use prefix for return type  (Naming)
• Avoid prefix for return type (Naming)
• Use prefix for derived type (Naming)
• Avoid prefix for derived type (Naming)

The four rules above will not be included into the default profile - see How to add rule to User Profile to learn how to add these into your custom profile.

This set of rules is distributed using the Rule AutoUpdate feature added into the Beta 2 of CodeIt.Right. Auto Update triggers in 15 minutes after you start Visual Studio. If you turned the feature off you can manually start the update wizard from the CodeIt.Right/Help & Support/Update Rules menu.

Technorati Tags: CodeIt.Right, Coding Guidelines, Naming Conventions, Best Practices, .NET, NET

by Serge Baranovsky

New CodeIt.Right rule posted:

• Externally visible types and members should have XML comments (General)

This rule makes sure all Public and Protected members and types have XML documentation comment.

AutoCorrect option for this rule is 'Add XML comment template' which will add

(for VB)

    ''' <summary>
    '''     
    ''' </summary>
    ''' <value>
    '''     <para>
    '''         
    '''     </para>
    ''' </value>
    ''' <remarks>
    '''     
    ''' </remarks>

(for C#)

    /// <summary>
    ///     
    /// </summary>
    /// <value>
    ///     <para>
    ///         
    ///     </para>
    /// </value>
    /// <remarks>
    ///     
    /// </remarks>

(actual content of the template will depend of the code element the XML template are being added to).

This set of rules is distributed using the Rule AutoUpdate feature added into the Beta 2 of CodeIt.Right. Auto Update triggers in 15 minutes after you start Visual Studio. If you turned the feature off you can manually start the update wizard from the CodeIt.Right/Help & Support/Update Rules menu.

Don't forget to leave your feedback in the CodeIt.Right forum http://community.submain.com/forums/4/ShowForum.aspx

(Note: if you skip the custom profile update step in the Rules Update Wizard, you still can add new rules to your custom profile(s) using the Add Rule button in the Profile Editor - you will find recent rules by sorting the date column)

Technorati Tags: CodeIt.Right, Coding Guidelines, Naming Conventions, Best Practices, .NET, NET

by Serge Baranovsky

New set of CodeIt.Right rules:

• Avoid unsealed attributes (Performance)
  
• COM visible types should be creatable (Interoperability)
  
• Pointers should not be visible (Security)
  
• Remove empty finalizers (Performance)

(All of the new rules above offer AutoCorrect options)

This set of rules is distributed using the Rule AutoUpdate feature added into the Beta 2 of CodeIt.Right. Auto Update triggers in 15 minutes after you start Visual Studio. If you turned the feature off you can manually start the update wizard from the CodeIt.Right/Help & Support/Update Rules menu.

Please leave your feedback how much you like/dislike the AutoUpdate feature, your suggestions - in the CodeIt.Right forum http://community.submain.com/forums/4/ShowForum.aspx

(Note: if you skip the custom profile update step in the Rules Update Wizard, you still can add new rules to your custom profile(s) using the Add Rule button in the Profile Editor - you will find recent rules by sorting the date column)

For more information on CodeIt.Right, getting started presentation, support and feedback see Beta 1 announce post.

Technorati Tags: CodeIt.Right, Coding Guidelines, Naming Conventions, Best Practices, .NET, NET

by Serge Baranovsky

We published new CodeIt.Right rules:

• Mark assemblies with assembly version (Design)
• Mark assemblies with CLSCompliant (Design)
• Mark assemblies with ComVisible (Design)
• Remove unused locals (Performance)

(All of the new rules above offer AutoCorrect options)

This is the first set of rules that we distribute using the Rule AutoUpdate feature recently added into the Beta 2 of CodeIt.Right. Auto Update triggers in 15 minutes after you start Visual Studio. If you turned the feature off you can manually start the update wizard from the CodeIt.Right/Help & Support/Update Rules menu.

The AutoUpdate feature is brand new - please leave your feedback how much you like/dislike it, what steps are not intuitive, what would you improve - in the CodeIt.Right forum http://community.submain.com/forums/4/ShowForum.aspx

(Note: if you skip the custom profile update step in the Rules Update Wizard, you still can add new rules to your custom profile(s) using the Add Rule button in the Profile Editor - you will find recent rules by sorting the date column)

For more information on CodeIt.Right, getting started presentation, support and feedback see Beta 1 announce post.

Technorati Tags: CodeIt.Right, Coding Guidelines, Naming Conventions, Best Practices, .NET, NET