@giggio I made many commits to fix your observations. When everything is aproved I will squash them all.
Which DiagnosticSeverity should I set?

@giggio How did you catch this exception in comment: #403 (comment) ?
After these commits to fix your observations, I ran VS and it fixed the CTRL + .

I walk through all my new commits and discovered that CTRL + . bug stoped in AlbertoMonteiro@ebdae16

So I started to mix the changes that I did in this commit, and I discovered that if I use the namespace CodeCracker.CSharp.Refactoring it will break when running VS.
So I moved to parent commit(AlbertoMonteiro@150a201) and ran VS again, the bug happend, stoped, and change the namespace from Refactoring to AnyElse and the problem was gone.

Why the simple namespace name change, breack when running on VS?

@AlbertoMonteiro You set the exception settings to catch all .NET Exceptions. If you don't do that, VS will not stop to let you inspect the exception. I don't know why, it should stop.
BTW, you also need to update the analyzer and code fix to use Resources for globalization support. See https://github.com/code-cracker/code-cracker/blob/cc44ad2419e25d794471b83867fbd08877af25dd/src/CSharp/CodeCracker/Style/ConsoleWriteLineAnalyzer.cs and the corresponding code fix.

@AlbertoMonteiro I can't see why the namespace would break the code. Try using the exception setting I talked about above and see if you can find what happened. Anyway, you are going to move it another namespace, so maybe this is moot.

@giggio commited the globalization support.
About the namespace breaking, I will record a video and upload on youtube , so you can see this weird behavior.

@AlbertoMonteiro Good job!
I did some small updates, check a475139 for more info. I got some edge cases that needed taking care of and the test file was on the wrong directory.

@giggio Thanks.
I will pay more antention next time!