dotnet-installer/TestAssets/TestProjects
2017-03-02 21:43:06 -08:00
..
AppWith2Tfm0Rid Fix long path 2017-02-28 11:58:06 -08:00
AppWith4netTfm0Rid Shorten another Test Asset name 2017-02-28 13:11:34 -08:00
AppWithAppDependency Upgrade Corefx and coreclr references 2016-08-31 10:41:47 -07:00
AppWithAssemblyInfo Migration: Handle different variations of specifying assembly attributes. 2016-11-18 18:05:00 +01:00
AppWithDepOnToolWithOutputName 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
AppWithDirectAndToolDep 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
AppWithDirectDep First try at refactor of Prepare.targets (#5647) 2017-02-13 13:06:30 -08:00
AppWithDirectDepWithOutputName 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
AppWithMultipleFxAndTools 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
AppWithOutputAssemblyName Upgrade Corefx and coreclr references 2016-08-31 10:41:47 -07:00
AppWithPackageNamedAfterFolder 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
AppWithToolDependency 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
DependencyContextFromTool 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
FSharpTestProjects Remove deprecated test assets (#4546) 2016-10-31 16:16:07 -07:00
InvalidSolution Updating the SDK to an SDK that includes globing for source and resources implicitly. 2017-01-05 12:31:48 -08:00
LibraryWithNetStandardLibRef When Library add reference to NETStandardLib if not present 2016-11-01 15:52:24 -07:00
LibraryWithoutNetStandardLibRef When Library add reference to NETStandardLib if not present 2016-11-01 15:52:24 -07:00
LibraryWithOutputAssemblyName Updating the SDK to an SDK that includes globing for source and resources implicitly. 2017-01-05 12:31:48 -08:00
LibraryWithUnresolvablePackageReference use missing package test to verify correct package feed parsing 2017-02-01 14:13:07 -08:00
MSBuildAppWithMultipleFrameworks 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
MSBuildAppWithMultipleFrameworksAndTools 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
MSBuildBareBonesProject Fix 4508: CLI verbs that call into msbuild should control their output (#4719) 2016-11-15 11:56:39 -08:00
MSBuildIntegration use Sdks attribute in dotnet new templates (#4916) 2016-12-04 22:31:58 -08:00
MSBuildTestApp 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
NewtonSoftDependentProject Adding End to End test for cache and filtered publish 2017-02-13 17:56:25 -08:00
NewtonsoftFilterProfile Adding End to End test for cache and filtered publish 2017-02-13 17:56:25 -08:00
Packages update version of nuget 2016-03-08 09:53:06 -08:00
PerformanceTestProjects Update Microsoft.NETCore.App to 1.0.3. 2017-01-05 08:57:53 -06:00
PJAppWithMultipleFrameworks Migration: Do not add RIDs for Library projects (#5279) 2017-01-11 17:05:12 -08:00
PJLibWithMultipleFrameworks Migration: Do not add RIDs for Library projects (#5279) 2017-01-11 17:05:12 -08:00
PJTestAppSimple Centralize Microsoft.Net.SDK Version (#4890) 2016-12-02 09:34:03 -08:00
PJTestLibraryWithConfiguration Adding an E2E test for pack with content during migration. 2017-02-23 23:07:38 -08:00
ProjectJsonConsoleTemplate dotnet-new csproj templates (#4382) 2016-10-14 00:06:35 -07:00
ProjectJsonWebTemplate 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
ProjectsWithGlobalJson [WIP] Reduce test target complexity [and running time] (#5403) 2017-01-22 14:40:00 -08:00
SlnFileWithNoProjectReferences dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid (#5218) 2017-01-05 12:04:57 -10:00
SlnFileWithNoProjectReferencesAndCSharpProject dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid (#5218) 2017-01-05 12:04:57 -10:00
SlnFileWithNoProjectReferencesAndFSharpProject dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid (#5218) 2017-01-05 12:04:57 -10:00
SlnFileWithNoProjectReferencesAndUnknownProject dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid (#5218) 2017-01-05 12:04:57 -10:00
SlnFileWithNoProjectReferencesAndUnknownProjectWithMultipleProjectTypeGuids dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid (#5218) 2017-01-05 12:04:57 -10:00
SlnFileWithNoProjectReferencesAndUnknownProjectWithSingleProjectTypeGuid dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid (#5218) 2017-01-05 12:04:57 -10:00
SlnFileWithNoProjectReferencesAndVBProject dotnet add uses ProjectTypeGuid or DefaultProjectTypeGuid (#5218) 2017-01-05 12:04:57 -10:00
TestAppDependencyGraph 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
TestAppSimple 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
TestAppWithContents green 2016-10-03 20:10:09 -07:00
TestAppWithEmbeddedResources 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
TestAppWithEmptySln 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
TestAppWithExplicitInclude fix 5466: explicity including a file causes a build break (#5475) 2017-01-27 18:39:44 -08:00
TestAppWithExplicitIncludeGlob fix EOL in test asset 2017-01-26 09:02:28 -08:00
TestAppWithLibrary Centralize Microsoft.Net.SDK Version (#4890) 2016-12-02 09:34:03 -08:00
TestAppWithLibraryUnderTFM 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
TestAppWithMigrateableScripts try again 2016-09-19 11:11:01 -07:00
TestAppWithMultipleFrameworksAndRuntimes 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
TestAppWithMultipleSlnFiles 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
TestAppWithProjDepTool 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
TestAppWithRuntimeOptions Updating versions in a few places that did not exist in the preview2 branch. 2016-09-02 15:01:59 -07:00
TestAppWithSigning pr feedback 2016-10-04 16:37:23 -07:00
TestAppWithSlnAndCaseSensitiveSolutionFolders 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
TestAppWithSlnAndCsprojFiles 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
TestAppWithSlnAndCsprojInSubDir 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
TestAppWithSlnAndCsprojInSubDirToRemove 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
TestAppWithSlnAndCsprojProjectGuidFiles 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
TestAppWithSlnAndCsprojToRemove 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
TestAppWithSlnAndDuplicateProjectReferences 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
TestAppWithSlnAndExistingCsprojReferences 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
TestAppWithSlnAndExistingCsprojReferencesWithEscapedDirSep 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
TestAppWithSlnAndLastCsprojInSubDirToRemove 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
TestAppWithSlnAndSolutionFolders 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
TestAppWithUnqualifiedDependencies Adding another global.json to a failing test asset. 2017-02-01 13:58:15 -08:00
TestLibraryWithAnalyzer Updating CoreFX, CoreCLR, Roslyn, CoreSetup to stable versions. 2016-06-14 03:14:53 -05:00
TestLibraryWithConfiguration Updating the SDK to an SDK that includes globing for source and resources implicitly. 2017-01-05 12:31:48 -08:00
TestLibraryWithMultipleFrameworks Updating CoreFX, CoreCLR, Roslyn, CoreSetup to stable versions. 2016-06-14 03:14:53 -05:00
TestLibraryWithTwoFrameworks remove desktop from multi target test asset 2016-10-20 17:39:51 -07:00
VSTestDesktopAndNetCore Updating the version of the TestFramework which fixed the tests for dotnet test and vstest and actually managed to move the projects used there to 2.0. So, only test packages should remain 1.0. 2017-03-02 21:43:06 -08:00
VSTestDotNetCore Updating the version of the TestFramework which fixed the tests for dotnet test and vstest and actually managed to move the projects used there to 2.0. So, only test packages should remain 1.0. 2017-03-02 21:43:06 -08:00
VSTestXunitDesktopAndNetCore 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
VSTestXunitDotNetCore Updating the version of the TestFramework which fixed the tests for dotnet test and vstest and actually managed to move the projects used there to 2.0. So, only test packages should remain 1.0. 2017-03-02 21:43:06 -08:00
WebAppWithMissingFileInPublishOptions 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
global.json Clean up the temporary TestAsset changes. 2016-07-21 12:23:51 -05:00
NuGet.Config Clean up the temporary TestAsset changes. 2016-07-21 12:23:51 -05:00