Per Bering
Per Bering
Will this get into v2.1?
FYI, the reason why we haven't done this before is that it takes for ever to do if your packages are stored on for example a Azure Storage file share....
Sounds like a good change and using Kestrel directly makes more sense. Why would `Watch-Directory.ps1` not work? @bplasmeijer do you see any problems doing this?
Ah yes that would be a problem. I wounder if we could use `dotnet watch run` in a development entrypoint so Watch-Directory.ps1 would still work?
mmm damn it does required that. FileSystemWatcher are not really good, always hit or miss and they are not much better inside a container :) - I'm thinking that we...
If possible can you try again on 2004? According to https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-2004%2Cwindows-10-2004#windows-10-host-os-compatibility, 1909 is "not support" but 2004 is.
Is this issue the same as Nick discovered with the firewall setup on Sitecore corp machines?
It's a good feature but checking `\\.\\pipe\\` doesn't work on Linux since it's a socket instead. I guess you could run `docker info` in a try/catch statement and then check...
Ah we are only talking about Build.ps1, missed that... Instead of failing you could switch the engine to Windows with `& (Join-Path $env:PROGRAMFILES "\Docker\Docker\DockerCli.exe") -SwitchWindowsEngine` and only fail in case...
Nice once, helpful messages. No sure if we should ask to switch or just switch? And the warnings should use Write-Warning.