Hi Massimo,
Thanks for sharing the workaround that you found.
Regards,
Balaji
One more question:
- the resource DLLs can be built targeting both x86 and x64 platforms or do I need to build two distinct set?
If this is the case, in the packagecontents.xml we'd need to specify two different CUIx folder, like:
[...]
<Components Description="2015 x86 plugin">
<RuntimeRequirements OS="Win32" Platform="AutoCAD*" SeriesMin="R20.0" SeriesMax="R20.0" />
<ComponentEntry AppName="comsMyPlugin" Version="1.0.0" ModuleName="./Contents/2015/comsMyPlugin.dll" />
<ComponentEntry AppName="comsMyPlugin" Version="1.0.0" ModuleName="./Contents/WIN32/comsMyPlugin.cuix" />
</Components>
<Components Description="2015 x64 plugin">
<RuntimeRequirements OS="Win64" Platform="AutoCAD*" SeriesMin="R20.0" SeriesMax="R20.0" />
<ComponentEntry AppName="comsMyPlugin" Version="1.0.0" ModuleName="./Contents/2015/comsMyPlugin.dll" />
<ComponentEntry AppName="comsMyPlugin" Version="1.0.0" ModuleName="./Contents/WIN64/comsMyPlugin.cuix" />
</Components>
[...]
Correct?
Hi Massimo,
Bitness of a resource dll did not seem to matter in the tests that I did.
Both the resource dll build with 32 and 64 bit configurations loaded interchangeably.
But I am not an expert in resource dll so cannot confirm that for sure. There are a few MSDN posts that say bitness does not matter for a resource dll.
If you would want to deploy separate versions of the 32 bit and 64 bit resource dll, then your packagecontent.xml looks ok.
Regards,
Balaji
Thank you Balaji.
What about the behaviour you excaled to engineering? I'm talking about the icon/resource switching according to the current theme.
Any news? Any timeline?
I updated our plugins to work with 2015, but I choose to distribute bitmaps only for light theme. Under dark theme the icons are readable, even if it's not the result you may expect. I placed a note in the 'known problems' section of the help files.
Regards,
Massimo
Hi Massimo,
The case notes from the request that I logged with our engineering team suggests that this has been fixed.
Sorry, I am not sure when/how the fix will be made available.
Regards,
Balaji
Hi Balaji,
by chance, do you know if that fis is included in the recent AutoCAD 2015 SP1? The readme doesn't mention it however.
Sorry, this fix wasn't included in SP1.
I just tested it with AutoCAD 2015 SP1 and the behavior was the same.
Regards,
Balaji