Wednesday, November 26, 2008, 09:11 AM - CodeRush/Refactor!A lot of Resharper people are complaining about the lack of CTRL + T (Go to type) feature in CodeRush, but I can now happily announce that a similar feature does exist.
The feature is called QuickNav in CodeRush and it must be manually configured in the DevExpress Options menu. Below the IDE category, you'll find Shortcuts where it's possible to change the key combination for a certain Command or add new ones. In order for the QuickNav to work optimal for both finding types and members to Shortcuts must be added.
I've mapped the "Go to type" feature to "CTRL + T", with QuickNav as command and AllTypes, , AllVisibilities, CurrentSolution as parameters (note the empty members param).
In order to get the "Go to member" feature, I've mapped it to "CTRL + ." with QuickNav as command and AllTypes, AllMembers, AllVisibilities, CurrentFile as parameters.
Wednesday, November 12, 2008, 08:37 PM - Code Style EnforcerThe new Code Style Enforcer version is 2.2.10.
• Settings file and default location for custom rules is changed to the user's documents folder. UAC should no longer be an issue.
• Rules are now only enforced for C# and VB projects/documents.
• Possible to activate/deactivate Code Style Enforcer for each individual project in a solution.
• Method parameters are now checked for violations again.
• Implicit and explicit cast operators no longer report invalid violations.
Friday, September 26, 2008, 01:20 PM - Code Style EnforcerIt's been way to long since I released a new version of Code Style Enforcer, but now I've finally took the time to get back into the code.
A new version can be expected really soon, it will mainly contain some fixes for reported bugs, e.g. invalid violations reported for implicit and explicit cast operators, and similar things.
I'm also going to have a look at the UAC issue and change where settings and rules are stored, since now it happens below the Program Files folder, which is no good.
Tuesday, September 23, 2008, 04:57 PM - Code Style EnforcerToday when I got back home from work I saw that Avast updated its virus definitions, so now it doesn't report a virus/worm anymore.
I must say that Avast took this false positive very seriously, since they fixed it within 24 hours.
Monday, September 22, 2008, 06:39 PM - Code Style EnforcerA couple of users have reported that Avast reports a virus/worm in the Code Style Enforcer zip file, or in the setup.exe to be more precise.
This seems to be a false positive, based on the following reasons.
I've scanned my computer without any viruses being found, but as soon as I build the installation in Visual Studio, Avast reports a worm in the setup.exe.
I've uploaded the setup.exe to Virus Total, see report, where 2 out of 35 virus scanners reports a possible worm.
I've now sent the setup.exe file to the Avast team, in order for them to verify that it indeed is a false positive, so that they can update their virus definitions for the future.