Fix long path
2017-02-28 11:58:06 -08:00
Shorten another Test Asset name
2017-02-28 13:11:34 -08:00
Upgrade Corefx and coreclr references
2016-08-31 10:41:47 -07:00
Migration: Handle different variations of specifying assembly attributes.
2016-11-18 18:05:00 +01:00
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
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
First try at refactor of Prepare.targets ( #5647 )
2017-02-13 13:06:30 -08:00
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
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
Upgrade Corefx and coreclr references
2016-08-31 10:41:47 -07:00
Fixing dotnet migrate global.json. This was failing because we were turning global.json into an empty string and trying to construct a directory for it. The fix was to detect this and transform it into a . directory. Migrate is already respecting the projects node in global.json.
2017-01-19 10:55:23 -08:00
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
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
Remove deprecated test assets ( #4546 )
2016-10-31 16:16:07 -07:00
Updating the SDK to an SDK that includes globing for source and resources implicitly.
2017-01-05 12:31:48 -08:00
When Library add reference to NETStandardLib if not present
2016-11-01 15:52:24 -07:00
When Library add reference to NETStandardLib if not present
2016-11-01 15:52:24 -07:00
Updating the SDK to an SDK that includes globing for source and resources implicitly.
2017-01-05 12:31:48 -08:00
use missing package test to verify correct package feed parsing
2017-02-01 14:13:07 -08:00
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
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
Fix 4508: CLI verbs that call into msbuild should control their output ( #4719 )
2016-11-15 11:56:39 -08:00
use Sdks attribute in dotnet new templates ( #4916 )
2016-12-04 22:31:58 -08:00
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
Adding End to End test for cache and filtered publish
2017-02-13 17:56:25 -08:00
Adding End to End test for cache and filtered publish
2017-02-13 17:56:25 -08:00
update version of nuget
2016-03-08 09:53:06 -08:00
Update Microsoft.NETCore.App to 1.0.3.
2017-01-05 08:57:53 -06:00
Migration: Do not add RIDs for Library projects ( #5279 )
2017-01-11 17:05:12 -08:00
Migration: Do not add RIDs for Library projects ( #5279 )
2017-01-11 17:05:12 -08:00
Centralize Microsoft.Net.SDK Version ( #4890 )
2016-12-02 09:34:03 -08:00
Adding an E2E test for pack with content during migration.
2017-02-23 23:07:38 -08:00
dotnet-new csproj templates ( #4382 )
2016-10-14 00:06:35 -07:00
Fixing a failing test and adding a few more E2E tests around binplace content for migrated projects.
2017-02-23 22:55:35 -08:00
[WIP] Reduce test target complexity [and running time] ( #5403 )
2017-01-22 14:40:00 -08:00
dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid ( #5218 )
2017-01-05 12:04:57 -10:00
dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid ( #5218 )
2017-01-05 12:04:57 -10:00
dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid ( #5218 )
2017-01-05 12:04:57 -10:00
dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid ( #5218 )
2017-01-05 12:04:57 -10:00
dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid ( #5218 )
2017-01-05 12:04:57 -10:00
dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid ( #5218 )
2017-01-05 12:04:57 -10:00
dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid ( #5218 )
2017-01-05 12:04:57 -10:00
Fixing a failing test. Basically, now that global.json paths have precedence, we were using the CLI global.json and finding the wrong project dependencies.
2017-02-01 12:15:00 -08:00
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
green
2016-10-03 20:10:09 -07:00
Adding a Exclude @(EmbeddedResource) during migration so that we don't get duplicate resources when building migrated apps.
2016-12-15 11:17:20 -08:00
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
fix 5466: explicity including a file causes a build break ( #5475 )
2017-01-27 18:39:44 -08:00
fix EOL in test asset
2017-01-26 09:02:28 -08:00
Centralize Microsoft.Net.SDK Version ( #4890 )
2016-12-02 09:34:03 -08:00
Fixing project dependencies migration so that they are only conditioned when they where under a TFM in the project.json to begin with.
2016-10-21 18:00:17 -07:00
try again
2016-09-19 11:11:01 -07:00
Updating the M.NC.App version to 1.0.3 on a couple of new test assets.
2017-01-05 22:57:16 -08:00
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
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
Updating versions in a few places that did not exist in the preview2 branch.
2016-09-02 15:01:59 -07:00
pr feedback
2016-10-04 16:37:23 -07:00
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
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
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
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
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
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
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
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
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
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
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
Adding another global.json to a failing test asset.
2017-02-01 13:58:15 -08:00
Updating CoreFX, CoreCLR, Roslyn, CoreSetup to stable versions.
2016-06-14 03:14:53 -05:00
Updating the SDK to an SDK that includes globing for source and resources implicitly.
2017-01-05 12:31:48 -08:00
Updating CoreFX, CoreCLR, Roslyn, CoreSetup to stable versions.
2016-06-14 03:14:53 -05:00
remove desktop from multi target test asset
2016-10-20 17:39:51 -07:00
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
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
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
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
Adding a UpdateContextTransform that generates items with the Update attribute set instead of Include. Also, removed the Exists condition for published content, because now that we are using Update, that check is not needed. I left the option to set a condition on the metadata though.
2016-12-13 16:45:39 -08:00
Clean up the temporary TestAsset changes.
2016-07-21 12:23:51 -05:00
Clean up the temporary TestAsset changes.
2016-07-21 12:23:51 -05:00
