You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And remove the need for a core3paket.csproj.references (one file less), so all project files are self-contained
On dotnet restore, the paket target will:
will read the PaketReference items/property
create an obj\core3paket.csproj.references (inside obj dir)
and call paket passing full path of obj\core3paket.csproj.references instead of infer location is near the .csproj
Like that the paket support seems more first class (like PackageReference), the csproj/fsproj is not verbose, and conditional based on framework or other is normal sintax ( Condition="'$(TargetFramework)' == 'net46'" ) already used for defined/props/packages
The text was updated successfully, but these errors were encountered:
enricosada
changed the title
put paket.references inside msbuild project for sdk preview3
put paket.references inside msbuild project for .net sdk projects
Jan 24, 2018
Atm with #1977 the
core3paket.csproj.references
file is used to add packages ref on restore, like before.I think the references can be included inside the fsproj:
or as property separated by
;
(easier for merge, likeTargetFrameworks
)And remove the need for a
core3paket.csproj.references
(one file less), so all project files are self-containedOn
dotnet restore
, the paket target will:PaketReference
items/propertyobj\core3paket.csproj.references
(insideobj
dir)obj\core3paket.csproj.references
instead of infer location is near the .csprojLike that the paket support seems more first class (like
PackageReference
), the csproj/fsproj is not verbose, and conditional based on framework or other is normal sintax ( Condition="'$(TargetFramework)' == 'net46'" ) already used for defined/props/packagesThe text was updated successfully, but these errors were encountered: