Sunday, March 11, 2007, 07:00 PM - Code Style EnforcerI have now updated Code Style Enforcer, after receiving a bug report, that caused problems with selection in the code editor after invoking the context menu for rule violations.
I also added activation/deactivation of Code Style Enforcer to the context menu of the Visual Studio solution.
An uninstall of any previous versions has to be made from the Add/Remove Programs dialog, before installing the new beta version. Why? Well, it has to do with Custom Actions and Upgrade Installations, read my previous blog post for more thorough information.
Sunday, March 11, 2007, 06:21 PM - GeneralI ran into this problem when making an upgrade installation of Code Style Enforcer. The problem is that Code Style Enforcer uses custom install/uninstall actions in order to locate and ensure that the correct DXCore version is installed, among other things.
When doing an upgrade installation, the old custom actions assembly is first loaded, into the AppDomain, in order to call the uninstall method for the version currently installed. When it’s time for the Install method to be called in the new Custom Actions assembly, it still uses the old assembly since that is already loaded into the AppDomain. This has to do with how the Assembly.LoadFrom method works. This is really bad, not only since the new and perhaps updated Install method won’t be called, but since the old one will execute instead.
Microsoft suggests signing the Custom Actions assembly with a strong name in order to solve the problem, but I’ve tried that without any success. Another solution might be giving the assembly different names for each new installer version, but this seems like a really ugly solution to me.
For more information about this have a look at:
I’m really not sure if this problem is entirely bound to setup projects in Visual Studio and the Uninstall and Install/Commit custom actions implemented as part of an Installer class. I will try to migrate my setup project to WiX instead and see if I can get it work as expected.
For the interested, the Windows Installer XML (WiX) is a toolset that builds Windows installation packages from XML source code. I will tell you more about it in another blog post.
Sunday, March 4, 2007, 08:27 PM - Code Style EnforcerWell, it is Sunday evening and I promised a beta version this week and believe it or not, but the beta version 2.1.0 of Code Style Enforcer is finally here.
Please try it out and give me some feedback of both possible bugs or features wished for. Make sure to read the included "readme" file for information about what is new.
Code Style Enforcer now comes with a setup program in order to make life so much easier.
I really hope you like this new improved version...
The name refactoring to valid names is not always invoked, in fact it is never invoked for local variables, since not supported by the Visual Studio API.
Code rules from previous versions of Code Style Enforcer must be reconfigured using the installed Code Style Enforcer Configurator application, which can be found in the start menu.
Download Code Style Enforcer.
Monday, February 26, 2007, 07:34 AM - Code Style EnforcerNow my new apartment is finally fully renovated and I have also managed to get myself and all my furnitures in. Therefore I thought it would be a great idea to celebrate with a Beta of the upcoming Code Style Enforcer version.
I will probably publish the beta release this week and rest assured, it has been tested quite alot, I'm using it myself at work. But of course there will be bugs, but I hope you can help me to find those, before the final release.
After this release, I will try to relese CSE more often, with minor upgrades, instead of a huge one like this is going to be.
So please stay tuned...
Sunday, February 4, 2007, 06:04 PM - Code Style EnforcerWell, what can I say, my apartment is undergoing a total renovation and my work area is occupied by paint buckets etc. It is almost finised now, so hopefully I will be able to complete the last few things real soon. Trust me, it is coming!!!