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
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
Create a new console project targeting .Net Framework 4.5.2.
Add NuGet package Microsoft.Azure.WebJobsv2.0.0.
Add some sample code for bare function and ensure everything is working fine.
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...
The text was updated successfully, but these errors were encountered:
The version
2.3.0
of theMicrosoft.Azure.WebJobs
package targets .Net Framework 4.6 (seems to have changed forv2.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
Microsoft.Azure.WebJobs
v2.0.0
.Microsoft.Azure.WebJobs
tov2.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 afterv3.0.1
), I decided to report it anyway...The text was updated successfully, but these errors were encountered: