You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// Logic taken from https://github.com/dotnet/runtime/blob/78ed4438a42acab80541e9bde1910abaa8841db2/src/libraries/Microsoft.Extensions.Hosting/src/HostingHostBuilderExtensions.cs#L209-L227
185
+
// Logic taken from https://github.com/dotnet/runtime/blob/dc5a6c8be1644915c14c4a464447b0d54e223a46/src/libraries/Microsoft.Extensions.Hosting/src/HostingHostBuilderExtensions.cs#L209-L227
186
186
187
187
// If we're running anywhere other than C:\Windows\system32, we default to using the CWD for the ContentRoot.
188
188
// However, since many things like Windows services and MSIX installers have C:\Windows\system32 as there CWD which is not likely
189
189
// to really be the home for things like appsettings.json, we skip changing the ContentRoot in that case. The non-"default" initial
190
190
// value for ContentRoot is AppContext.BaseDirectory (e.g. the executable path) which probably makes more sense than the system32.
191
191
192
-
// In my testing, both Environment.CurrentDirectory and Environment.GetFolderPath(Environment.SpecialFolder.System) return the path without
192
+
// In my testing, both Environment.CurrentDirectory and Environment.SystemDirectory return the path without
193
193
// any trailing directory separator characters. I'm not even sure the casing can ever be different from these APIs, but I think it makes sense to
194
194
// ignore case for Windows path comparisons given the file system is usually (always?) going to be case insensitive for the system path.
0 commit comments