/Community

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 these 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.

Read more here - http://submain.com/blog/CodeItRightBeta2IsOutBuild1007268.aspx 

---

Thank you,
Serge Baranovsky
http://submain.com - .NET Developer Tools  |  Microsoft VB MVP  |  http://vbcity.com - VB Developer Community
» » (Static Code Analysis + Automatic Refactoring) / Painless Coding Guidelines = CodeIt.Right - http://submain.com/codeit.right
» » C#/VB .NET Coding Guidelines - FREE 100+ page ebook (PDF) http://submain.com/guidelines

When it try to update the rule, the error has occurred. Below is the screen shot.

 

This is great feature, but I think the problem is on the dll extension of the rule. This extension may not pass some of firewall. I think that you should put it in an zip or cab file, then download all, extract at client user then run update. 

Thank you for reporting the issue. Would you please send us LOG file at support@submain.com. You can find the log file in "<My Documents>\SubMain\CodeIt.Right for VS2005\CodeIt.Right.log".

---

Thank you,
Misha Zhutov
http://submain.com - .NET Developer Tools

Sent it.

 Misha, I would like to know there is any way that I can check the source code region (#region....#endregion)

Eg, Each source file must have the predefined header such as Copyright information, in class must have specified region, and Private field must be in the specified region...?
 

Thank you for sending the log file. We will use to troubleshoot the issue.

In the current version our parser ignores #region keywords but we have it on our to-do list.

Once we have that done, it will be possible to write the rules you mention above.

---

Thank you,
Serge Baranovsky
http://submain.com - .NET Developer Tools  |  Microsoft VB MVP  |  http://vbcity.com - VB Developer Community
» » (Static Code Analysis + Automatic Refactoring) / Painless Coding Guidelines = CodeIt.Right - http://submain.com/codeit.right
» » C#/VB .NET Coding Guidelines - FREE 100+ page ebook (PDF) http://submain.com/guidelines

Do you by any chance have Norton or McAfee installed? We suspect this is the problem we will need to work around.

---

Thank you,
Serge Baranovsky
http://submain.com - .NET Developer Tools  |  Microsoft VB MVP  |  http://vbcity.com - VB Developer Community
» » (Static Code Analysis + Automatic Refactoring) / Painless Coding Guidelines = CodeIt.Right - http://submain.com/codeit.right
» » C#/VB .NET Coding Guidelines - FREE 100+ page ebook (PDF) http://submain.com/guidelines

Yeah, I'm on company with Firewall and Sophos antivirus.

Because CodeIt.Right scan the source code also, so I think that we should have some more features

- Allow checking public method XML Comment existing or not, that's so great because it will prevent the developer coding without document.

- It should also scan the header of source file (most of the source code has this as comment, except the source code file of dummy developer)

- This feature I think it's not easy, it should ignore the Visual Auto generate code. for example, when I create a text box on a Form with Text value = "Text box 1", then VSS will automatically create the textbox object and have the statement: TextBox1.Text = "Text box 1"; this should be ignore the Rule related to globalization (just example) Or the programmer should list some files that it will ignore when analyze code, this list must be save for other analysis.

These are the cool feature that  another tools does not support. Because, most of the main feature of CodeIt.Right, FxCop also have, except the correct... Because FxCop analyze on assembly, and CodeIt.Right works on source code, so, I think you should use this advantage to do which assembly analysis tool (like FxCop) can not.

Thanks and look forward to testing the next beta release.
 

 

Thank you, Hoang Minh. 

hoangminh:

- Allow checking public method XML Comment existing or not, that's so great because it will prevent the developer coding without document.

This is good suggestion for a rule - we will add it on the list. 

hoangminh:

- It should also scan the header of source file (most of the source code has this as comment, except the source code file of dummy developer)

This one is a little tricky - headers are all different depending on an organization standards and checking just for presence of (any) header is arguably useful. What do you think? 

hoangminh:

- This feature I think it's not easy, it should ignore the Visual Auto generate code. for example, when I create a text box on a Form with Text value = "Text box 1", then VSS will automatically create the textbox object and have the statement: TextBox1.Text = "Text box 1"; this should be ignore the Rule related to globalization (just example) Or the programmer should list some files that it will ignore when analyze code, this list must be save for other analysis.

I'm not sure I got this - could you please elaborate? 

hoangminh:

These are the cool feature that  another tools does not support. Because, most of the main feature of CodeIt.Right, FxCop also have, except the correct... Because FxCop analyze on assembly, and CodeIt.Right works on source code, so, I think you should use this advantage to do which assembly analysis tool (like FxCop) can not.

This is exactly the direction we are heading to [;-)]

---

Thank you,
Serge Baranovsky
http://submain.com - .NET Developer Tools  |  Microsoft VB MVP  |  http://vbcity.com - VB Developer Community
» » (Static Code Analysis + Automatic Refactoring) / Painless Coding Guidelines = CodeIt.Right - http://submain.com/codeit.right
» » C#/VB .NET Coding Guidelines - FREE 100+ page ebook (PDF) http://submain.com/guidelines

About the source header files, to make it easily configure, I think that RegEx is the best solution. You can provide the developer to configure the source header for CodeIt.Right.

For example: the below is a small header text on CSharp file using Regular expression:

  Another Suggestion:

- You should add the Rule: use Using statement when use IDisposal type (like SqlConnection...) (ReSharper has this feature)

- In the Cach block, if there is the throw statement only and some declaration, such like
catch(Exception ex){ throw;}, this should be warned because it does no thing here.

- Check for the potential exception such as when detection there is statement like: objectInstance.Name without checking objectInstance == null first (ReSharper also has this feature).

- Check that in a source file, there is at most 1 class type

- Check that the source file has organized to correct folder.
For example, the source file name as: NamingRule.cs and it is the source of class: SubMain.CodeItRight.Components.Rule.Naming, then it should be organized in the folder /Rule/Naming of project (assume that SubMain.CodeItRight.Components is the Root namespace of project)