Protected Projects by VSS can be edited

[ranjan]

Hi there,

We got projects stored in MS SQL-Server and version them with Visual Source Safe.

If a user makes a new connnection to a repository and fails/forgets to configure source control, some odd stuff happens:
1. He can modify the whole projects
2. The source control-configurations on other ea-installation get lost.

What are we doing wrong?
Regards, Ranjan

[Laura_H]

Did you ever get a answer about this?  We have come across the same "feature" using Oracle with Visual Sourcesafe.  Is it something that we just have to be careful of, or is it something that we are doing wrong?

[ranjan]

Did you ever get a answer about this?  We have come across the same "feature" using Oracle with Visual Sourcesafe.  Is it something that we just have to be careful of, or is it something that we are doing wrong?

Actually the second problem got fixed with release 770, which I am very glad about.

But you can still access and modify a versioned project, if you skip the version configuration, which is a bit odd. If you check this modified model out next time, the version from the versioning system is restored though.

As I didn't get an answer on my hint, I think they judge it as low priority.    

[Laura_H]

Thanks for that.  We are still on build 767 so we'd  better get upgraded!

[HowardB]

The problem of version controlled packages losing their association to VC configurations was due to a bug that was exposed in builds 768 and 769.  It was corrected in build 770.

The other behaviour that you observed, where version controlled packages were not locked when there was no defined VC configuration was not considered a bug.  In the case where a model uses a VC config that is not defined on a particular user's machine, EA has always displayed warning messages as the model is loaded, to alert the user to this fact.  The alternative, having all of the packages locked against modification in the event of a missing VC configuration or a failed connection to you VC system was considered  much less desirable.

This area of functionality has been further improved in EA version 6.0, with the introduction of "offline" version control.  Now, if you cannot connect to your version control system, EA still allows you to work normally (with some limitations) until you are able to reconnect.

BTW:  If you require support for EA, please send a support request to [email protected].  We will usually reply to such emails on the same day.