2 of 2 people found this helpful
I opened an SR about this issue. It was bumped up to a DR, DR/ER #01213196. The current status is:
18 Oct 2016
Reviewed during the latest planning cycle and not selected for inclusion in the current release. The next review cycle is planned for 1H2017.
There is a way to get around it.
1. Uninstall .2.1.
2. Install .1.0 (the very first VX release; maybe it's just .1)
3. Install .2.1
4. Using the Release Switcher, make sure .2.1 is the registered version.
Some of the missing COM references will reappear. Some won't. I forget exactly which ones. For the ones that are now listed in the normal add references list, use them.
In your .net project, remove old references and add new, using the COM object explorer where you have to manually add the reference by selecting a .dll or .tlb file. Go to the \project\obj\x86\Debug folder in your project and select the Interop.xxxx.dll file, like Interop.Viewdraw.dll, etc.
Yes I realize this is in effect using the .dll files from the prior release. So far that does not seem to be an issue, and I have not had any odd failures or lost functionality in any of the tools. I have working scripts for DxDesigner, Xpedition, Fablink, Drawing Editor, PartEditor, CellEditor, and PadstackEditor. I made an automation template with all of this working for .1.2, which you can get here. At a minimum you can get all the .dll files you need from it, if the ones in your current projects don't work per the above instructions.
Best of luck getting it to work. I really hope Mentor addresses this sometime soon. If they change something in the COM and the old .dlls don't work, it will cause a major disruption. Well, what it will cause is we won't upgrade our software until they fix it. The out is that they officially don't support compiled scripts, so anything using the COM is tough luck if it doesn't work.
Many thanks for your detailed answer.