First of all I'd like to say I'm very happy with this recent development and I'm very interested in Swift on Windows.
There are, however, a few serious problems with the current state of affairs. I wanted to discuss them first here rather than opening JIRA issues for them in the bug tracker.
The issues are, in no particular order:
The installer is not properly signed. It's nice that there's a PGP signature but on Windows it's customary to use Authenticode PE signing. The self-signing by
dt.compnerd.comis nice but doesn't quite cut it.
Just like on macOS the
.pkgfiles are signed in the native was appropriate for the platform, so it should be on Windows. I shouldn't be getting SmartScreen warnings nor should I be getting the orange UAC prompt (unsigned or unidentified signer).
The default install directory is very extremely not Windows-like.
Program Fileswould orobably be a better place, but the very least we should have we specify an custom directory. The documentation says:
The default installation location for the toolchain on Windows is
but gives no way to specify another one.
swift-5.3-RELEASE-windows10.exe /layoutjust created a copy of the installer.
Continuing the previous issue, it would be very nice if there would a
.ziprelease, or any other release that supports "
Using Swift should absolutely not require us to drop files in the VS directory as currently required and documented in Support Files. The fact that it isn't persistent and requires maintenance after every VS update is just the icing on the cake.
The REPL should not require
If you feel that locating the Python install in the Registry is not something you should do and want to require Python in
PATHyou should require
py.exerather than Python.
If I had to sort them by importance for me it would be: #4, #3, #2, #1 and #5.
#4 is absolutely the worst problem. #5 and #1 are "merely" annoyances and #2 and #3 may be worked around but not as easily.
Thanks and great job on your work so far!