Daniel Plaisted
ac67434ea4
Fix debian package generation
...
Previously, dotnet-deb-tool-consumer.csproj was copied to the out/artifacts folder before being restored. This no longer works as it depends on repo properties, and there is a Directory.Build.props in teh out directory to stop projects inside it from getting the repo properties. So this change restores it in-place instead.
2017-09-01 12:12:10 -07:00
Daniel Plaisted
ae0aa8ed24
Move dir.props to auto-imported Directory.Build.props
...
This is necessary for setting the intermediate output path to work correctly
2017-08-24 15:46:45 -07:00
Eric Erhardt
56f2652406
Fixing the reference to dotnet-deb-tool to be correct.
...
No more using * versions. Only specify the version in a single place.
2017-03-30 14:39:54 -05:00
Livar Cunha
ab28591c10
Replacing hard coded references to shared framework version.
2017-03-06 21:25:42 -08:00
Parallels
f42599dec2
Fixing ubuntu deb generation.
2017-03-03 11:13:41 -08:00
Livar Cunha
23e39c10b7
Moving as many of our test assets to netcoreapp2.0 as possible. I believe the only ones missing at the test packages, because tools always target 1.0. And the other ones are VSTestDotNetCore and VSTestXUnitDotNetCore, because we can't run tests on 2.0 yet. Or, when I tried it failed. I may came back to try this out later.
2017-03-02 17:41:21 -08:00
Eric Erhardt
7036fa1aef
Update dotnet-deb-tool-consumer to use the latest dotnet-deb-tool.
...
The latest deb-tool will use the CLI's runtime, which is required on distros that don't have .NET Core 1.0 installed.
2017-02-22 21:34:22 -06:00
