Update Path.GetTempPath description

[adamsitnik]

Recently we have backported dotnet/runtime#72452 to all supported versions of .NET and .NET Framework.

fixes dotnet/runtime#105012

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-io

[learn-build-service-prod]

Learn Build status updates of commit 48ec09b:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO/Path.xml	✅Succeeded	View

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[learn-build-service-prod]

Learn Build status updates of commit 97f2c48:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO/Path.xml	✅Succeeded	View

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[learn-build-service-prod]

Learn Build status updates of commit 7fd711d:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO/Path.xml	✅Succeeded	View

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[learn-build-service-prod]

Learn Build status updates of commit 4748704:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO/Path.xml	✅Succeeded	View

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[GrabYourPitchforks]

the method skips the preceding sequence and returns C:\Windows\SystemTemp

@adamsitnik Just to be pedantic, there are some cases where GetTempPath2 will return a directory other than %WINDIR%\SystemTemp. It might be worthwhile for us to link directly to https://learn.microsoft.com/windows/win32/api/fileapi/nf-fileapi-gettemppath2w rather than try to keep our docs up to date with them. This also makes us more future proof in case the OS updates the behavior going forward.

if your operating system is Windows 11 or Windows Server build 20348 or later

AFAIK we don't perform an OS version check. We simply look for the existence of the export. This is another case where we should link to the authoritative documentation for the underlying Win32 function rather than trying to duplicate it ourselves (and risk getting out of sync if they make a change regarding available versions).

[Mafii]

AFAIK we don't perform an OS version check.

That is true, but the change in .NET Framework (4.8.*) was not included in earlier builds of Windows, even if the GetTempPath2 API was available, as Windows ships .NET Framework itself.

For example, my co-worker has a Windows 11, Build 22631.3737, and the behaviour of C# applications targeted at net48 is different on his machine than on mine, which is Windows 11, Build 22631.3880. So just mentioning the presence of the GetTempPath2 API is not sufficient for .NET Framework (it is for .NET 6.0.32+...).

I agree linking the win32 API docs would be an improvement.

[GrabYourPitchforks]

Feedback from netfx servicing:

• Do not include the compat switch in the Learn docs. Documenting it gives the false impression that the team is committed to keeping the switch around in its current state indefinitely. Additionally, ownership of this rests with CSS, and we should allow them to be in charge of their own communication channel. (Typically CSS publishes these switches in a KB article if needed, not in the API docs.)
• We should update the docs to reflect all frameworks this change is applicable to. But it's not up to API docs to say when the change came in, because we should optimize for the world where the change rolls out in rapid fashion and almost everybody coming to these docs already has the changes pulled down.
• We should remove from the docs anything that we do not implement ourselves. For example, since we do not read env vars, we should not document them. Instead, link to an authoritative source of how our dependencies operate and make that doc team responsible for keeping the documentation up to date.

I'll send shortly a new iteration with includes these changes and merges Genevieve's recommendations.

[learn-build-service-prod]

Learn Build status updates of commit 8d7b7ab:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO/Path.xml	✅Succeeded	View

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[gewarren]

Preview looks good: https://review.learn.microsoft.com/en-us/dotnet/api/system.io.path.gettemppath?view=net-9.0&branch=pr-en-us-10118&tabs=windows#remarks

[adamsitnik]

I'll send shortly a new iteration with includes these changes and merges Genevieve's recommendations.

Thank you @GrabYourPitchforks !

[learn-build-service-prod]

Learn Build status updates of commit 88a640d:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO/Path.xml	✅Succeeded	View

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel