/Community

It currently makes local variables which are constant camel cased too.  This is in direct violation to the All Constants Must be PascalCased rule in StyleCop. I had managed to do half the style cop rules about casing (namely making everything pascal cased where required), and was starting work on making the rest camel cased, so ran ...

This is the result of a paramter rename to CamelCase.  It incorrectly made the enums lower case too.  public static string GetMSBuildPath(     ProjectType projectType,     out string options) { string result = null; options = String.Empty; switch (projectType) {     case ...

I ran CodeIt.Right with the "Long Acronyms should be Pascal cased" rule on a large project, with several hundred replacements.  Where it worked, it did it well, and the renaming was largely successful.  However, as it went through, there were a few errors that were marked, and a few "re-run the tests" flagged ...

I can confirm CamelCase is fixed in this version.  Thanks!

If one of your rules would allow a particualr StyleCop or FXCop rule to be turned on, it would be really useful if it referred to it in the documentation, so it is a simple job to find that rule and turn it on too.

The "Method->Review visible event handlers" documentation is missing.  mk:@MSITStore:C:\Program%20Files%20(x86)\SubMain\CodeIt.Right\Help\CodeIt.Right.chm::/Html/ReviewVisibleEventHandlers.htm This program cannot display the webpage    Most likely causes:You are not connected to the Internet. The website is ...

When you fix the following rule:  Do not declare externally visible instance fieldsViolation DescriptionExternally visible type BuildLab.SharedFunctionality.Utility.ActiveDirectoryWrapper contains an instance field userData is externally visible because has public modifier. Correcting ViolationThe rule provides the following auto-correct ...

I just tried moving a nested class.  It worked fine, but all the references to the class did not get modified, and I had to do it by hand.  Is this a bug, or is it not possible.  The class was created correctly, but references such as: List<TextFileConfiguration.DevkitDetails> devkits = new ...

Hi Serge, Thanks  - I'll give it a go and get back to you.  For your reference, the build I tried was: CodeIt.Right v1.1.08262.exe Chris

I have just tried installing and running CodeIt.Right on my project.  It has found many Camel Case problems, but I cannot use the tool to auto resolve them like I want to.  If something is called LinesOfSolution, surely the rename should just make it linesOfSolution NOT linesofsolution.  I am also turing on StyleCop and FxCop ...