Create a FSharp.Tools NuGet package - closes #408 - #409
Conversation
|
Well, you need FSharp.Compiler.dll, FSharp.Compiler.Server.Shared.dll, FSharp.Compiler.InteractiveSettings.dll, fsiAnyCpu.exe. I also think it's correct to add FSharp.Build.dll and Microsoft.FSharp.Targets - in theory they feel as if they could be in a separate package, but I believe FSharp.Build.dll looks for fsc.exe in the same directory that it resides in by default, so it's appropriate to bundle them. |
|
I think this might still not work out-of-the box if you run this on a clean machine (i.e. Azure VM). At least I recently tried running Not sure if we can get the MSBUILD stuff from NuGet as a dependency or something...? |
|
ok I added these. I wonder if we should depend on FSharp.Core package, but I assume since we are an app this is not really a good idea and we would need to copy files anyway, |
|
Hmm, Tomas, do you remember what dependencies were those? |
|
Yes, for this I believe you should add all the relevant MSBuild DLLs as local copies. I think you can just change these references to be The whole thing would definitely need to be tested on OSX, Linux and Windows. Ideally you would package + test as part of CI. |
|
will look at this tomorrow. Now I have to watch Bayern vs. BVB ;-) 2015-04-28 20:06 GMT+02:00 Don Syme notifications@github.com:
|
|
Yes, first things first @forki ! |
|
done |
|
Could you change the name per this comment |
|
done |
There was a problem hiding this comment.
What about this one (Microsoft.Build?)
Create a FSharp.Tools NuGet package - closes #408
what else do we need?
/cc @dsyme @granicz