Glad to hear you found the problem. Looking forward to the new release.

-Larry

We isolated and came up with a fix for the problem that we will release today.  Ultimately it has to do with a problem on the SQL Server.  It is not giving us some character back when the DAL is attempting to determine if there is a concurrency exception.  Regardless, we came up with a work around and it will be in the official 1.4 release that should be on the site later today.

Thanks for the heads up on this one.

Trent,

In a previous post I mentioned that Visual Studio was crashing when working with Object Mapper and that I received a message back from MS referring me to MS Article ID: 915038. I’m having my Help Desk contact MS to get the hot fix to see if it resolves the problem. In the meantime here is the sequence of events that repeatedly causes the problem in case you wish to try a duplicate it. I'm using the 4/5/06 pre-release version of the framework.

1.       Create a SF BO

2.       Open Object Mapper and map the BO to a SQL Table

3.       Rebuild All

4.       Close Object Mapper

5.       Open the designer file for the object and modify code for a field

6.       Copy modified code

7.       Open Object Mapper

8.       Double Click on the field to be customized

9.       Check Custom Code Option

10.   Paste in custom code

11.   Click Ok to close Window

12.   Double Click on field that was just customized

13.   Uncheck Custom Code OR modify code OR do nothing

14.   Click OK to close window

15.   After about 20 seconds VS crashes.

It appears that once a customization has been made it cannot be modified. The only way to change a field that has be customized is to double click on the field in object mapper and select Clear Customization. Once that is done the field may be re-customized.

-Larry