Subversion Repositories DevTools

The folders alongside this readme.txt file are the EA Interops that we have used thus far.

Below is a quideline on interoperating EA with VS2003

Currently we are using EA 7.5
BUT,...The EA_DocGenP.dll is built against dotnet v1.1 which needs the v7.0 interop in order to build.
Interops 7.1 and 7.5 use dotnet v2

Heres how I use these.

1) Copy the v7.0, v7.1, and v7.5 folders into your "c:\Program Files\Sparx Systems\EA" folder
2) Confirm that the interop.ea.dll in your "c:\Program Files\Sparx Systems\EA" folder is the same as one of the ones in the v7.x sub-folders.
   If it is not then you may have an older or newer version of EA than any of the v7.x sub-folders represent. You may have to create a new v7.x sub-folder
   to keep a copy of your interop, and add it to source control too so others benefit.
   However, at this time, you should be using EA 7.5
   Assuming you are using EA 7.5, it is fine to have your 7.5 interop in the "c:\Program Files\Sparx Systems\EA" folder except
   for when building and debugging the EA_DocGenP.dll. Here we need to v7.0 interop. So go into the v7.0 folder and run the activate script.
3) Open Visual Studio .NET 2003 and open the EA_DocGen workspace
4) Build EA_DocGenP.dll
5) start to debug - EA should start up. Now you can set breakpoints etc.
6) When I am done, I usually reset the interop by going into the v7.5 folder and running the activate script.

One day we will rebuild EA_DocGenP.dll using a newer .net framework version, but until then, you have to be aware of the interop compatibility issues I have
resolved using the mechanism above.

NOTE: Could have kept all of these interops in release manager in the Sparx_Systems_EA_Object_Lib package, BUT, Sparx Systems have not advanced the version
number with successive rebuilds and releases of this interop (they are all 2.10.238.1) which is what the version in release manager advertises (and it is the
dotnet v1 version and is used in jats builds of EA_DocGen). We may have to create new interop packages in release manager each time EA is upgraded rather than
creating new versions of the Sparx_Systems_EA_Object_Lib package.