Steffen Forkmann

yes we will make the FSharp.Compiler.Service pluggable. But tbh Paket is the only tool that you will find that is ready for such things and allows to generate load scripts...

all I'm saying is: it's basically there for you to use ;-)

Of course do we support version ranges and semver. To a much deeper level than nuget ;-) This technique supports the full power of paket. Am 25.02.2017 18:16 schrieb "Glenn...

For the record: I did not suggest to prefer one over the other. In F# scripting this will be pluggable. Am 25.02.2017 18:20 schrieb "Steffen Forkmann" : Of course do...

You can use everything from https://fsprojects.github.io/Paket/dependencies-file.html so it could look like this: #r "paket: NUnit ~> 2.6.3" #r "paket: DotNetZip >= 1.9" .... using NUnit; And Paket will make sure...

we don't do things like running powershell scripts on install - which we consider wrong But most things work as expected. Especially from scripting perspective

since these will be extracted by paket I guess you can still continue to do so

If someone makes me a member and transfer ownership to me then I can move it to fsprojects. Do we have a maintainer? Gustavo Leon schrieb am Mi., 27. Mai...

Id there a general strategy for type providers in dotnet sdk 3.x? Since we don't get any new fsharp.compiler.tools packages anymore - what's the replacement? /cc @dsyme @cartermp

Reality is that this was the only way to get things working. But it's not really important anymore. The question is how can we proceed?