StrataFrame Forum » StrataFrame Application Framework - V1 » Issues » Moving profiles.....

Moving profiles.....

Keith Chisarik — Tue, 08 Aug 2006 13:52:27 GMT

I have some work / testing done on PC1, I want to move it to PC2. How?

When I do a clean install of DDT to PC2 and select "Open Profile" all I can select is "New".

This leads to another question, sharing "profiles" or metadata and implementing databse/table updates.

Right now we use Stonefield, so I equate the DDT to that. If I make changes to table structures I know to make certain files available for other developers to import to their workspace, then the framework detects the changes and updates the databases in place.

So, how do I move/share/update DDT metadata (.pkg files correct?) to 1) another box 2) other devs 3) client sites.

Our current framework has the ability to update database structures in place when it detects that we have updated the meta-tables. Does SF do this?

I guess I have made a few assumptions about the DDT and want to clarify it feature set.

I am practically just trying to move my "play stuff" to my laptop for Friday and issues with that led to these other questions.

Thanks.

RE: Moving profiles.....

StrataFrame Team — Tue, 08 Aug 2006 13:52:27 GMT

No problem... the deployment dialogs are also stored within the DBEngine dll (the ones that pop up when you deploy the profile from within the DDT). So, if you need one of the dialogs, they're in there as well.

RE: Moving profiles.....

Keith Chisarik — Tue, 08 Aug 2006 13:49:56 GMT

totally what I wanted to hear......

Thank you.

RE: Moving profiles.....

StrataFrame Team — Tue, 08 Aug 2006 13:47:32 GMT

Yes, to update a single database, you will need to run the Deploy to Server option within the DDT for the open profile. To encapsulate the database deployment within an application, you will need to use the MicroFour StrataFrame DBEngine.dll assembly. It contains the MicroFour.StrataFrame.DBEngine.DatabaseMigrator class. This create a new instance of this class and use its DeployMetaData() and DeployData() methods to deploy the structure and the static data, respecively. Each of these is non-blocking and raises events to show the progress of the operation. Within you're application, it would be probably best for the app to store off the last modified date of the shared .pkg file within the registry. If the data changes, then re-deploy the structure.

RE: Moving profiles.....

Keith Chisarik — Tue, 08 Aug 2006 13:42:53 GMT

That I get for the development environment, what is the procedure to publish changes to an in place application (assume Winforms since ASP.NET would be a server based update).

Example:

I have an application in place using a local SQL Express database as the datasource, I make changes to both the application and its database structure (tables, indexes, etc). How do I update my in-place customer DB? Do I run the DDT deploy? Can that be encapsulated into an application?

What I have now is seamless updates to data structures that are handled by my current (custom) VFP Framework when it detects changes to Stonefield metadata. Will i be able to accomplish that with SF out of the box? with some work? or not at all?

Thanks.

RE: Moving profiles.....

StrataFrame Team — Tue, 08 Aug 2006 13:15:34 GMT

Both PC1 and PC2 need to point to the same SQL Server database in order to both be able to see the profiles that have been created. All of the meta-data is stored within the StrataFrame database and is only exported to the .pkg file to be deployed at a remote site. So, to copy the data from two computers that cannot see the same database, you will need to a) copy the data from database A to database B or b) create a .pkg file for the profile on PC1 and create a new profile on PC2 and then import the .PKG file from PC1 into the new profile on PC2.

As for the framework detecting the changes to the meta-data for business objects, any time a structure change is made, you must open the Business Object Mapper and rebuild the partial classes for the tables that have changed. This will update the structure on the business objects to match the current structure of the meta-data, sql tables, etc.