|
| | | StrataFrame Beginner
 
Group: Forum Members
Last Login: 03/25/2006 6:08:39 PM
Posts: 36, Visits: 65 |
| | Started a new solution, after deleting the previous solution, and added a business object. When I went to the object mapper I say two business objects, one from my previous solution and the new one. I assume it's getting this information from the database, but could someone explain what is going on? Very confusing. |
| |
| | | 
StrataFrame Developer
Group: StrataFrame Developers
Last Login: Yesterday @ 9:47:36 PM
Posts: 4,115, Visits: 4,185 |
| I don't think this is coming from the database. More than likely you have a busienss object within your solution with two different namespaces. For example, the BO.cs has a different namespace than the BO.Designer.cs file. This will create a "Phantom" business object since technically they are in two different namesapces. This generally only occurs in CSharp projects since a namespace is required and if one is not specified in the Business Object Mapper, this can be the result.
Too verify, manually open the BO.cs and the BO.Designer.cs files and see if they have different namespaces. If so, change one of the them and only one should appear in the BO Mapper. |
| |
| | | 
StrataFrame Developer
Group: StrataFrame Developers
Last Login: 06/17/2008 9:28:35 AM
Posts: 2,649, Visits: 1,863 |
| Yes, the functionality you're seeing is coming from the database... the Business Object Mapper uses the StrataFrame database to persist settings for your business objects. The Business Object Mapper has a project record that it ties to your computer through the full path to your project file. Since the project you re-created had the same path as the project you deleted, the Business Object Mapper thought that they were the same project and thought that it was already configured.
So, when you delete and re-create the project, if you want to delete all of the settings associated with the old project in the Business Object Mapper, you'll have to go into the project properties of the Business Object Mapper and manually delete the project configuration.
You'll also notice that when you move your project to a different folder (as is the case when you don't "save" the project when you create it and it creates the project in a temporary folder until you save it permanently) you'll have to "re-configure" your project through the Business Object Mapper. NONE OF YOUR SETTINGS WILL BE LOST as the Business Object Mapper's project record is not deleted, but you'll have to re-tie it to the new path for the project file.
Hope this helps 
The "ghost" business objects Trent is talking about can also appear, just like he said, if the namespaces don't match on your business objects' files (half of the class is in one namespace, and half of the class is in the other namespace, and the Business Object Mapper thinks you've created two separate business objects with the same name, so it lists both of them).
www.bungie.net |
| |
|
|