SubMain Community

How to submit CodeIt.Right Log file to SubMain support

Serge B. — Sun, 22 Jun 2008 05:43:00 GMT

CodeIt.Right Log file contains detailed debug information that allows us to troubleshoot most every issue on you experience with the product.

These are the steps to email the log file to us:

Open Visual Studio
In the menu bar, click CodeIt.Right, then click Help & Support, and then click Email Log File
Attach file from the location in the email body - in the screenshot above is "C:\Users\sergeb\Documents\SubMain\CodeIt.Right for VS2008\CodeIt.Right.log"
Click Send to email the attached file to us.

PADNUG CodeIt.Right Presentation Slides

SubMain.Blog() — Tue, 13 May 2008 01:13:19 GMT

by Serge Baranovsky As I mentioned earlier I presented CodeIt.Right in Portland at PADNUG last week. I had great time, thank you all guys and girls - you are wonderful and very friendly audience! I'm glad I got to know better some of you during the "informal" meeting at Gustav's after the presentation. Few of you asked if the slides will be available, so I'm published PDF version of the slides on our community page - PADNUG CodeIt.Right Presentation Slides . If you need the PPT version - just drop...(read more)

Upcoming updates, tutorials and PADNUG presentation

SubMain.Blog() — Sat, 03 May 2008 00:16:56 GMT

by Serge Baranovsky v1.1 progress & Enterprise Edition The v1.1 release that includes .NET 3.5 syntax has been slightly delayed. There are two reasons for that - we had too much fun at the MVP Summit mid-April and we made few significant changes to the parsing and refactoring engines to support the 3.5 syntax. The coding part is done, we cover all of the .NET 3.5 now. And we are going through a major testing phase as the base application layer responsible for all .NET versions was affected. We...(read more)

CodeIt.Right Rule Update 20080412

SubMain.Blog() — Sat, 12 Apr 2008 19:59:05 GMT

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...(read more)

CodeItRight.Cmd.exe Command Line Options

Serge B. — Mon, 24 Mar 2008 05:11:00 GMT

CodeItRight.Cmd is the command-line companion to the CodeIt.Right application. Like CodeIt.Right, CodeItRight.Cmd analyzes source code and reports violations, such as possible design, performance, and security issues. CodeItRight.Cmd can be used as a stand-alone tool or added to automated build processes.

The following are the command line parameters that are supported by SubMain.CodeItRight.Cmd.exe ; Parameter values are not case sensitive.

/Solution - (Required*) - full file name of the solution to load (*.sln file) (*) This parameter is not required if /Project parameter specified.

/Project - (Required*) - full file name of the project to load (*.csproj or *.vbproj file) (*) This parameter is not required if /Solution parameter specified.
/Out - (Required) - full name of the xml report output file.
/OutXSL - (Optional) - full name of the xsl file to override the default xsl.
/CRData - (Optional) - full name of the CodeIt.Right .crdata file. When specified, CodeItRight.Cmd will use the exclusion list (violations, rules and files) saved using the Visual Studio version of CodeIt.Right.
/Profile - (Optional) - name of the User Profile that defines active rule set for the analysis. When omitted, the buil-in profile is used.
/Quiet - (Optional) - disables console output.

/Help - display list of command line parameters.

Example:

SubMain.CodeItRight.Cmd.exe /Solution:"C:\MyProjects\MyProject\MyProject.sln"
/Out:"C:\MyProjects\MyProject\MyProject.CIR.Output.xml"
/CRData:"C:\MyProjects\MyProject\MyProject.crdata" /Profile:"My Profile"

CodeItRight.Cmd Error Codes

0x0 No errors
0x1 Command Line Switch Error
0x2 Command Line Argument Error
0x4 Initialization Error
0x8 Analysis Error
0x10 Output Error
0x20 Unknown Error

CodeIt.Right v1.0.08035 CodeItRight.Cmd.exe Refresh

SubMain.Blog() — Sun, 23 Mar 2008 09:00:44 GMT

by Serge Baranovsky Since the v1.0 release a number of improvements were requested for use CodeIt.Right in an automated build process and we are making a refresh for CodeItRight.Cmd.exe available today. This version of CodeItRight.Cmd will be included as part of the v1.1 release which additionally will ship with ready to use tasks for MSBuild and NAnt. See CodeItRight.Cmd.exe Command Line Options for complete list of the console version command line switches and error codes. Important: This copy...(read more)

Tutorial: Creating Custom Rules

Serge B. — Sun, 16 Mar 2008 23:17:00 GMT

The best part about CodeIt.Right is that you are not limited to just the rule libraries included into the box. You can easily define your own (custom) rules. What makes this possible is the "CodeIt.Right SDK". The SDK documentation is available online at http://submain.com/codeit.right/sdk/ as well as locally as part of your CodeIt.Right help file.

In this tutorial we will create "Use Certain Suffixes For Derived Types" rule. We will

Create Custom Rule Template using Wizard that CodeIt.Right adds to Visual Studio
Implement set of methods and properties that will find and correct violations of the rule
Define Configurable Properties for the rule, so the users will be able to create instances of the rule and tweak it to their needs
Deploy the new rule

Create Custom Rule Template Using Wizard

Open Visual Studio
In the menu bar, click File, and then click New Project
In the New Project dialog box, in the Project Types pane, select CodeIt.Right Projects if that option is not already selected.
In the Templates pane, select the template for the appropriate programming language (Visual Basic or Visual C#). The custom rule in the examples uses Visual Basic.
Complete the Name, Location, and Solution fields for the custom rule.
Click OK. The New Rule Wizard dialog box appears.
In the New Rule Wizard dialog box, complete as many of the fields as possible. Fields that have a red asterisk to the right are required. Click Next.
Select the options to determine the scope for the custom rule. To select or deselect all the options, select All. Click Next.
Select the targets for the custom rule. When done, click Finish.

The status bar at the bottom of the Visual Studio window displays the progress of the creation of the custom rule.

Edit the Generated Template

After a custom rule template is created, you can edit it in the Solution Explorer. You can edit template information, the content generated by the New Rule Wizard, and implement code of the Check and Correct methods.

Double-click the rule in Soultion Explorer to edit it. The generated regions of the rule are collapsed by default.

Expand the Wizard Generated Code region to review the code generated based on options selected in the New Rule Wizard. You can edit the options if necessary. Note that the rule's ID is automatically generated GUID - you can edit it as well but make sure your ID is not equal to any of the built-in CodeIt.Right rules or even better your rule ID doesn't follow CodeIt.Right internal ID schema.

#Region "Wizard Generated Code"

#Region "Data Entered On Wizard form"

    Private Const InputID As String = "0500daf7-f2a0-4549-b90e-bd8f6d515bb5"
    Private Const InputName As String = "UseCertainSuffixesForDerivedTypes"
    Private Const InputTitle As String = "Use Certain Suffixes For Derived Types"
    Private Const InputSeverity As SeverityLevel = SeverityLevel.Warning
    Private Const InputScopes As RuleScopes = _
      RuleScopes.Public or RuleScopes.ProtectedInternal or RuleScopes.Private or RuleScopes.Abstract or RuleScopes.Sealed _
      or RuleScopes.Readonly or RuleScopes.Virtual or RuleScopes.Override or RuleScopes.Extern or RuleScopes.Unsafe _
      or RuleScopes.SpecialName or RuleScopes.Const or RuleScopes.Volatile or RuleScopes.WriteOnly _
      or RuleScopes.WithEvents or RuleScopes.Default
    Private Const InputAuthor As String = "SubMain Team"
    Private Const InputEmail As String = "support@submain.com"
    Private Const InputUrl As String = ""
    Private Const InputAvailableTargets As RuleTargets = RuleTargets.Class
    Private Const InputViolationDescription As String = ""

#End Region

#Region "Constructor"

    Public Sub New()
        Me.Name = InputName
        Me.Title = InputTitle
        Me.Severity = InputSeverity
        Me.Targets = Me.AvailableTargets
        Me.Scopes = InputScopes
    End Sub

#End Region

    Public Overrides ReadOnly Property ID As String
        Get
            Return InputID
        End Get
    End Property

    Public Overrides ReadOnly Property AvailableTargets As RuleTargets
        Get
            Return InputAvailableTargets
        End Get
    End Property

    Public Overrides ReadOnly Property Author As String
        Get
            Return InputAuthor
        End Get
    End Property

    Public Overrides ReadOnly Property Email As String
        Get
            Return InputEmail
        End Get
    End Property

    Public Overrides ReadOnly Property Url As String
        Get
            Return InputUrl
        End Get
    End Property

    Public Overrides ReadOnly Property ViolationDescription As String
        Get
            Return InputViolationDescription
        End Get
    End Property

    Public Overloads Function Correct(ByVal correctionOptionIndex as Integer) As Boolean
        MyBase.Correct(correctionOptionIndex)

        Select Case correctionOptionIndex

            Case Else
        End Select

        Return False
    End Function

#End Region

In the Template to be populated by rule author region, edit the AutoCorrectionOptions property to establish all the options for automatic correction of violations to the rule. Each option is added to the drop-down list in the Action column when code is analyzed. The GetCorrect0Name will be implemented in the next bullet.

Public Overrides ReadOnly Property AutoCorrectionOptions As String()

    Get

        If (MyBase._userCorrectOptions.Count = 0) Then

            ' Get title of the correction option
            Dim text As String = Me.GetCorrect0Name

            If ([text].Length > 0) Then

                ' Add to the list of available options
                MyBase._userCorrectOptions.Add([text])

            End If

        End If

        Return MyBase.AutoCorrectionOptions

    End Get

End Property

In the Template to be populated by rule author region, edit the Correction method to establish how violations to the rule are corrected. In the example below, the correct suffix is added to the code element. The new name is then checked using helper function NamingRuleUtilities.FixForUniqueName to make sure it is unique in the solution. If not, the name is further modified so that it is unique. SuffixToCheck is a configurable property that we will define later in this tutorial.

Private Function GetCorrect0Name() As String

    Dim baseName As String = String.Empty

    If (Not MyBase.Element Is Nothing) Then

        Dim info As ICodeElementInfo = MyBase.Element.ToCodeElementInfo

        If (Not info Is Nothing) Then

            ' Get the code element name
            Dim displayName As String = info.DisplayName

            ' Add the correct suffix
            If ((Not Me.SuffixToCheck Is Nothing) AndAlso (Me.SuffixToCheck.Length > 0)) Then
                baseName = (displayName & Me.SuffixToCheck)
            End If

        End If
    End If

    ' Make sure the new name is unique
    Return NamingRuleUtilities.FixForUniqueName(baseName, MyBase.Element)

End Function

In the Template to be populated by rule author region, edit the Check method to establish violations to the rule are found. In the example below, each appropriate code element is checked for the correct suffix. If the element does not include the correct suffix, it is flagged as a violation. MustImplement is another configurable property defined later in the tutorial. Method ITypeInfo.IsAssignableFrom returns True if the code element derived from the type stored in MustImplement. Helper function NamingRuleUtilities.HasSuffix returns True is code element has the suffix, False otherwise.

Public Overrides Function Check(ByVal element As IElementInfo) As Boolean

    If (Not element Is Nothing) Then

        Dim info As ICodeElementInfo = element.ToCodeElementInfo

        If (Not info Is Nothing) Then

            ' Get the code element name
            Dim displayName As String = info.DisplayName

            ' If configurable properties SuffixToCheck and MustImplement have values
            If (((Not Me.SuffixToCheck Is Nothing) AndAlso (Me.SuffixToCheck.Length > 0)) _
               AndAlso ((Not Me.MustImplement Is Nothing) AndAlso (Me.MustImplement.Length > 0))) Then

                Dim info2 As ITypeInfo = TryCast(info, ITypeInfo)

                ' If element derives from the type (MustImplement) and doesn't have correct suffix (SuffixToCheck)
                If (((Not info2 Is Nothing) AndAlso info2.IsAssignableFrom(Me.MustImplement)) _
                   AndAlso Not NamingRuleUtilities.HasSuffix(displayName, Me.SuffixToCheck)) Then

                    ' Flag the violation
                    Return True

                End If

            End If

        End If

    End If

    Return False

End Function

Configurable Properties

Configurable Properties are flexible mechanism that allows to develop rules that can be customized in user profiles (rule instances). They must be marked with attribute <ConfigurableProperty>.

For our rule we need two configurable properties -

MustImplement - will filter and only run the rest of the rule against code elements that derive from the type assigned in this property
SuffixToCheck - will allow to define for each rule instance suffix to be that the code element derived from MustImplement should have

<ConfigurableProperty, Description("Type should implement the specified type or interface")> _
    Public Property MustImplement As String

        Get
            Return Me._mustImplement
        End Get

        Set(ByVal value As String)
            Me._mustImplement = value
        End Set

    End Property

<ConfigurableProperty, Description("Certain Suffix to be checked")> _
    Public Property SuffixToCheck As String

        Get
            Return Me._suffixToCheck
        End Get

        Set(ByVal value As String)
            Me._suffixToCheck = value
        End Set

    End Property

Here is how properties are configured for a specific instance of the rule we developed in this tutorial - "Exception class name must have 'Exception' suffix" (click the image for full size):

Adding another rule to the same project

At this point of the tutorial we have one custom rule implemented in the project (library). If you want to add another rule or more to the library, you need to right-click project in the Solution Explorer, select Add New Item and pick Custom Rule Class under CodeIt.Right Items - this will start New Rule Wizard.

Build and Deploy new rule

Our rule is now ready to be deployed.

Build your custom rule project
Copy the resulting .dll assembly into the <CodeIt.Right installation>\Rules directory (typically Program Files\SubMain\CodeIt.Right\Rules)
Add a new instance of the new rule to your user profile. See How to add rule to User Profile.

Note: You don't need to close Visual Studio when you deploy new or updated rule library. CodeIt.Right picks up the rule library changes every time you analyze code or open Profile Editor.

Where do I find samples?

Your best source for rule examples is CodeIt.Right's own rule library (see the <CodeIt.Right installation>\Rules directory). As of this post we have implemented 75+ rule classes with 100+ rule instances in the detault profile. Feel free to explore what we've got using Lutz Roeder's wonderful Reflector and learn what's inside of each rule.

Keep an eye on is our community Custom Rule Repository - it will grow as users develop and share their rules. This is also the place where we post our complete sample rule projects.

Join us at the Party With Palermo MVP Summit 2008

SubMain.Blog() — Wed, 12 Mar 2008 08:34:19 GMT

by Serge Baranovsky Besides hosting traditional now vbCity and VB-INSIDERS get-together around MVP Summit this year we are also sponsoring the " Party With Palermo " on Sunday, April 13, 2008 @ 7:00PM - 10:00PM - more details at http://www.partywithpalermo.com/ If you are in Seattle area that weekend, come join in - it'll be fun. There will be plenty great people to meet, free swag, free drinks and food. Find me - you will get free software too (did I just say CodeIt.Right out loud? :)...(read more)

CodeIt.Right reviewed by Mike McIntyre

SubMain.Blog() — Mon, 10 Mar 2008 07:53:50 GMT

by Serge Baranovsky Mike McIntyre posted great review of CodeIt.Right on DevCity.NET - http://www.devcity.net/Articles/348/CodeIt.Right.Review.aspx - Mike has put CodeIt.Right through a test using 10 of his projects. Mike summarizes: I feel CodeIt.Right's features for configurable static code analysis and its ability to automatically correct my code make it well worth the purchase price. It has become and indispensable addition to my developer toolkit. I highly recommend you give it a try. Thank...(read more)

CodeIt.Right Pricing and Limited Time Offer

SubMain.Blog() — Thu, 21 Feb 2008 10:20:12 GMT

by Serge Baranovsky CodeIt.Right is back to regular price of $250/user and we also introduced volume license discounts. For limited time when you purchase CodeIt.Right license we include complementary 1 year of Software Assurance & Gold Support Subscription - more information about the subscription - (regular - only 3 months of Software Assurance only included with additional $100 per year subscription). And, as always, you are covered by our 60-day money-back guarantee. » Buy CodeIt.Right Now...(read more)

CodeIt.Right Introductory Price

SubMain.Blog() — Wed, 06 Feb 2008 07:51:21 GMT

by Serge Baranovsky CodeIt.Right will be available at the introductory price of $180 through February 20th, 2008 (regular price $250/user after Feb 20th). To make it even better the introductory price also includes complementary 1 year of Software Assurance & Gold Support Subscription - more info about the subscription - (regular - only 3 months included with additional $100 per year). And, as always, you are covered by our 60-day money-back guarantee. > February 20th is only two weeks away,...(read more)

CodeIt.Right v1.0 Released!

SubMain.Blog() — Wed, 06 Feb 2008 03:50:33 GMT

by Serge Baranovsky CodeIt.Right is finally finished after about 3 years in the making. That's right, CodeIt.Right is Released ! It is out in its all new shiny package :) I would like to make a pause here and extend my deepest gratitude towards everyone who helped make this release possible. From the SubMain development team, the advisory board members, to everyone who participated in the community and contributed feedback over the year since we released the first public beta. CodeIt.Right, my 7...(read more)

New CodeIt.Right Rules - Update 20080128

SubMain.Blog() — Mon, 28 Jan 2008 22:57:15 GMT

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...(read more)

How to add rule to User Profile

Serge B. — Thu, 24 Jan 2008 10:15:00 GMT

Some of the rules included with CodeIt.Right are not part of the built-in profile as are not part of the Microsoft Guidelines and yet they often come very handy especially when you choose to use a standard other than recommended by Microsoft.

This post covers step-by-step how to add a rule to custom user profile. In this walk-through we will add rule "Replace identifier prefix" (ReplaceIdentifierPrefix) [Naming] and configure it to replace the old style "m_" variable prefix with the new .NET style "_" (underscore). This is very convenient when move existing old style project to the .NET naming conventions.

Open Profile Editor
Make sure you are not using built-in profile -> see How to create own Profile
Click the Add Rule toolbar button
Find and select the "Replace identifier prefix" in the list and click OK
Enter name for the new rule (we will use "Replace "m_" with "_" is"), set PrefixToCheck parameter to "m_" and PrefixToReplace to "_", choose Targets (using only the targets that are applicable to the rule allows for better analysis performance) and click Save
New rule "Replace "m_" with "_" is" is part of your profile now.

How to create own Profile

Serge B. — Thu, 24 Jan 2008 08:45:00 GMT

When you try to edit the built-in Microsoft Guidelines profile in CodeIt.Right you will get a message saying that profile is not modifiable. If you want to customize CodeIt.Right profile, you need to create your own profile first. This can be done by cloning existing profile or creating your own from scratch.

Cloning existing profile

To clone existing profile you need

Open Profile Editor
Click the Save As toolbar button
Enter name and (optional) description for your profile
Newly created profile is opened in Profile Editor

Creating new profile

To create new profile from scratch you need

Open Profile Editor
Click the New toolbar button
Enter name, (optional) description for your profile. Then choose Base Profile to copy rules from (select Blank if you want to start your profile from scratch)
Newly created profile is opened in Profile Editor

CodeIt.Right Release Candidate build 1.0.08005

SubMain.Blog() — Wed, 16 Jan 2008 10:11:49 GMT

by Serge Baranovsky Here we have another smallish update for CodeIt.Right - build 1.0.08005. Early next week we publish another couple of new really cool rules. We will use rule Auto-Update to push them to you. You can see the product is getting very stable now and we only do minor modifications. Which means, guess what? That we are releasing soon :) So, make sure you take advantage of our pre-release CodeIt.Right license pricing while it's not too late ;) Changes since the last build Enabled the...(read more)

CodeIt.Right Pre-release price

SubMain.Blog() — Tue, 25 Dec 2007 10:02:44 GMT

by Serge Baranovsky As the RC is available we are releasing CodeIt.Right in the next 3 weeks. We decided to offer the product for purchase at a pre-release price with an extra bonus. Buy CodeIt.Right here . This is the full license we just give you an opportunity to get it at a lower price. Pre-release price Pre-release price $250 $150 (includes complementary 1 year of Software Assurance & Gold Support subscription ) Buy CodeIt.Right today and save! Post-release price User license - $250 (includes...(read more)

CodeIt.Right Release Candidate build 1.0.07355

SubMain.Blog() — Fri, 21 Dec 2007 12:28:36 GMT

by Serge Baranovsky Release is just around the corner - CodeIt.Right Release Candidate build 1.0.07355 is available now. This build also includes CodeIt.Right SDK help file. Please download the Release Candidate and share your feedback in the forums . Major changes overview since the last Beta build Added support for VS2008 - currently only supports .NET 2.0 solutions in the VS2008 IDE Included CodeIt.Right SDK help file - installs into the SubMain/CodeIt.Right/Help directory. Also available separately...(read more)

New CodeIt.Right Rules - Update 20071203

SubMain.Blog() — Mon, 03 Dec 2007 10:26:36 GMT

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> ///...(read more)

CodeIt.Right Beta build 1.0.07322

SubMain.Blog() — Mon, 19 Nov 2007 10:20:33 GMT

by Serge Baranovsky Another refresh for CodeIt.Right Beta build 1.0.07322. Please download the latest build and to let us know what you think on the forums . Major changes overview since the last build Changed setup directory for VS2005 version to "CodeIt.Right" - used to be "CideIt.Right for VS2005" Toolbar and most of the menu is now enabled even when you don't have any solution/projects open Changed file format of Rule Update engine to .ZIP (from .DLL) to avoid firewall issues. Added new rules...(read more)

CodeIt.Right Tutorials Updated

SubMain.Blog() — Fri, 02 Nov 2007 18:32:47 GMT

by Serge Baranovsky We have updated CodeIt.Right Flash presentations based on the Beta 2 layout - they are covering new features as well - http://submain.com/tutorials Quick Start - Quick 1 minute CodeIt.Right walk through Introduction to CodeIt.Right Features - Here is where we show main CodeIt.Right functions and options ISerializable Pattern example - One of many scenarios when CodeIt.Right helps to diagnose issues early and implement coding patterns correctly. Please let us know in the CodeIt.Right...(read more)

CodeIt.Once build 1.2.07303

SubMain.Blog() — Wed, 31 Oct 2007 20:42:22 GMT

by Serge Baranovsky Another update for CodeIt.Once - build 1.2.07303 - resolved issues with solution folders, generics, improved quality of the Rename, Extract Interface and Encapsulate Field commands. Download link - http://submain.com/download Technorati Tags: CodeIt.Once , Refactoring , Visual Studio , .NET , NET...(read more)

New CodeIt.Right Rules published - Update 20071017

SubMain.Blog() — Wed, 17 Oct 2007 08:59:59 GMT

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...(read more)

New CodeIt.Right Rules published - Update 20071008

SubMain.Blog() — Tue, 09 Oct 2007 00:17:36 GMT

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...(read more)

CodeIt.Right Beta 2 released - build 1.0.07268 - Share feedback and win $100 Amazon gift certificate

Serge B. — Thu, 27 Sep 2007 08:06:00 GMT

CodeIt.Right Beta 2 is out now - this is a major update since the Beta 1.

Our team is eager to hear your feedback on the Beta 2 version, as you can really influence the next stage of development. Be sure download the Beta 2 and to let us know what you think on the forums, and have your chance to win 1 of 3 $100 Amazon gift certificates to be awarded to the top three posts by October 31st.

0x0	No errors
0x1	Command Line Switch Error
0x2	Command Line Argument Error
0x4	Initialization Error
0x8	Analysis Error
0x10	Output Error
0x20	Unknown Error