Azure Func running .net 8 break when the func project Microsoft.Extensions.Logging.Abstractions and/or Microsoft.Extensions.Options package is upgraded to 9.x

[tbithell]

Not sure if this belongs here or not, but the issue is very strange and this is where I was brought when I looked for Microsoft.Extensions.Logging.Abstractions.

The reason I say it is strange is because the actual error message that we received pointed us to an internal package causing the problem. We downgraded it and it still claimed it was the problem even though that same package version was working in a different environment.

Earlier today I downgraded both of the Extensions packages back to 8.0.2 and the func starts no problem.

I'm also seeing the option to update my Microsoft.AspNetCore.Mvc.Testing package to 9.x, but it helpfully tells me it won't work since it's .net 8 and not .net 9.

Should we just be avoiding 9.x packages or is there an issue with backwards compatibility?

I apologize I can't provide much more details than the above, and for sure can't provide code or csproj files etc. I was just hoping to get some direction.

Thanks!

[tbithell]

I'm going to close this and assume the internal package didn't like the newer version of this package

[julealgon]

Should we just be avoiding 9.x packages or is there an issue with backwards compatibility?

@tbithell the vast majority (if not all) of Microsoft.Extensions.* packages are not tied to the target framework version, meaning you should be able to use later versions of them in previous target frameworks (we use a ton of v8 and v9 of those packages in our NET472 solution, for example).

Maybe you could share the error you were seeing?