Excellent   The good thing about OnPaint is that you can try/catch it and if it fails, the WM_PAINT message is sent so much that it will just paint again (likely succeeding the second time).

Well Ben, whatever you did worked.  I haven't had the error since putting those assemblies on my machine.  I have gone into the mapper changed some customizations and built some partials all without error.  And the form actually comes up normally, no more transparencies where the paint didn't work.   THANKS!!!

Here are the DLLs with the try/catch in the OnPaint.  Maybe this will allow you to use the BOMapper on your computer.

That is a very, very odd error.  For some reason, it seems that the SQL query is pushing a WM_PAINT message up the WndProc call sequence on a background thread.  The WaitOne means that the SQL Server client is pausing the main thread while the background thread does the processing, but I have no idea why it's trying to paint during that.  We can put a try/catch in the OnPaint to prevent an exception from being thrown, but other than that, all I know to do is check the thread context to make sure it's on the main thread before painting.

Oh, and just worth pointing out here.  I was able to go to another machine with the same assemblies and bring up the BO Mapper perfectly.  It points to the same database and everything.  Not sure exactly what that tells us, but it almost seems to be isolated to my PC.

Well, I'm not sure if this helps or not but I did get this screenshot out of the whole thing.  It actually gave me an error when I tried it again....and it looks like a memory problem of some kind.  But it did actually load up all of the projects before it gave me the error that time.  Here's the screenshot.

Well i finally got back to what I was working on after being pulled onto a different project.  I downloaded the assemblies and put them in the gac.  It looked promising, since the BO mapper came up and let me actually create my BO's and build some partials.  However, it still had that 'transparent' look on some of the windows.  The kind of thing that looks like a memory problem usually.  Then when I tried to go back in it a second and third time it crashed the IDE.  So we are back to where we started.  What should I do now?  Any ideas?

If you downloaded the SF assemblies from the previoys post, be sure to update the UI assembly with this one.  There was a minor bug with the disabled states of a TextBox or MaskedTextBox.  Sorry

Andria,

I have attached the latest SF assemblies which will be part of the 1.6.2 release.  These are what we have been running on for a while and have been tested quite a bit so I am not concerned for you to run on them.  I left out the Inherited assembly since you probably have the latest version of DevExpress already in your references and nothing else has changed in that assembly.

I do not think this will fix your problem...but it is worth a shot.  I think it is data related.  Try this first, and if it does not work, then the only thing I can do is have you send your your SF SQL data (mdf or a backup) via a PM or something and I would have to debug it.  There is no way for me to determine what is going on in the DTE without debugging it.  Thanks.

Hi Andria,

While we didn't have this problem we did have an issue with the BO mapper that someone else also reported and the SF guys fixed with a new DLL. Sorry but I don't know who made the post of what forum it was in but it was in the last 4 to 8 weeks. All I can suggest is that you trawl the forums looking for a post with attachments - it may (or may not) help. It certainly fixed the problem we had.

Cheers, Peter