While working on the next release of the Windows 7 Boot Updater I separated the core updating system from the interface. It is generally good practice to do this since then it is modular. Since Visual Studio 2010 no longer supports Intellisense for C++/CLI I decided to convert the interfaces to C# since they were almost purely System.Windows.Forms. The core remained C++/CLI since it had a lot of native dependence. This created another problem. The only easy way to distribute this is as a core DLL (from the C++/CLI code) and a separate EXE (from the C# code). But I…
To make static manged classes in C++/CLI you use the combination of keywords abstract and sealed. Static managed classes can only contain static members (functions and variables) and cannot be instantiated or inherited from. I believe they are nicely sped up, but I haven't verified this.
However, if you add delegates or literals to the static class, the compiler complains:
I just completed re-imaging my laptop (my main computer) so that I could move up to Windows 7 and Visual Studio 2010. I do a lot of work in Visual Studio (most of my projects are C, C++, C++/CLI, or recently C#). I thought the new addition would be great and I heard about a number of new features that I was excited about. However I should have been a bit more cautious. I have found two major issues so far, only one of which I have found a solution to.
I have done a huge overhaul to the website. It may not be completely noticeable at first since I have been very diligent in maintaining the style. However, the site is now mostly run by Habari. I picked Habari as the content-management system since it was powerful yet very easy to modify for my own person use. I created an entire theme so that the style remained consistent, but gained all the power of being able to have posts and comments managed behind the scenes.
Additionally I had to create a plugin which did a lot of additional work such …

