StrataFrame Forum » StrataFrame Application Framework - V1 » Business Objects and Data Access (How do I?) » Migration Issues 1.6.6 to 1.7.3.1

Migration Issues 1.6.6 to 1.7.3.1

Malcon — Tue, 14 Sep 2010 09:45:52 GMT

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?

RE: Migration Issues 1.6.6 to 1.7.3.1

Trent L. Taylor — Tue, 14 Sep 2010 09:45:52 GMT

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!

RE: Migration Issues 1.6.6 to 1.7.3.1

Ivan George Borges — Sat, 11 Sep 2010 06:38:39 GMT

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.

RE: Migration Issues 1.6.6 to 1.7.3.1

Malcon — Fri, 10 Sep 2010 07:40:57 GMT

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?

RE: Migration Issues 1.6.6 to 1.7.3.1

Ivan George Borges — Thu, 09 Sep 2010 19:17:51 GMT

Hiya. Have a look at this post:

http://forum.strataframe.net/FindPost27100.aspx

So, I guess my advice to you at this point would be to rename one of the BOs.

RE: Migration Issues 1.6.6 to 1.7.3.1

Malcon — Thu, 09 Sep 2010 15:47:47 GMT

There is no error message when mapping. It maps the BO "correctly," creates its properties, methods correctly. The VS that displays the error, since the namespace of Bo does not match the same namespace design of Bo.

Yes, I tried to map part of both Business Objects both projects.

As I understand it, the design of class always takes the first available project he finds in BoMapper.

Example, in Bo Mapper:
-Project_01
     -boOne     -boTwo
     -boThree
Project_02
   -boFour
   -boOne
   -boFive

The namespace of boOne in Project_02 is "Project_02", but the namespace design of this class will be Project_01.

Recalling, that only occurs in Businnes Objects of the same name.

RE: Migration Issues 1.6.6 to 1.7.3.1

Ivan George Borges — Thu, 09 Sep 2010 15:04:58 GMT

What message error do you get when you build the partials from the BO Mapper?

Have you tried creating a brand new BO and buiding its partial to see if it works?

RE: Migration Issues 1.6.6 to 1.7.3.1

Malcon — Thu, 09 Sep 2010 14:49:08 GMT

Hi Ivan,

Ivan, the BO Mapper I do not get it to work properly, I entered manually in the desing of each BO and changed the correct namespace

RE: Migration Issues 1.6.6 to 1.7.3.1

Ivan George Borges — Thu, 09 Sep 2010 14:28:00 GMT

Got it, let us know once you have it working. ;)

RE: Migration Issues 1.6.6 to 1.7.3.1

Malcon — Thu, 09 Sep 2010 14:18:39 GMT

Ivan is just that.
The class that is referencing the correct project, the more the designer of the class did not.
Partial Build tried but still did not work, I am manually changing the designer of my BusinessObjects to run.

Tanks

RE: Migration Issues 1.6.6 to 1.7.3.1

Ivan George Borges — Thu, 09 Sep 2010 13:51:36 GMT

Another thing, at some point we had to rebuild all the partials. Since you were on 1.6.6, I guess it could be the case, go to the BO Mapper and rebuild all your partials.

RE: Migration Issues 1.6.6 to 1.7.3.1

Ivan George Borges — Thu, 09 Sep 2010 13:46:27 GMT

Aren't you having a Namespace conflict?

RE: Migration Issues 1.6.6 to 1.7.3.1

Malcon — Thu, 09 Sep 2010 13:13:08 GMT

Hello Ivan,

I made the procedures more still with errors. I noticed a detail.
My solution has N projects, I have two boInstaladora, one at Project X and one Y in the project, and there is a reference between the two projects.
The error is this:
Error 4 'LibraryApp.BusinessObject.boInstaladora.Dispose (bool)': no suitable method found to override C: \ System Athena \ LibraryMonitoramento \ BusinessOhject \ boInstaladora.designer.cs 26 33 LibraryMonitoramento

The description of the error is in the 'LibraryApp.BusinessObject.boInstaladora' (LibraryApp project) but the error is saying that the project is LibraryMonitoramento.

Can this be? In 1.6.6 version

RE: Migration Issues 1.6.6 to 1.7.3.1

Ivan George Borges — Thu, 09 Sep 2010 11:52:25 GMT

Go ahead, have no fear!!! :D

RE: Migration Issues 1.6.6 to 1.7.3.1

Malcon — Thu, 09 Sep 2010 11:43:15 GMT

Hello Ivan,

in installation of 1.7.3 I´m ignored the installation of Phase Database Deployer with "fear" is that it overwrites the settings of my current BO.
Can I ask to repair the installation and install the Deployer Phase Database?

RE: Migration Issues 1.6.6 to 1.7.3.1

Ivan George Borges — Thu, 09 Sep 2010 10:16:07 GMT

Hi Malcon.

While instaling version 1.7.3 did you allow the installer to go through the database install? This will make sure all your SF tables are updated with the current structure.

After that, once you rebuild the your StrataFrame Inherited UI with DevExpress 9.1, I would make sure the GAC has the latest DLLs. You could even delete them all from the GAC and copy back from the Common folder (C:\Program Files (x86)\Common Files\MicroFour\StrataFrame). This will make sure all DLLs are current. Still, make sure you don't have old DLLs around the place, since Visual Studio could be pointing to some of them.

Let us know how it goes... ;)