V12 and V11 compatibility

[ssands]

Apologies in advance if this has been addressed elsewhere.

Are there any compatibility issues if I have some users on a shared model (MS SLQ Server & SVN) running V11 and one (me!) using V12?

Thanks!

[qwerty]

No known issues so far. The basis is very stable. You just will get problems in training since the UI has changed quite a bit.

q.

[ssands]

Thanks, q!

[Geert Bellekens]

The only thing I got in trouble with was a change in the API when retrieving Elements or Packages.
The operation used to throw an exception if something was not found, and  in v12 it suddenly returns an empty object.
I had to update the EA Navigator code to take this into account.

Geert

[ssands]

Thanks, Geert! I think I'll take the plunge. The rest of my team can't upgrade until our support staff rolls it out to them. Fortunately, I have the permissions to do that on my own.

[heba]

The only thing I got in trouble with was a change in the API when retrieving Elements or Packages.
The operation used to throw an exception if something was not found, and  in v12 it suddenly returns an empty object.

Seems that I've run into exactly this problem.  EA12 reliably crashes with with my add-ins.  I'll start to investigate, thanks for pointing this out!

-Heiko

[Eve]

I would love to see an example of code that crashes in EA 12 that didn't in EA 11. In the last thread I did describe ways that issues could happen, but to the best of my knowledge they were theoretical, no such change should have been included in v12 precisely because we shouldn't be causing this kind of problem.

[Doug Blake]

There is a small problem with TFS integration of Version Control. See following quote from the answer to my bug report.

There have been some changes to TFS integration in EA 12. When opening your existing project (which has TFS integration) with EA 12 you will need to open the Version Control settings and enter a "Display Name" (see the "TFS Settings" help topic). This should be entered as shown in the User column of the Visual Studio Source Control Explorer when you checkout a file. This change was implemented to avoid potential data loss when integrating with TFS.

[Geert Bellekens]

I would love to see an example of code that crashes in EA 12 that didn't in EA 11. In the last thread I did describe ways that issues could happen, but to the best of my knowledge they were theoretical, no such change should have been included in v12 precisely because we shouldn't be causing this kind of problem.

Simon they where very much NOT theoretical. I had to fix the code for my add-ins at my client as well.

Here's the cullprit:

Code: [Select]

       /// <summary>
        /// returns the element witht the given ID
        /// </summary>
        /// <param name="elementID">the id of the element</param>
        /// <returns>the element with the given id</returns>
        public EAElement findElementByID(int elementID)
        {
            object elementFound = null;
            EAElement returnedElement;
            //first look in the cache
            if (!this.elementCache.TryGetValue(elementID, out returnedElement))
            {
                //if not found in the cache then look in the repository
                try
                {
                    elementFound = wrappedModel.GetElementByID(elementID);
                }
                catch (COMException)
                {
                    //nothing could be found, return null
                    return null;
                }
                returnedElement = EAWrapperFactory.createEAWrapper(this, elementFound) as EAElement;
            }
            return returnedElement;
        }
In my code I create wrappers for the EA.Element objects.
This code behaves differently in v11 and in v12.
In v11 I get an exception, which I catch and return null.
In v12 I don't get an exception and I go on to create my wrapper using EAWrapperFactory.createEAWrapper using the null object.
Later on when I try to use the wrapped EA.Element object I get NullpointerExceptions, which make EA go down hard.

Geert

PS. Yes I agree that this piece of code could have been written more defensively.  

[Eve]

Simon they where very much NOT theoretical.

Maybe theoretical wasn't the right word. I knew that if anyone here changed the error behavior for a function from throwing an exception to returning null it would cause crashes in some add-ins. But that's as far as my knowledge went.

Speaking as an individual rather than a Sparx Systems representative. I didn't think that such a change had been made to version 12. Even seeing your code, I can't find anywhere that could have changed that behavior. But I believe you that you are seeing a change in behavior. I am personally embarrassed about it, and when I find out where it is and the person responsible they will feel my displeasure.

Anyway, thanks for the sample code. Is wrappedModel.GetElementByID just calling Repository.GetElementByID?

[qwerty]

Cheers! We stand with you, Simon!

q.

[Geert Bellekens]

Is wrappedModel.GetElementByID just calling Repository.GetElementByID?

Yes, I have an attribute called wrappedModel that contains an object of type EA.Repository

Thanks for your support Simon  

Geert