-
제목
Implications of .NET version changes in version 9.3 and version 10 -
설명
When administrators who have a working 9.0 9.1.x or 9.2.x install of Identity Manager update to version 9.3 or newer, scripts which used to work before the upgrade either fail to compile or return different results than were returned in earlier versions.
The 9.3 documentation has a mention of this in the Release Notes
[Excerpt:]
One Identity Manager is now based on .NET 8.-
- Scripts and all custom extensions must be compatible with .NET 8.
- NuGet packages are supported as dependencies in scripts.
Custom scripts for synchronization projects that use custom DLL files must be adapted and recompiled. For more information, see Known issues.
These short lines cover a very large area
Visit Microsoft Learn. Each version has "breaking changes"
- Some changes introduce binary incompatibilities (hence the warning about recompiling DLLs)
- Some changes introduce "Behavioral changes". From the Microsoft link above
- Behavioral change - Existing code and binaries may behave differently at run time. If the new behavior is undesirable, existing code would need to be updated and recompiled.
-
-
원인
One Identity have chosen to update the .NET framework version for very good reasons.
These reasons include
- Very large performance increases
- .NET 4.8 approaching end of life
- See the following Microsoft article
-
해결 방안
Before upgrading a Production Environment to version 9.3 or later, all scripts need to be checked in a lower level environment (for example dev/test) to ensure compatibility with .NET 8 (for 9.3.x) or .NET 10 (for version 10.0)
This includes not only syntactic validity (i.e. does it compile), but also behavior (does the script return the expected result) as custom scripts using .NET functions which have changed in any of the versions between .NET 5 up to .NET 8 or .NET 10 may no longer work as expected.
Note also that since scripts now have the capability of including NuGet packages, this means the compilation needs to be performed on a workstation with access to NuGet online sources, or a correctly configured local NuGet repository.