>That's because the MM .NET DevExpress assemblies are compiled with the previous version of DevExpress. We are in the process of releasing the new version of our subclasses, but for now, you can do the following:

>1. Open the MM .NET DevExpress project
>2. Remove references to the old DevExpress assemblies
>3. Add referencdes to the new DevExpress assemblies back in
>4. Add your own strong key file to the DevExpress project (if you don't know how to do this, see the MM .NET Dev Guide topic "Recompiling MM .NET Assemblies" for details.
>5. Recompile the project.

This has nothing to do with an MM.NET DevExpress project. These are working applications built long before MM.NET was installed on the machine. When you install MM.NET DevExpress controls, then attempt to open your existing projects, the forms cannot be opened because of the NullReferenceException error.

Following the instructions above did not help, unless you are suggesting I should convert the existing projects to MM.NET. I always use the above procedure when installing new DLL's anyway, but I'm under the impression that when I install MM.NET DevExpress controls, it should not affect applications that use DevExpress 6.2.6 controls. Is that correct? Should I replace the DevExpress assemblies in existing projects with MM.NET DevExpress assemblies?

DevExpress thinks that this is an installer issue: "This problem may occur if the latest update of our suites #was not# installed correctly. Note: I recommend that you install the latest update of our suites which was shipped today - DXperience 6.2.6. This update contains code fixes for a bug we have detected with the build you are using which may cause such a problem."

However, the problem is resolved immediately as soon as MM.NET DevExpress controls are removed from the machine.