Issues related to Service Fabric and .Net Framework> 4.5.2

We are currently using the service application (version of execution: 5.1.163.9590). I understand that there are newer versions there. But my questions are general.

The visual studio template for creating a new service application (for the above runtime) uses .NET Fraemwork version 4.5.2 by default. But we would like to use the .NET Framework 4.6.x. (I know that some versions of the C # compiler are backward compatible, but I do not want to rely on any of this except this version of the .net framework). I also know that there are ways to batch upgrade the .net infrastructure to the correct version. But there was a fear that if you scale the cluster, the necessary .net infrastructure would not be part of the new nodes.

We would like to target a specific .net infrastructure (say 4.6.2 or 4.7, etc.) and update our code to compile this version of the .net framework.

My questions:

  • How should we deploy the source cluster so that the .net frame version (say, 4.6.2) is deployed on all nodes?
  • When we scale a cluster with additional nodes, what steps should we take to ensure that all nodes are deployed with the selected version in the previous step?
  • Assuming that the cluster has been working for some time, how can we upgrade to the next version of the .net framework (say 4.7) without any problems without updating or scaling (assuming we compile our code in .net framework 4.7 and redeploy )?

( ), , . , .

.

+4
1

: , .net(, 4.6.2) ?

A: , PowerShell (DSC). DSC script, , .Net http://code.commongroove.com/2016/08/09/powershell-dsc-script-resource-dot-net-4-6-2/

Q: , , ?

A: , DSC script node node DSC, , node.

: , , .net framework ( 4.7) - ( , .net framework 4.7 )?

A: , . , . . , , .

,

0

Source: https://habr.com/ru/post/1674517/


All Articles