Author Topic: 3.6/4.0 Side-by-Side Installation (Read 11075 times)

JourneymanDave · « **on:** March 15, 2004, 12:10:50 pm »

Probably ignorance on my part, but isn't there a way to run EA 3.6 and the release version of EA 4.0 on the same machine? Maybe install to different directories?

I was previously able to run 3.6 rel. 661 and 4.0 Beta 4 together, but as I'm installing the 4.0 rel. 720 (Release), I'm being prompted to uninstall the 3.6 installation.

I'd really like to have the ability to diagram using UML 1.x and 2.x, because for a while my clients will be in a transition phase between versions. It appears that with the 4.0 release version, I'll no longer be able to use the two side-by-side. Am I just wrong on this?

Bruno.Cossi · « **Reply #1 on:** March 15, 2004, 12:44:39 pm »

Hi,

this is actually a huge problem for us - one of our clients has close to 100 licences of EA, used on several different projects by multiple teams. New projects are starting to use EA4, but the existing work stays in 3.60 for now (will eventually be converted, but due to the repository being critical and the work on critical path, will not be converted for weeks at least).
Some of the people work on two projects at the time and need to access both EA3.60 and EA4.0 repository.
Is there any way how to get around it?

Thanks!

Bruno

sargasso · « **Reply #2 on:** March 15, 2004, 01:59:25 pm »

Good Question!

I am running 3.6 (prod) and 4.0 (in trial mode) on the same machine. Now that the "auto" convert bug is fixed (as at 718 ) I haven't had any major problems except...

I wish that there was some way to visually distinguish v3.6 models from v4! I have about 16 different models on the go - on the desktop, I'd love to be able to "see" which version the .EAP file is (without using names, of course) as I keep accidentally opening 3.6 projects in v4.

B

JourneymanDave · « **Reply #3 on:** March 15, 2004, 03:03:15 pm »

For the sake of completeness, I'll reiterate that I was able to successfully run the 4.0 beta along with the release 3.6 versions, with no issues.

If you need access to both of them simultaneously, consider hanging on to the beta for juuuuust a bit longer until this question can be answered.

If I have to choose, I'm moving to the 4.0 version because the enhanced feature set justifies it. It would be somewhat of a hardship to not be able to switch back and forth at the moment though, and I'm sure I'd have to uninstall/reinstall a few times to meet my requirements.

fredhirschfeld · « **Reply #4 on:** March 16, 2004, 09:26:12 am »

Ok, this suggestion may not be viable for many but... Maybe using some VM Ware products (MS, IBM?) to have the old EA working in. I know using VMWare for just this is a bit much but I have found VM software very useful in other areas too...

Fred

JourneymanDave · « **Reply #5 on:** March 16, 2004, 12:17:16 pm »

Quite funny, because I'm a big fan of VMWare also, and I've seriously considered installing 3.6 on one of my VMs to get around this

However, I still need to resolve this for several of the analysts on my team also, so my original issue still stands.

Thx for the suggestion.

Sam_Mancarella · « **Reply #6 on:** March 16, 2004, 03:45:47 pm »

Hello to all.

Firstly many thanks to all of you for bringing the EA3.60 / EA4.00 issue to light. We intend to address this issue by making a "legacy" version of EA3.60 for registered EA4.00 users, now that EA4.00 has been released.

What we would like from all of you is a "show of hands" to know whether what we propose is suitable, namely to create a build of EA3.60 that will:
- Install itself in a different directory (eg: "%programfiles%\Sparx Systems\EA360")
- Install itself with a different product ID (so that there are no install/uninstall/upgrade conflicts with current and future EA builds and releases)
- Not register itself as an automation server
- Not register itself as the default application for .eap file types

The only drawback to this solution as it currently stands would be that the "legacy" version will only open and modify EA 3.60 repositories and not EA 4.00-upgraded versions, nor will EA 4.00 open an EA 3.60 model without upgrading it - this also applies if the repository is accessed via automation.

All going well, this version should be available for registered users in the next couple days.

In the meantime, we'd be pleased to hear everyone's thoughts on the proposed solution.

Sam Mancarella
- Sparx Systems

sargasso · « **Reply #7 on:** March 16, 2004, 05:33:59 pm »

:)With the greatest possible respect...

Quote

- Not register itself as an automation server
- Not register itself as the default application for .eap file types

At the moment I would prefer that these applied to 4 not 3.6

Bruce

sargasso · « **Reply #8 on:** March 16, 2004, 05:57:32 pm »

Sorry Sam,
That wasn't a go at v4.0

I have 80+ analysts here that we have to introduce to UML 2, have them trained and modify the ISD processes to use UML2.

In addition to that, I have to somehow validate XMI for UML2 and check that we can adequately interface system models with projects that use "a certain other" UML modelling system.

My optimal path would be to have small groups of analysts
1. investigate the benefits of UML2 to their systems i.e. use EA4 as a plaground rather than the standard tool issue.
2. estimate the effort required to convert their modelling to UML2
3. migrate systems on a controlled basis with oversight from the program office.

We have "just" stabilised their use of UML at the 1.5 level - all the process and methods material relates to 1.5 modelling techniques and so does the training material.

So, while I can appreciate the move to UML2 and EA4, I just cant let them "get loose on it" without the proper controls. If we did they would all invent their own techniques, model structures etc etc and goodbye reusability, interchange between groups etc etc all the things we have only just started to measureably achieve.

Bruce

p.s. Under Bruce's 4 stages of technology adoption theory:

For UML 2 I am currently very much at upper level 1 / lower level 2 at the moment. I am waiting on OMGs expecetd release of the spec at end of April to see if they've addressed certain issues.

JourneymanDave · « **Reply #9 on:** March 16, 2004, 07:45:07 pm »

Sam, for my own purposes, your proposed solution would work out great. I'd prefer that 4.0 becomes the default application, but 3.6 is still made available for ad hoc use. This was effectively the way I was working while testing the 4.0 beta. I'm lucky in the regard that I don't have the same amount of time investment in training that Sargasso does, so my pain is easier to manage

Appreciate the quick response to this issue.

wmac · « **Reply #10 on:** March 17, 2004, 09:22:45 am »

Hello,

To be honest I am not very familiar with UML 2.0 so I will work with 1.4 until I know enough about 2.0

Besides I have 3 projects which I have worked with 1.4 and I am not sure I know enough to change them to ver 2.0. I think I need 1-2 months (may be more) before I can start working with EA4 on serious projects.

Mac

dlundy · « **Reply #11 on:** March 17, 2004, 02:22:47 pm »

I have been prepping for UML 2 for a while so that is not a concern.

However, the "auto" update feature that converts 3.6 automagically to 4.0, is a concern.

I take it that 4.0 does this without notification?

Dan

Sam_Mancarella · « **Reply #12 on:** March 17, 2004, 09:24:34 pm »

Quote

However, the "auto" update feature that converts 3.6 automagically to 4.0, is a concern.

I take it that 4.0 does this without notification?

This is not the case - EA actually performs the upgrade via the Upgrade Project Wizard which should show when you open a pre 4.0 model.

NB: It will also backup your model (if it's an eap file) before the upgrade is performed.

Sam Mancarella
Sparx Systems

Bruno.Cossi · « **Reply #13 on:** March 17, 2004, 09:56:25 pm »

Hi Sam,

this would be perfect for us!
Thanks,

Bruno

Quote

Hello to all.

Firstly many thanks to all of you for bringing the EA3.60 / EA4.00 issue to light. We intend to address this issue by making a "legacy" version of EA3.60 for registered EA4.00 users, now that EA4.00 has been released.

What we would like from all of you is a "show of hands" to know whether what we propose is suitable, namely to create a build of EA3.60 that will:
- Install itself in a different directory (eg: "%programfiles%\Sparx Systems\EA360")
- Install itself with a different product ID (so that there are no install/uninstall/upgrade conflicts with current and future EA builds and releases)
- Not register itself as an automation server
- Not register itself as the default application for .eap file types

The only drawback to this solution as it currently stands would be that the "legacy" version will only open and modify EA 3.60 repositories and not EA 4.00-upgraded versions, nor will EA 4.00 open an EA 3.60 model without upgrading it - this also applies if the repository is accessed via automation.

All going well, this version should be available for registered users in the next couple days.

In the meantime, we'd be pleased to hear everyone's thoughts on the proposed solution.

Sam Mancarella
- Sparx Systems

Sam_Mancarella · « **Reply #14 on:** March 22, 2004, 06:37:32 pm »

Hi to all.

Just a quick post to announce that the compatibility edition of EA 3.60 for EA4.00 users is available in the registered users download page.

To Reiterate from my previous post, this edition of EA3.60 will:
- Install itself in a different directory (eg: "%programfiles%\Sparx Systems\EA360")
- Install itself with a different product ID (so that there are no install/uninstall/upgrade conflicts with current and future EA builds and releases)
- Not register itself as an automation server
- Not register itself as the default application for .eap file types

Remember also that the "legacy" version will only open and modify EA 3.60 repositories and not EA 4.00-upgraded versions, nor will EA 4.00 open an EA 3.60 model without upgrading it - this also applies if the repository is accessed via automation.

Note also that EA4.00 upgrades an EA3.60 model via the model upgrade wizard, which runs when an EA3.60 model is opened in EA 4.00.

Best Regards,
Sam Mancarella
- Sparx Systems

Sparx Systems Forum

News: