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

Microsoft.Azure.WebJobs built against net46 but NuGet still packaged as net45 #2064

Open
ggirard07 opened this issue Dec 19, 2018 · 0 comments

Comments

@ggirard07
Copy link

The version 2.3.0 of the Microsoft.Azure.WebJobs package targets .Net Framework 4.6 (seems to have changed for v2.1.0 release according to #1651). But the NuGet package is still declared with moniker net45.

This result in users updating their packages without any warning from NuGet, but then unable to run their solution.

Repro steps

  1. Create a new console project targeting .Net Framework 4.5.2.
  2. Add NuGet package Microsoft.Azure.WebJobs v2.0.0.
  3. Add some sample code for bare function and ensure everything is working fine.
  4. Update NuGet package Microsoft.Azure.WebJobs to v2.3.0.

Expected behavior

User should be not be able to update to an unsupported package without any error.

Actual behavior

NuGet package is updated without any error. Then solution no longer build.

Known workarounds

User can update its project target framework... but the problem here is that he has to go through the hassle of updating its NuGet first to discover the new version is not compatible.

Related information

Not sure whether this issue is relevant as v3.x is out now.
But as v2.x seems to still being maintained (v2.3.0 released after v3.0.1), I decided to report it anyway...

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

1 participant