This has nothing to do with the framework really since certain properties in .NET are stored using a string value instead of a typed reference.  I rename things all the time, but I generally leave them alone once I start incorporating them more and more into items such as ListPopulation settings and so forth because it no longer relies solely on the refactoring tools or the Rename... to catch the references.  In this case, you will have to do a search and replace to catch those places.

If you do a search and replace it should find and resolve most of your non-referenced settings for the BO but there is no guarentee until you execute that code.  So in short, you can rename the BO, or any other class for that matter.  But just remember that you may need to do a search and replace on top of the rename.

Hope this helps.

This is really not an issue, I just want to make sure I’m on the right track.

In working with StrataFrame it appears that the framework does not respond well to changing the name of a business object. While the object gets renamed correctly and compiles, when you go to run the app, references to the object in things like ListViewDataSourceProperty get lost. So I’m assuming that rule one should be, once you create a business object don’t rename it.

-Larry