I'm really looking forward to this conference and to Las Vegas of course. We are about eight people from here, coming from different companies, who are attending the conference. We're leaving this Saturday and will stay for a little over a week, so hopefullt we'll experience more than just the conference, e.g. Las Vegas night life, Grand Canyon, etc.
So if any of you are going there, we might bump in to each other :)!
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.
When I get back in about two weeks from now, I hope there will be a new version of DXCore available, so that we can get the last few things in to the upcoming version of Code Style Enforcer.
I am not sure which of these three things that is the reason for me to start this blog, maybe a combination, time will tell...
One reason, probably why I started, is to spread the interest in plug-ins, or add-ins, for Visual Studio. DXCore, by a company called Developer Express, is a really good extensibility framework for these kinds of things. Did I forget to mention that it is free!!!
I myself have made a plug-in that uses DXCore for checking the code against a configurable code standard. I will tell you more about this in my upcoming blog. There will also be a special page dedicated to this project "Code Style Enforcer", where you can download the latest version.
Another hot topic of interest to me right now is the new upcoming .NET Framework 3.0, former WinFX. I am currently involved in a project utilizing WPF, which I think is a really good upgrade from Windows Forms. It is therefore very likely that some topics in this blog will be about .NET 3.0.