.net core 2.2 和 3.1 应用槽可以共存于同一个应用服务中吗? [英] Can .net core 2.2 and 3.1 application slots coexist in the same app service?
问题描述
我们目前在 azure 应用服务中有两个插槽:暂存和生产.我们刚刚将 .net core 2.2 迁移到 3.1，并在单独的开发应用服务中对其进行了测试.我们即将发布 3.1 应用到 staging.
We currently have two slots in azure app service: staging and production. We just migrated .net core 2.2 to 3.1 and tested it in a separate dev app service. We are about to publish the 3.1 app to staging.
有谁知道让一个插槽运行 2.2 和另一个插槽运行 3.1 是否有任何问题?
Does anyone know if there are any issues with having one slot running 2.2 and another one 3.1?
推荐答案
Azure web app是一个PaaS服务，我们不能修改里面的内容.正因为如此，它默认集成了很多环境，或者默认支持我们所有常用的SDK版本.
Azure web app is a PaaS service, and we cannot modify the content in it. Because of this, it integrates many environments by default, or supports all our common SDK versions by default.
测试步骤:
创建一个应用服务(jasonp2core22)，版本为.net core 2.1.
Create an app service (jasonp2core22) which version is .net core 2.1.
运行 dotnet --info.
创建一个应用服务(jasonp2core31)，版本为.net core 3.1.
Create an app service (jasonp2core31) which version is .net core 3.1.
运行 dotnet --info
Slot本质上是一个app服务，不用担心，一切都可以正常运行.
Slot is essentially an app service, so your worries are non-existent, and it can all run normally.
同时运行 dotnet --info.
这篇关于.net core 2.2 和 3.1 应用槽可以共存于同一个应用服务中吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
