Book a Demo

Author Topic: Support for .Net 1.1?  (Read 4879 times)

Stuart Trotter

  • EA Novice
  • *
  • Posts: 14
  • Karma: +0/-0
    • View Profile
Support for .Net 1.1?
« on: October 15, 2009, 09:58:57 pm »
Hi All,

I've been writing a few add-ins recently which are compiled in .Net 3.5 and they work perfectly. The problem I have is that a client really wants a few add-ins in .Net 1.1 for EA 7.5. I didn't think this would be a problem until I created a new project in VS2003 and tried to add the Interop.EA.dll as a reference. Visual Studio refused to add it complaining that it's not a valid COM dll. I also tried compiling the standard .Net 1 sample plugin from Sparx and got a compilation error saying the following:

Metadata file 'c:\Program Files\Sparx Systems\EA\Interop.EA.dll' could not be opened -- 'Version 2.0 is not a compatible version.'

Has support for .Net 1.1 been deprecated in EA 7.5? Or am I doing something stupid?

Thanks,
Stuart

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Support for .Net 1.1?
« Reply #1 on: October 15, 2009, 10:43:55 pm »
Can't you use the (pre .net) com object?
(I think you then need to reference the EA.tbl)

Geert

Stuart Trotter

  • EA Novice
  • *
  • Posts: 14
  • Karma: +0/-0
    • View Profile
Re: Support for .Net 1.1?
« Reply #2 on: October 15, 2009, 11:34:38 pm »
Possibly, but I thought if I used that I can only write automation applications rather than an actual addin for EA... I could well be wrong though.

smendonc

  • EA User
  • **
  • Posts: 148
  • Karma: +5/-0
  • I love YaBB 1 Gold!
    • View Profile
Re: Support for .Net 1.1?
« Reply #3 on: October 16, 2009, 11:17:22 am »
You should be able to create a version of Interop.EA.dll for VS 2003 and .net 1.1.  Two common ways to do this would be to reference EA.tlb in VS 2003 - this will automatically create the rcw layer or run tlbimp.exe from a command line passing it EA.tlb as a parameter.  This will create a version of Interop.EA.dll which you can use instead of the one provided by Sparx.  You'll need to use the tlbimp.exe version that shipped with VS 2003.  Below is a link to the msdn site that provides the options for tlbimp  http://msdn.microsoft.com/en-us/library/tt0cf3sx(VS.71).aspx .

Stan.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Support for .Net 1.1?
« Reply #4 on: October 16, 2009, 06:31:10 pm »
Quote
Possibly, but I thought if I used that I can only write automation applications rather than an actual addin for EA... I could well be wrong though.

I don't believe that matters at all.
All you need to do to make your application an EA addin is create a COM compatible dll (and register it), implement the EA methods and let EA know it has to load your dll as an addin via the registry.

Geert

Stuart Trotter

  • EA Novice
  • *
  • Posts: 14
  • Karma: +0/-0
    • View Profile
Re: Support for .Net 1.1?
« Reply #5 on: October 16, 2009, 06:58:23 pm »
Thanks guys, I'll give it try. By implication though I'm guessing that means the standard interop.ea.dll provided by Sparx is for .Net 2 and up.

Thanks again,
Stuart