FSharp.Compiler.Service.ProjectCracker.dll is not in Nuget

[fbehrens]

How to pull it in ?

cc @forki

[forki]

@Krzysztof-Cieslak Am 04.01.2018 21:40 schrieb "Frank Behrens" <notifications@github.com>:

…

How to pull it in ? [image: image] <https://user-images.githubusercontent.com/13704/34583289-757f7c4e-f197-11e7-9f9e-51d21379439d.png> cc @forki <https://github.com/forki> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#31>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNC3yw8vmtjVlQXpuKdDDUc4FHSUeks5tHTdDgaJpZM4RTifX> .

[Krzysztof-Cieslak]

There is FSharp.Compiler.Service.ProjectCracker nuget package.... but not sure if using ProjectCracker is good idea anyway. Enrico's Dotnet.ProjInfo (https://github.com/enricosada/dotnet-proj-info) works better as far as I can tell....

[enricosada]

i dont want to vote because is mine, but ProjectCracker has many drawback (in process, known stackoverflow, depends on msbuild libs not always avaiable and special env var to set, doesnt really work on netcore because .net msbuild <> .net core msbuild).

if you can start with Dotnet.ProjInfo, works for both old fsproj and new fsproj (see https://github.com/fsharp/FsAutoComplete/ ) and anyway the data structure is the same (the one for FCS) so can be replaced if needed

[enricosada]

any issue with project parsing, anyone, feel free to ping me directly

[enricosada]

And about dotnet.projinfo, for POC, you dont need to use as library (more complicated maybe).
just call it from command line (ref https://github.com/enricosada/dotnet-proj-info/tree/master/examples using --fsc-args arg ) to get the list of fsc args (enough to initialize FCS, always)