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.

Sign up for GitHub

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

Jump to bottom

[Cauldron.Interception.Fody] Wrong version of Cauldron.Interception.Fody referenced #74

Open
Dhairya-Sangoi opened this issue Oct 23, 2018 · 3 comments
Open

[Cauldron.Interception.Fody] Wrong version of Cauldron.Interception.Fody referenced #74

Dhairya-Sangoi opened this issue Oct 23, 2018 · 3 comments

Comments

@Dhairya-Sangoi
Copy link

Hey,

I have a doubt regarding how Fody chooses which version of the weaver to use.

Let's say, there is a solution having multiple projects, each using different version of Cauldron (Cauldron.BasicInterceptors). Each version of Cauldron brings a corresponding compatible version of Cauldron.Interception.Fody (which is the actual addin of Fody). Now, will Fody choose right version of Cauldron.Interception.Fody, or it would always choose the latest version available in the packages folder?

If we try to build such a solution, then the build fails for the project consuming lower version of Cauldron. I guess this is the expected behavior.

The link AddinSearchPaths mentions that Fody would always take the latest version of the addin.

Could you please help by asserting this assumption.
@reflection-emit
Copy link
Collaborator

Yea I have the problem too with different Fody versions. If Fody finds a newer Addin version in the package folder Fody will use it.
Following issue is related to this problem:
Fody/Fody#524

@Dhairya-Sangoi
Copy link
Author

Thanks for the quick reply. I am using PackageReference in my project. But still it doesn't resolve to the correct Addin version. I think, this is the limitation of fody, coz it doesn't know which version of the Addin we are using (maybe because it doesn't parse the csproj/packages.config file to lookup for the version information)

@reflection-emit
Copy link
Collaborator

Just found this... Fody/Fody#557
I will look into this... Maybe it fixes these problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Dhairya-Sangoi @reflection-emit