Ever since I have upgraded to Windows 7, I often times get the error "Please select at least one DLL implementing the IEdmAddIn5 Interface" whenever I try to load an EPDM addin.
It is a good addin, because my work around is to:
[If the addin has never been loaded before it seems to work okay too.]
Now all is good, but what a pain! Anyone else seen this? Anyone have a real fix for it?
I just came across this error and to fix it I renamed the class that implements the IEdmAddin5 class. It worked this time around.
Works here too.
Very clever! Do you simply rename the class before every compile?
Found something interesting today. I had an addin that would not work. Tried the addin in a different vault and it worked fine!
Not sure what this all means, but thought I'd pass it along.
For anyone interested. I have come across this message again recently after upgrading to EPDM 2013 SP2.0.
The resolution to the problem was to select .Net 4.0 as the target framework, and not .Net 3.5 as in the past. For some reason this fixed it. So .Net 3.5 is probably out the door because of Windows 8
I found the exact problem causing this error on my setup. The GetAddInInfo function CANNOT throw an exception. Any exception has to be caught before giving the control back to ConisioAdmin.exe.
I had a int.Parse causing the problem and when I used int.TryParse, it passed. I then enclosed the int.Parse inside a try-catch block and it worked.
100 per cent. Any exception thrown will yield that generic error message unless you handle that exception yourself.
I have seen it often and had the same work around solution. However, lately I have also come across another issue where the addin will not load in Debug mode, but will load and run correctly as a complete add-in. After I’ve loaded it as a complete add-in, I can unload it and then load it in the debug mode. I never correlated to Windows 7 however, because I’ve been on Windows 7 for quite some time. The thing I correlated it with was that I had to upgrade to 2010 SP3 and then downgraded to SP1.0. This started happening after this so I thought it was only an issue I was having because of the downgrade. Sorry I don’t have a real fix but I hope this helps.