#2843, #2806

[MikhailArkhipov]

#2843 Failure to set AfterHostStarted working directory stops RHost

• add ACL check on the directory

#2806 Still occasionally get package load failures

• store provider rather than create workflow when editor instantiates keyboard processor

#2853 Error adding database connection

• reference signed and versioned binaries from lib

Update System.Collections.Immutable to 1.3.0

[int19h]

I don't think the write permission was the problem for that bug. In that case, it was a directory belonging to a different user, so it couldn't even be read.

FWIW, perhaps it's easier to just try to do Directory.GetFiles on it, and catch an exception? If it fails, then it's definitely not usable. I'm not sure it being not writeable would actually cause R to fail though.

[MikhailArkhipov]

OK. I wanted stricter check since writing generally assumes reading (in common sense case anyway)

[int19h]

I don't think that is the case for Windows ACLs, at least - I just tried, and you can deny read and allow write to the same user at the same time, and it actually enforces it in that manner.

[MikhailArkhipov]

Yes, it is possible in general case since ACLs may apply to, say, pipes.

[MikhailArkhipov]

I'll leave writing check method for now in case we need it