|
|
@@ -16,6 +16,9 @@
|
|
|
1. Bump engine version ([example commit](https://github.com/Eideren/xenko/commit/6fb6580b3c60b98d16e2f01d0cce449d568886da))
|
|
|
1. If there is a .NET SDK version upgrade:
|
|
|
- Aside from usual changes ([example PR](https://github.com/stride3d/stride/pull/2888)), one important thing is to update the prerequisites installer ([example commit](https://github.com/stride3d/stride/commit/65e93bef9dd301007e65e0c2c684dd6cbc3906a8)) and `global.json` ([example commit](https://github.com/stride3d/stride/commit/4333cd2e28c3ecbbc8462635b80e038cd6cb3ec7))
|
|
|
+ - Also, add the new .NET Framework in VSPackage StrideCommandsProxy.cs ([example commit](https://github.com/stride3d/stride/commit/dc8ba75d3b127ee39c9650c9c5cbf07a1d730b0c#diff-ed3d93093709147db6205c48c4015b60d98f44ad8d555e94d825e44f5999efb3R181))
|
|
|
+1. If there is a new Visual Studio released:
|
|
|
+ - Assuming there is no major breaking changes, simply updating the vsixmanifest so that it can do VS2022, VS2026 and any new versions is enough.
|
|
|
1. Optional: Update Stride development NuGet packages version in all samples in `https://github.com/stride3d/stride/tree/master/samples`
|
|
|
- This is especially useful if there are asset upgrader taking a lot of time; otherwise, the default project upgrader will still be run on sample creation
|
|
|
- Open `samples\Stride.Samples.sln` with GameStudio. Let upgrade run, and do a "save all" from GameStudio; if there is any error opening the project, fix them and reset files before reopening (do not save incomplete `csproj` changes without asset upgrades)
|
xen2