Deploying framework-dependent .NET apps will fail if service doesn't have right version

[timheuer]

When publishing to app service or functions, a user may be using an framework-dependent deployment option (FDD) (the default). Upon publishing (especially with newer versions, go-live RCs, etc.) there is a possibility that the resulting service doesn't have FDD support yet. While self-contained deployment (SCD) is an option it isn't the default in our flows.

Publishing from the extension should do a pre-check with all known information to see if the resulting deployment will succeed in a runtime start (sans user-delivered errors).

[alexweininger]

I new to FDD and SCD but read about them on https://learn.microsoft.com/en-us/dotnet/core/deploying/. Let me know if there are any other resources.

Publishing from the extension should do a pre-check with all known information to see if the resulting deployment will succeed in a runtime start (sans user-delivered errors).

Is there more information available so we can implement this pre-check? How can we know if a service supports FDD or SCD?

Love to know more about this because increasing the success rate of deployments is top priority.

[timheuer]

@alexweininger -- I don't think a service needs to know it supports SCD because the nature of SCD is it shouldn't care mostly. But FDD requires that it will need to support whatever framework will need to be deployed. The source can look at the source target framework version and the source (app service) should have ability to check to see if the target is available on that instance (probably need to work with App Service team to see what info is available to interrogate)