Development Environment
.NET Framework ver 2.0.50727
Windows Server 2003, Enterprise Edition Build 3790 (Service Pack 2, v.2825)
Visual Studio 2005 Professional Edition ver 8.0.50727.762 (SP.050727-7600)
Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Standard Edition

StrataFrame Assemblies I am using
// Assembly MicroFour StrataFrame Base, Version 1.5.0.0
// Assembly MicroFour StrataFrame Business, Version 1.5.0.0
// Assembly MicroFour StrataFrame DBEngine, Version 1.5.0.0
// Assembly MicroFour StrataFrame Extensibility, Version 1.5.0.0
// Assembly MicroFour StrataFrame Inherited UI, Version 1.5.0.0
// Assembly MicroFour StrataFrame Install, Version 1.3.2515.18818
// Assembly MicroFour StrataFrame Security, Version 1.5.0.0
// Assembly MicroFour StrataFrame UI, Version 1.5.0.0
// Assembly MicroFour StrataFrame Install, Version 1.3.2515.18818

 
Steps to re-create
1. Application Database Connections, StrataFrame Data Store is selected, and is valid, Selected
2.  File->New->Project
3. Visual C#->StrataFrame Windows Application
 -- Succeeded
4. StrataFrame->Solution Preferences
 -- No project listed in project drop down, no languages listed, no project listed under security preferences
5. Cancel
6. Save all and rebuild solution
7. StrataFrame->Solution Preferences
 -- No project listed in project drop down, no languages listed, no project listed under security preferences
8. StrataFrame->Business Object Mapper
  -- Odd, the project is listed under available projects here!
9. Highlight project name and select Configure Project under Actions
10. Select New in Choose Project dialog
11. Give project a name, Description, and select the Sql Server connection string (local server, trusted connection, projectname is the db name (the default))
12. Dialog->Save Changes? -- select Yes
First Error-- Broken Rules Exist red arrow highlights the Project Name, "A project already exists with this name"
 -- Now, I created a scratch project using a new name, for sure it did not exist. So I cancel out, and cancel out of the Choose project dialog
 and then close the Business Object Mapper.
 13. Rebuild Project, save all then pull up the Business Object Mapper again, red x next to project name, highlight and select configure project.
 14. Project now available in Choose Project, select it and  hit edit.
 15. Prior information is all there as I added, I then hit the Okay Button. it is at this point I get the unhandled exception error:
 The exception unknown software exception (0xe053534f) occurred in the application at location 0x77e4bee7.
 16. Click Okay, VS crashed out.
 
 I start up VS again, Pull up the Business Object Mapper, Configure Project, Highlight the new project and select "Select", first time I do this it is okay,
 the second time I get the unhandled exception error again?
 
 Does anyone know why or what is happening???

You can turn on debugging of the data sources used by the StrataFrame addins with some registry keys:

Key: HKLM\Software\MicroFour\VSAddIns

Values:   DebugMode / DWord / any value other than 0
             DebugFile / string / the full path to an output file (i.e.: "C:\Debug.html")

Then, if you would run the BOMapper until you get the error and attach the debug file to your next post.  You'll probably have to zip it because I don't think you can directly post an HTML file.

Thanks, I did and got the same failure but captured the debug file. I rar'd it up and attached it.

Ray,

This file was so large that it was not usable.  Would you please get out of Visual Studio, delete the debug HTML file.  Then go in and go straight to the BO Mapper where the error manifests itself. There was so much in this file it was as though you had been running much longer and it was difficult to read.  Thanks.

I did as you asked. The odd thing is, the debug file is only 7 megs when I go straight into the business mapper, it is not until I hit the Okay button and Visual Studio crashes out that the file grows to over 95 megs! So, that might help narrow it down, but it is tiny until that point and I am going straight into the project then the mapper and configure, edit, and just hitting okay. That blows up Visual Studio. I'll send another debug file, but, its the smallest I can get it.

For some reasons, when the business object attempts to save the record, SQL Server thinks that there is a concurrency exception.  We are testing OptimisticAllFields within that business object, and something in your SQL Server install is different from the norm... collation, case-sensitivity, not sure.  So, SQL Server won't let the record update because it detects a concurrency issue, but the business object realizes that there is not a concurrency issue, so it automatically resaves the record... at which point, it gets into a loop.

So, we changed the BOMapper business objects to use row versioning and stored procedures to circumvent the issues with concurrency in different database environments.  The changes will be in the next update.