Incorrect Host Version

[brettsam]

Version

4.0.7018

Description

Created a new .net8 app in VS and hit F5 -- the core tools reports that it's running 4.6xx, yet it seems pretty clear that it's actually 4.8xx:

Azure Functions Core Tools
Core Tools Version:       4.0.7018 Commit hash: N/A +ec5981453def131abe6005327168b918fac8d426 (64-bit)
Function Runtime Version: 4.634.3.22875

Yet it's running from here:

C:\Users\brettsam\AppData\Local\AzureFunctionsTools\Releases\4.107.0-inprocess\cli_x64\in-proc8\

Steps to reproduce

Launch .net 8 in-proc app in VS

[liliankasem]

@brettsam we now display the core inproc host version:

Function Runtime Version: 4.40.100.25262

Which is used for .NET 6 and .NET 8. But do we still want to display the 6 | 8 respectively i.e. 4.640.100 and 4.840.100?

@mattchenderson - let me know if you have thoughts on this too

[jviau]

@brettsam we now display the core inproc host version:

Function Runtime Version: 4.40.100.25262

@liliankasem, where does this message come from? If it is from a func host assembly, I am surprised it has that version at all and not a 4.[10|8|6]40.100.25262

[liliankasem]

@jviau Looks like from the ScriptHost

https://github.com/Azure/azure-functions-core-tools/blob/40a19e11f70f3c9aaefb3911a8581014ec748413/src/Cli/func/Common/Utilities.cs#L51C57-L51C67

https://github.com/Azure/azure-functions-host/blob/c62778b79e53786dce2852a39b9c1c73690be651/src/WebJobs.Script/Host/ScriptHost.cs#L78

I know in Azure it does show up as 4.630 and 4.840 so I wonder where that comes from?

[jviau]

Ah okay. This is a "problem" with the host only present when using this assembly from the nuget packages. We only inject the "MinorVersionPrefix" when building the site extension and linux artifacts - we don't inject it for the nuget package. NuGet will complain if you try and change your Version property between TFM's. We will need to:

1. Update Microsoft.Azure.WebJobs.Script to be multi-targeted
2. Update build logic to change assembly version for different TFM, but not package version.

[jviau]

To explain the original issue:

We introduced that 4.6xx or 4.8xx value based on a MinorVersionPrefix msbuild property. We only supplied that value when building for site extension and linux artifacts. It was never supplied when building as a nuget package. Our targets at the time would then default MinorVersionPrefix to 6 when not present, so both net6 and net8 in-proc got the same 4.6xx version. Our targets now no longer default that property, but we still don't supply it. So in-proc builds from nuget are now 4.xx, no minor prefix at all. We can introduce that minor version prefix, but today it comes from Microsoft.Azure.WebJobs.Script which is NOT multi-targeted, so net8 and net6 both use the same copy, no way to differentiate the version there. Which is why we will need to make it multi-targeted to differentiate between the two and resolve a different version.

OR core-tools can take the existing version and insert 6 or 8 based on the running TFM.