Author Topic: Source Safe - Configure for Entire Project? (Read 6008 times)

DMT · « **on:** November 03, 2003, 08:50:05 am »

Now that Source Safe integration has been added, I intuitively expected to do something like the following, based upon my experience with Visual Studio:

1. Configure EA so it recognizes that I'm using Visual Source Safe, providing my user name, etc.
2. Right-click on the root node, and click something like, "Add Model to Source Control..."
3. Specify the name and location of the project in Source Safe.

That's it. Now, this isn't EXACTLY what I'm seeing. It appears that I need to configure source control for every single package in the entire project, including sub-packages. It appears that I need to manually type in file names and versions.

It's really strange, and I'm not sure exactly why I would need to go through all of this. One mouse click and one dialog should handle it.

Is there any other way to configure a model to use source control? Is it really this difficult? Or am I missing something.

Thanks in advance,

Dave

Phil_Bachmann · « **Reply #1 on:** November 04, 2003, 04:54:09 pm »

Yes, it is that difficult.

It was envisaged that people would want to version only a few packages in a model, and that being able to specify the name of the export file was more import than quickly marking a package as version controlled.

Phil Bachmann
Sparx Systems

DMT · « **Reply #2 on:** November 04, 2003, 05:51:19 pm »

Hmmm. OK. I guess it isn't what I was expecting when it was announced. I'm trying to eliminate the shared database on our network by checking the model into Source Safe in its entirety.

Thanks.

- Dave

Barry_Pearce · « **Reply #3 on:** November 11, 2003, 05:57:55 pm »

Hmm. This is a MAJOR disappointment and means that we will have to change *our* working practices - rather than the tool *suporting* our practices.

I also feel this makes the tool less useful for large scale - multi-developer development where version control of packages is crucial to control of the product and releases.

In Rational Rose you can control EVERYTHING....and sub-packages may be controlled as well.

It seems odd that we would only version control a small number of packages!? After all - EVERYTHING in our system is version controlled - our release management systems rely on it - and how else do you support previous versions if you cant go back!?

----

What I really want to see in EA (given we are new users of the corporate version - chosen as a product instead of Ration Rose...) is the ability to version control EVERY package - parent & child - thus providing MAXIMUM resuse across projects, and maximum developer concurrency within a project based on a distributed development environment - replication is not enough - because the source code generated from the model is based on a package - the replication method of sharing means the two can become out of sync - a problem solved by version controlling and releasing the source code & package together....

I can explain in clearer more detailed definitions if required....but at the moment this is hampering us quite severly.

DMT · « **Reply #4 on:** November 12, 2003, 07:26:07 am »

Proposed solution:

1. Open Visual Studio
2. Copy how it works with source control.

I know, an oversimplification, but this is an example of "if you can't do it right, don't do it at all." I'm sure a lot of time and energy went into designing and coding the feature, but it was designed in a fashion that doesn't solve the problem.

Barry_Pearce · « **Reply #5 on:** November 13, 2003, 03:10:42 pm »

Indeed. We use CVS with distributed offline developers - the CVS repository is our central means of sharing and controlling - so the lack of granularity certainly doesnt help....ho hum..

EaChris · « **Reply #6 on:** November 19, 2003, 05:27:47 am »

Indeed, this would be very helpful.
On each level Xml generation would have to generate placeholders for all child nodes (with relative paths to their xml file) and trigger generation of these XMLs in a subdirectory.
Best regards,
Chris

Phil_Bachmann · « **Reply #7 on:** November 19, 2003, 04:17:41 pm »

The latest releases of EA now support a feature that allows sub-packages to be versioned.

Does this extra granularity solve people's problems?

Is there more required?

Phil Bachmann
Sparx Systems

Barry_Pearce · « **Reply #8 on:** November 25, 2003, 06:43:59 pm »

Ill test the new one in about 6 hrs time - Ill let you know Phil.
Cheers.

Cryolitte · « **Reply #9 on:** March 23, 2005, 09:01:02 pm »

Allowing sub-packages to be individually versioned is definitely an improvement.

Could you also consider adding a feature to allow individual elements to be version controlled, like files in VS.Net? That would be great.

Sparx Systems Forum

News: