Any issues with 1.7.3.5 in a multi-developer, multi-SF version environment


Author
Message
Alex Luyando
Alex Luyando
StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)
Group: StrataFrame Users
Posts: 112, Visits: 1.2K
Hi all. 

So I will find it difficult to not install 1.7.3.5 really soon, and am assuming I will need to allow the StrataFrame database to be installed/updated. Any issues with having other developers running prior versions of StrataFrame and taking their time to upgrade? We have some pretty mission-critical applications and I don't want to break their apps just because I want to be the first kid on the block with the latest release. 

Thanks, and nice having the MF gang back in the saddle. 

________________
_____/ Regards,
____/ al
Replies
Alex Luyando
Alex Luyando
StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)StrataFrame User (298 reputation)
Group: StrataFrame Users
Posts: 112, Visits: 1.2K
Thanks guys. So I'm reading your posts as saying "prior versions of StrataFrame will still work against a 1.7.3.5-upgraded StrataFrame database."  Clearly I'd prefer if everyone upgrades, but not everyone is an early adapter (and sometimes with good reason). That said seems you guys have always put out read-for-prime-time releases, even when they are marked as beta. 

Thanks. 

________________
_____/ Regards,
____/ al
Trent Taylor
Trent Taylor
StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 7K
Well, we have been using this release ourselves for a very long time.  It is solid.  But if you have older projects you want to leave on the older version, then one option would be to create a backup copy of the StrataFrame database and either keep it or create a new one that you upgrade to 1.7.3.5.  This way you can migrate things over a project at a time if you need to and still swap between them using the data source connection for StrataFrame inside of Visual Studio.  But in truth, it is always easier to move everything forward at once.

Backing the DB up is always a good idea though, no matter what! Smile
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search