Lukas Rieger

I wanted to add an end2end integration test, but hit an unexpected issue: With PR https://github.com/fsprojects/Paket/pull/2664 I made it so that the build doesn't use the local reference assemblies for...

Manual tests for both direct execution and bootstrapper exection were Ok. If you use the bootstrapper, then you also need the latest paket.exe downloaded, an old one from cache obviously...

merged master, now build is green again

It's not directly breaking, since you would have to enable it in the app.config manually. So if you do nothing, nothing changes. Can you maybe take a quick look at...

> would it work with paket global tool or magic mode? It should already work as is with magic mode, just set the app.config of the bootstrapper. > I feel...

As this PR wasn't merged, there is no such feature. It wasn't merged because the app settings is more of a hack, and it would have been preferable to add...

Thinking about this some more, I would prefer to keep discovery as-is, and just add the helper methods. That is, ``RunTestsInAssembly`` will only discover static properties. If you want to...

Sure. There are mainly three reasons to skip a test: 1) The test itself is WIP 2) The feature under test is WIP 3) The test is failing, you know...

After ``glasgow flash`` this seems to happen less often. It still errors out if I execute a glasgow command immediatly after plugging it in, but if I plug it in...

I use ``ContextInsensitive`` and would appreciate it also being in the built-in version. There are two related but slightly different use-cases for ``ConfigureAwait (false)``: 1) move from UI Thread to...