search

3F / DllExport

.NET DllExport with .NET Core support (aka 3F/DllExport aka DllExport.bat)
MIT License
940 stars 131 forks source link

Failed to resolve assembly... #127

Closed esso23 closed 4 years ago

esso23 commented 4 years ago

Hi,

I have a problem when using latest version with .NET Standard 2.1 (same problem occurs when I use .NET Core 3.1). The error happens when building:

'Failed to resolve assembly: 'dllexport_issue.dep, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' dllexport_issue D:\Sync\Projects\dllexport_issue\packages\DllExport.1.7.0-beta\tools\net.r_eg.DllExport.targets 74'

Basically I have ClassLibrary1 referencing ClassLibrary2 and in some cases DllExport cannot resolve ClassLibrary2 assembly when creating exports for ClassLibrary1. I tried to isolate the problem and the build task fails when there is an Attribute that has an Enum property which is initialized in Attribute constructor (not sure that's the ACTUAL problem, but when I was adding things one by one, that's where it broke). See attached repro.

Here is complete solution with minimum repro. Just compile 'dllexport_issue' project and error occurs: 'Failed to resolve assembly: 'dllexport_issue.dep, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' dllexport_issue D:\Sync\Projects\dllexport_issue\packages\DllExport.1.7.0-beta\tools\net.r_eg.DllExport.targets 74 ' dllexport_issue.zip

Edit: Maybe it's worth to note I am porting code to .NET Standard 2.1 from .NET Framework 4.7.2 where I was also using DllExport (1.6.5) and everything worked fine.

3F commented 4 years ago

Confirm. Thanks for the report and attached sample!

.NET Framework 4.7.2 where I was also using DllExport (1.6.5) and everything worked fine.

Yes, please use this before fixing problem. I'll try to review issue for 1.7 beta2.

3F commented 4 years ago

Please test applied solution through latest beta releases.