Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling second-tier references #15

Closed
Leogiciel opened this issue Jan 3, 2017 · 3 comments
Closed

Handling second-tier references #15

Leogiciel opened this issue Jan 3, 2017 · 3 comments

Comments

@Leogiciel
Copy link
Contributor

I use this nuget package which delivers four dlls but references only the top two of them in the csproj. (see my post on SO explaining this behaviour).

VS and MSbuild both do right at compilation, detecting references from other two libraries and resolving them because they are on the same folder (according to this post ) and the four libraries are in the bin folder.

Wax doesn't detect them, and I understand that's because it's based on csproj file, but if MSBuild can do it maybe we can too ?

Regards

@Leogiciel
Copy link
Contributor Author

I'm working on it, and I'll send you a pull request.

@tom-englert
Copy link
Owner

Using Assembly.LoadFile is dangerous, the file will be locked by the VS process forever. I have refactored it using Mono.Cecil (d36a782)

@Leogiciel
Copy link
Contributor Author

Nice ! Thank you for the tip, I didn't know about Cecil, it looks amazing !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants