Below the steps that follow:
-Desistalação of StrataFrame 1.6.6
-Removal of the folder StrataFrameSourceCode 1.6.6
-Reboot the computer
-Installation StrataFrame 1.7.3.1
-Installation StrataFrameSourceCode 1.7.3.1
-Reboot the computer
-Checking the DLL in Assembly
-Build-MicroFour StrataFrame Inherited UI with DevExpress 9.1
-Changing the DLL in my projects
-RebuilAll-BOs of all of my project

After these steps, continue to build problem throughout my Bussines Objects.
- Error 2 'LibraryApp.BusinessObject.boEventos.Dispose (bool)': no suitable method found to override C: \ System Athena \ LibraryMonitoramento \ BusinessOhject \ boEventos.Designer.cs 26 33 LibraryMonitoramento

-Error 117 'LibraryApp.BusinessObject.boEventos' Does Not Contain a definition for 'AddSecurityKey' and no extension method 'AddSecurityKey' accepting a first argument of type 'LibraryApp.BusinessObject.boEventos' Could Be found (are you missing a using directive or an assembly reference?) C: \ System Athena \ LibraryMonitoramento \ BusinessOhject \ boEventos.Designer.cs 46 18 LibraryMonitoramento

And in some other messages appear Bussines Objects:
- Error 94 'LibraryApp.BusinessObject.boTipoOS.OnCheckFieldSecurity (MicroFour.StrataFrame.Business.CheckFieldSecurityEventArgsBase)': no suitable method found to override C: \ System Athena \ LibraryMonitoramento \ BusinessOhject \ boTipoOS.Designer.cs 627 33 LibraryMonitoramento
- Error 92 'LibraryApp.BusinessObject.boTipoOS.GetFieldEnumType ()': no suitable method found to override C: \ System Athena \ LibraryMonitoramento \ BusinessOhject \ boTipoOS.Designer.cs 601 37 LibraryMonitoramento
- Error 89 'LibraryApp.BusinessObject.boInstaladora.OnCheckFieldSecurity (MicroFour.StrataFrame.Business.CheckFieldSecurityEventArgsBase)': no suitable method found to override C: \ System Athena \ LibraryMonitoramento \ BusinessOhject \ boInstaladora.designer.cs 491 33 LibraryMonitoramento


What can it be happening?

Ivan Thanks for the tip, but in SF 1.6.6 I had this feature. The same BO in two different projects.

Any chance of maintaining this compatibility?

Hi Malcon.

I have a feeling this has been this way all the time, but since you had it working before I really don't know what could have happened. I will forward this to the guys, but I think your best bet at the moment would be to name them differently and carry on.

Malcon,

It still works as you can have the same BO name in two different namespaces.  The issue is not as much the different assemblies, but namespaces.  Make sure that your namespaces are correct as this would just be a standard .NET related issue as you cannot have to identically named classes occupy the same namespace unless they are partial to each other, in which this case they would not be.

I would be more than happy to look at this, but in these cases, if you could create a simple app that reproduces the scenario, then I can look at your configuration to see what the issue is.  Sometimes screenshots and forum posts don't give us that "ah-hah" moment since it would something else in the mix.

Thanks!