Hey, Geert,
Ok thanks. After a while I did get the EAAddinFramework project to compile, after removing most of the add-in related things from the projects.
I mentioned just using Interlop.EA, because your library seemed very big, with all kinds of dependencies, some related to UML diagrams, some TFS work ticket stuff, some related to Addin UI stuff. - No offense to your libraries though, from the looks of it you can a lot of things with it.
My initial plan was just some simple validations are refactoring/renaming that won't become an addin, but just a winform or console instead.
(for example, some validations:
- name all foreign keys $"FK_{child.column}_{parent.column}
- name all primary keys $"PK_{parent.column}
- this seems like a EA bug but: When I have a unsigned int with a relation that I change to a char, the char(n) becomes an unsigned char in my script - not valid sql)
Anyway - the whole wrapping framework you've made seems pretty useful. I've been busy trying to debug against these COM calls the whole day, and it's going terrible... If I could load the whole model in memory first or something, it'd make my life a lot easier.
I'm home now, tomorrow at work I'll continue trying.
Is the assumption correct:
I can just include the EAAddinFramework project, create a class that inherits from EAAddinBase, and then us that on a EA.Repository, and use it for parsing and renaming purposes?
Or - probably a better question, any tutorial or guide on how to use your libraries (as processing libs, not an actual add-in)
Thanks a lot for the help so far.