bf41c2eeaa
* Rename Umbraco.Core namespace to Umbraco.Cms.Core * Move extension methods in core project to Umbraco.Extensions * Move extension methods in core project to Umbraco.Extensions * Rename Umbraco.Examine namespace to Umbraco.Cms.Examine * Move examine extensions to Umbraco.Extensions namespace * Reflect changed namespaces in Builder and fix unit tests * Adjust namespace in Umbraco.ModelsBuilder.Embedded * Adjust namespace in Umbraco.Persistence.SqlCe * Adjust namespace in Umbraco.PublishedCache.NuCache * Align namespaces in Umbraco.Web.BackOffice * Align namespaces in Umbraco.Web.Common * Ensure that SqlCeSupport is still enabled after changing the namespace * Align namespaces in Umbraco.Web.Website * Align namespaces in Umbraco.Web.UI.NetCore * Align namespaces in Umbraco.Tests.Common * Align namespaces in Umbraco.Tests.UnitTests * Align namespaces in Umbraco.Tests.Integration * Fix errors caused by changed namespaces * Fix integration tests * Undo the Umbraco.Examine.Lucene namespace change This breaks integration tests on linux, since the namespace wont exists there because it's only used on windows. * Fix merge * Fix Merge
55 lines
2.5 KiB
C#
55 lines
2.5 KiB
C#
using System;
|
|
using System.IO;
|
|
using System.Linq;
|
|
using Umbraco.Cms.Core.Hosting;
|
|
|
|
namespace Umbraco.Cms.Core.IO
|
|
{
|
|
public class IOHelperWindows : IOHelper
|
|
{
|
|
public IOHelperWindows(IHostingEnvironment hostingEnvironment) : base(hostingEnvironment)
|
|
{
|
|
}
|
|
|
|
public override bool IsPathFullyQualified(string path)
|
|
{
|
|
// TODO: This implementation is taken from the .NET Standard 2.1 implementation. We should switch to using Path.IsPathFullyQualified once we are on .NET Standard 2.1
|
|
|
|
if (path.Length < 2)
|
|
{
|
|
// It isn't fixed, it must be relative. There is no way to specify a fixed
|
|
// path with one character (or less).
|
|
return false;
|
|
}
|
|
|
|
if (path[0] == Path.DirectorySeparatorChar || path[0] == Path.AltDirectorySeparatorChar)
|
|
{
|
|
// There is no valid way to specify a relative path with two initial slashes or
|
|
// \? as ? isn't valid for drive relative paths and \??\ is equivalent to \\?\
|
|
return path[1] == '?' || path[1] == Path.DirectorySeparatorChar || path[1] == Path.AltDirectorySeparatorChar;
|
|
}
|
|
|
|
// The only way to specify a fixed path that doesn't begin with two slashes
|
|
// is the drive, colon, slash format- i.e. C:\
|
|
return (path.Length >= 3)
|
|
&& (path[1] == Path.VolumeSeparatorChar)
|
|
&& (path[2] == Path.DirectorySeparatorChar || path[2] == Path.AltDirectorySeparatorChar)
|
|
// To match old behavior we'll check the drive character for validity as the path is technically
|
|
// not qualified if you don't have a valid drive. "=:\" is the "=" file's default data stream.
|
|
&& ((path[0] >= 'A' && path[0] <= 'Z') || (path[0] >= 'a' && path[0] <= 'z'));
|
|
}
|
|
|
|
public override bool PathStartsWith(string path, string root, params char[] separators)
|
|
{
|
|
// either it is identical to root,
|
|
// or it is root + separator + anything
|
|
|
|
if (separators == null || separators.Length == 0) separators = new[] { Path.DirectorySeparatorChar, Path.AltDirectorySeparatorChar };
|
|
if (!path.StartsWith(root, StringComparison.OrdinalIgnoreCase)) return false;
|
|
if (path.Length == root.Length) return true;
|
|
if (path.Length < root.Length) return false;
|
|
return separators.Contains(path[root.Length]);
|
|
}
|
|
}
|
|
}
|