@dnenov Could you add more details about stability.

I would also like to hear inputs from @BogdanZavu as well.

If we must downgrade, we need to make couple more changes,

• We install 10.0.x in with setup-dotnet step in GitHub actions, we will need to specify version in there as well.

  Dynamo/.github/workflows/build_dynamo_all.yml

  Line 24 in d7fda6d

  10.0.x

• We will also need to update rollForward policy in global.json

@dnenov Could you add more details about stability.

I would also like to hear inputs from @BogdanZavu as well.

If we must downgrade, we need to make couple more changes,

• We install 10.0.x in with setup-dotnet step in GitHub actions, we will need to specify version in there as well.

  Dynamo/.github/workflows/build_dynamo_all.yml

  Line 24 in d7fda6d

  10.0.x

• We will also need to update rollForward policy in global.json

It is part of this thread - https://autodesk.slack.com/archives/C0531NMR189/p1759417135610879?thread_ts=1753895883.337709&cid=C0531NMR189. @Mikhinja is reporting severe speed issues potentially due to parts of Dynamo not being correctly ran under Preview 5 SDK environment.

@dnenov Could you add more details about stability.

I would also like to hear inputs from @BogdanZavu as well.

If we must downgrade, we need to make couple more changes,

• We install 10.0.x in with setup-dotnet step in GitHub actions, we will need to specify version in there as well.

  Dynamo/.github/workflows/build_dynamo_all.yml

  Line 24 in d7fda6d

  10.0.x

• We will also need to update rollForward policy in global.json

So, basically we need to lock against Preview 5 without roll forward? OK, let me do these changes just in case.

This PR is a provision, in case we are forced to use it.

We will need to install Preview 5 SDK on the machine: Install the [10.0.100-preview.5.25277.114] .NET SDK or update [C:\Jenkins\workspace\Dynamo\DynamoSelfServe\pullRequestValidation\Dynamo\global.json] to match an installed SDK.

@dnenov @avidit Would you educate me about Preview 5 without roll forward, why without if machines are going to have RC5 or higher?

@dnenov @avidit Would you educate me about Preview 5 without roll forward, why without if machines are going to have RC5 or higher?

With rollForward: "latestFeature" dotnet will use latest feature band of the specified major and minor version, if the exact version specified is not available (e.g., from 8.0.100 to 8.0.300 if 8.0.300 is installed). This gives flexibility for devs, ci machines to have different feature version.
With rollForward: "disable", an exact match is required.

Getting the exact version is easier in GitHub actions with setup-dotnet action. For internal agents, we need some changes.

My take on this is to wait a little bit before doing a downgrade.
We already did a good amount of testing and released components built with latest .net 10 rc 1 - I think we are where we should be and others will catch up.
Also there is no ITF pressure anymore.

potentially due to parts of Dynamo not being correctly ran under Preview 5 SDK environment.

We need to confirm/further look into this. Imo as long as it still works even if it's slower we should be good for now.

This one did not build, so re-triggered as https://master-5.jenkins.autodesk.com/job/Dynamo/job/DynamoSelfServe/job/pullRequestValidation/18513/

@BogdanZavu This is a backup plan in case the performance issue was real between our build and D4R. We need to be prepared that the ITF boston machine does not come with latest .NET10 SDKs

This one did not build, so re-triggered as master-5.jenkins.autodesk.com/job/Dynamo/job/DynamoSelfServe/job/pullRequestValidation/18513

@BogdanZavu This is a backup plan in case the performance issue was real between our build and D4R. We need to be prepared that the ITF boston machine does not come with latest .NET10 SDKs

This is expected to fail since we don't have the exact version of net10 SDK installed in the build image.

My take on this is to wait a little bit before doing a downgrade. We already did a good amount of testing and released components built with latest .net 10 rc 1 - I think we are where we should be and others will catch up. Also there is no ITF pressure anymore.

potentially due to parts of Dynamo not being correctly ran under Preview 5 SDK environment.

We need to confirm/further look into this. Imo as long as it still works even if it's slower we should be good for now.

So @avidit @QilongTang @dnenov I'm having some second thoughts on this.
I was under the impression that we have much more time until the next ITF - we said pass to the one in Krakow but the one in Boston is only one week away.
I talked with Vlad and saw that current D4R is not usable.
This is latest build config for .net sdk 10 merged in master :
Revit - preview 5
Core - preview 7
D4R - preview 5

Probably our best bet to be ready for ITF Boston would be to stick to preview 5 across the board.

My take on this is to wait a little bit before doing a downgrade. We already did a good amount of testing and released components built with latest .net 10 rc 1 - I think we are where we should be and others will catch up. Also there is no ITF pressure anymore.

potentially due to parts of Dynamo not being correctly ran under Preview 5 SDK environment.

We need to confirm/further look into this. Imo as long as it still works even if it's slower we should be good for now.

So @avidit @QilongTang @dnenov I'm having some second thoughts on this. I was under the impression that we have much more time until the next ITF - we said pass to the one in Krakow but the one in Boston is only one week away. I talked with Vlad and saw that current D4R is not usable. This is latest build config for .net sdk 10 merged in master : Revit - preview 5 Core - preview 7 D4R - preview 5

Probably our best bet to be ready for ITF Boston would be to stick to preview 5 across the board.

My brief chat with @mjkkirschner suggests that some components (specifically the Flag CLI), which were built with Preview 7 in mind, are actually being executed under Preview 5 within D4R and Revit. This mismatch appears to be generating the large volume of empty logs - likely due to repeated runtime failures - which in turn causes the significant performance degradation.

I’m not entirely sure how to validate or mitigate this while remaining on Preview 7, but I agree with @BogdanZavu that the most pragmatic approach for now is to revert to Preview 5 and align with the SDK version agreed for this release.

@QilongTang @BogdanZavu @avidit I tried removing RC1 and only leaving the Preview 5 runtime on the system, and I cannot start Dynamo.

@dnenov @avidit PR check failing, restarted at https://master-5.jenkins.autodesk.com/job/Dynamo/job/DynamoSelfServe/job/pullRequestValidation/18535/

Merging this to align with Revit preview build