You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To support mixed mode assemblies, the ExcelDnaDoc analyzer is compiled with different target framworks. This needs to be reflected in the NuGet package too. See #15 .
The text was updated successfully, but these errors were encountered:
Do you think it is worth creating and maintaining separate ExcelDnaDoc.exe's for each platform target instead of changing the way we analyze assemblies to use something better than System.Reflection, that supports reading assemblies built for any platform, and would allow us to continue to have a single .exe?
I haven't tested it, but I'd expect Microsoft's CCI should be able to give us all the assembly metadata we need, regardless of platform. If not, maybe Mono.Cecil would...
Seems like it’s worth a look - if you put a branch together I’d be happy to test it with my mixed- mode assemblies.
I don’t have the time to look into this though, so much code, so little time.
On 5 Jun 2018, at 03:28, C. Augusto Proiete ***@***.***> wrote:
@govert / @Cronan:
Do you think it is worth creating and maintaining separate ExcelDnaDoc.exe's for each platform target instead of changing the way we analyze assemblies to use something better than System.Reflection, that supports reading assemblies built for any platform, and would allow us to continue to have a single .exe?
I haven't tested it, but I'd expect Microsoft's CCI should be able to give us all the assembly metadata we need, regardless of platform. If not, maybe Mono.Cecil would...
Thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
To support mixed mode assemblies, the ExcelDnaDoc analyzer is compiled with different target framworks. This needs to be reflected in the NuGet package too. See #15 .
The text was updated successfully, but these errors were encountered: