v0.9.0 - info about .net framework

get info about .net framework (reference path, installed versions)

find .net framework reference path

cli arg --net-fw-references-path, used as --net-fw-references-path System System.Data

This support also -f (--framework) argument, like -f v4.7.
Note that the value is the target framework version (TargetFrameworkVersion msbuild prop)

this command doesnt need a project to be used

find installed .net framework versions

cli arg --installed-net-frameworks
list of the installed .NET Frameworks versions

this command doesnt need a project to be used

Additional

• fix --project-reference , now show the project refs paths
• minor breaking change, ResolvedP2PRefsInfo.TargetFramework is now string option (was string), because old sdk project doesnt use that

v0.8.0 - support old fsproj

add more cli options:

--msbuild => path to msbuild
--dotnetcli => path to dotnet, used for "dotnet msbuild"
--msbuild-host => what msbuild host to run, to force specific or auto (oldsdk/dotnetsdk). By default for oldsdk is msbuild and dotnetsdk is dotnet

Old fsproj parser

Use msbuild from command line to ask msbuild info about the project (not using msbuild as library)

How works:

• override the CoreCompile target, to gather info about the project properties (OutputType, etc)
• convert the msbuild properties to fsc args, using the Fsc task code

To override the CoreCompile target, the CustomAfterMicrosoftCommonTargets property is used as hook to import the generate .target file after F# targets are imported (msbuild override targets with same name, based on import sequence)

To convert msbuild properties to fsc compiler args, use the same Fsc msbuild task class code.

• Fsc msbuild task from microsoft/visualfsharp repo
• msbuild classes from mono/mono repo

The strategy for msbuild properties -> fsc args can be customized

Additional:

• dotnet-proj-info support netcoreapp2.0 framework
• Dotnet.ProjInfo support netstandard2.0 framework
• the Fsc task is not bundled with Dotnet.ProjInfo, so clients can pin another version if needed

v0.6.0

Fix errors with deep project references #1
Fix failure if path (project or temp) contains whitespace #2

milestone v0.6.0

v0.5.0

• Dotnet.ProjInfo to use as lib
• dotnet-proj-info to use as cli tool

see examples for cli usage