Can't define Generic .Net Interface

[frik_stuart]

I have a .Net interface defined as follows:
public interface IRepository<T>

I can not find any way to define this Generic interface in EA since the "Details" tab where you define "Templates" is not available for interfaces like it is for classes. I have also tried reverse engineering the interface but it also does not seem to define the Type parameters.

Does anyone know how to do this in EA? Otherwise my round-trip engineering would be pretty useless if it can't handle this standard .Net2.0 functionality.

[Eve]

Unfortunately, EA doesn't handle generic interfaces.

[frik_stuart]

Ok thanks Simon. Do you know if this is on the Roadmap in the near future?

[Eve]

It's one of the changes I'm desperate to see go in, but I'm note sure when that will happen.

[«Midnight»]

Please push for inclusion in EA 7.5 production. Not having this would essentially destroy compatibility with .Net 3.x and C# 3.0, not to mention VB 2008.

(IMHO) Failure to address this before production would seriously degrade the quality of support for these products, making the advertised feature set of EA 7.5 somewhat shaky.

[Frank Horn]

It's not only .Net 3.x, but .Net 2.0. EA's inbuilt C# code generation is next to useless as long as there is no full support for generics.

Ok, code generation can be improved by working on the templates, but there's nothing like this for reverse engineering , and some .Net 2.0 constructs are simply being ignored by EA: not only generic interfaces, but also inheritance of generic classes.

[«Midnight»]

Frank says it well.

These holes were hard to take before, but we could - and did - hold out hope that they would disappear in the next update, when EA supported current .Net and VS versions. This has often been mentioned, and we've been told to wait until the whole package could be released at once.

That time has come, and now it is time to deliver on these earlier issues.