An annoying bug in Visual Studio 2005 beta2 when using Developer Express' controls

A lot of people have noticed a highly annoying bug in Visual Studio 2005 when dealing with Developer Express' controls. The description of the bug goes like this:

During the build of the solution IDE starts throwing a modal dialog box with error icon: "cannot access a disposed object. Object name: 'DesignerFrame'". If you click OK the same dialog reappears and you'll never get rid of it (regardless if you click OK or not) and you won't be able to close IDE either (you have to resort to Task Manager for killing it). Regardless of the issue the solution starts running if it was built properly.

AFAIK this is the problem in Visual Studio 2005 Beta 2 and there are two workarounds to this problem:

  • upgrade to a CTP later then beta 2 (preferably july CTP since there is no public august CTP version of DevExpress controls) where error doesn't appear anymore
  • close all designer windows within IDE before doing build

Change in nullables implementation is giving results

Almost a month ago the blogosphere was full of reporting the change of nullables implementation starting from August CTP. I was curious if this change affected the Developer Express components - they didn't work with nullables before. So the kind folk at DevExpress provided me the build compatible with August CTP. The preliminary results are very encouraging: it works, or better, you are free to bind nullable properties to DevExpress controls. Developers using ORM products that support nullables will be very very happy about this (me included). What can I say other than: Good move, Microsoft.

New version of Spell Checker plugin for CodeRush(DXCore)

I just released a beta of new Spell Checker plugin version (a plugin for DXCore/CodeRush for Visual Studio.Net). The main new feature is that it does spell checking of XmlComments and Comments, too. Furthermore, different settings and dictionaries can be used for different categories.

So, if you are interested in a free spellchecker for your Visual Studio.NET code, go for it. Feedback is appreciated.

You'll find it here.

Creating DevExpress' XtraForm derived form as partial class

Developer Express offers an XtraForm (a windows form derived from Form class) with Look & Feel default set so you don't have to use LookAndFeel objects to centralize its appearance. One annoying feature is that when you create an XtraForm derived class using Add/New Item... in VS.NET 2005 beta 2 it will create traditional Form class structure: one file and no partial classes as Form does.

If you want partial class (possible only in Visual Studio.NET 2005) and XtraForm the solution is rather simple: Create a standard windows Form instead, go to its code and change the base class to XtraForm. Voila. The same is true for XtraUserControl.

Refactoring in VB.NET 2005?

C# 2005 does refactoring and this is a well known (and very welcome) feature by now. A less known fact is that VB.NET 2005 does refactoring, too. Not out of the box. Instead, Developer Express provides a free refactoring plugin based on DXCore (free engine used by CodeRush for Visual Studio.NET). Refactoring is code modification without alterating external program functionality to put is shortly (for more information about refactoring follow the refactoring links). So, if you are "on" VB.NET 2005 beta 2, go check refactoring.
There is also a Refactor! PRO version (not free, works in all Visual Studio.NET 200x versions) that has additional refactorings that are useful in C#, too. Follow the inline links to learn more (so I don't have to re-write those information :-)). Very interesting feature of Refactor! PRO is that it is extensible - you can add your own refactorings if you wish to. Isn't that cool?