I created a Business Object Library within the Web Solution and selected to run the Business Object Mapper ... the following error occurs.  I have also uninstalled and reinstalled SF 1.4.1 and still get the error message.  I also tried to run the Business Object Mapper from within the Example Web Application, same result.

Help!

Error Message is as follows:

SqlException
 Invalid object name 'DTEprojects'.

Source     : .Net SqlClient Data Provider

Stack Trace:
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
   at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
   at MicroFour.StrataFrame.Data.DbDataSourceItem.GetDataTable(DbCommand Command, OnChangeEventHandler CallBack)
   at MicroFour.StrataFrame.Data.SqlDataSourceItem.GetDataTable(DbCommand Command, OnChangeEventHandler CallBack)
   at MicroFour.StrataFrame.Data.DataLayer.GetDataTable(DbCommand Command, Boolean RegisterNotification)
   at MicroFour.StrataFrame.Business.BusinessLayer.FillDataTable(DbCommand CommandToExecute)
   at MicroFour.StrataFrame.AddIns.DTEprojectsBO.FillProjects(String[] ProjectPaths)
   at MicroFour.StrataFrame.AddIns.PartialClassBuilderDialog.BuildProjectNode(PartialClassBuilderVSProject Prj)
   at MicroFour.StrataFrame.AddIns.PartialClassBuilderDialog.BuildTreeView()
   at MicroFour.StrataFrame.AddIns.PartialClassBuilderDialog.InitForm()


Charles T. Blankenship
Senior Consultant
Novant Consulting, Inc.
704.975.7152
http://www.novantconsulting.com

CT,

I have recompiled the assemblies with the latest changes and attached them to this post.  To get your GAC and assemblies up to date, do the following:

1. Close down all Visual Studio Instances
2. Download the attachment
3. Extract all of the files (XML and DLL) to the "c:\program files\common files\microfour\strataframe" folder overwriting the existing files.
4. Open two Explorer Windows.  Navigate one to the "c:\program files\common files\microfour\strataframe" folder and the other to the "C:\Windows\Assembly" folder.
5. From the Common Files folder (where you extracted the new files) select the MicroFour StrataFrame...: AddIns.dll, Base.dll, Business.dll, DBEngine.dll, Extensibility.dll, Inherited UI.dll, UI.DLL
6. Drag the selected files into the "c:\windows\assembly" folder (GAC)
7. You assemblies will now be on the latest version.
8. Go back into Visual Studio and see if the error persists

If the error still occurs at this point, I know for a fact the the structure on the SQL Server does not match the business objects in the assemblies and we will need to get your data structures up to date.

Let me know if this gets you going.