From 52908bae9b6d5894c46b97da4cb46ad994072d95 Mon Sep 17 00:00:00 2001 From: Nirmal Guru Date: Wed, 12 Feb 2020 10:10:46 +0530 Subject: [PATCH 1/6] Remove unused 'Tasks.UnitTests2' project This is a part of XMake project in VS repo. This is not used here in this MSBuild repo. --- src/Tasks.UnitTests2/AssemblyIdentityTest.cs | 125 ---------------- src/Tasks.UnitTests2/AuthoringTests.txt | 136 ------------------ .../Properties/AssemblyInfo.cs | 33 ----- src/Tasks.UnitTests2/UtilTest.cs | 96 ------------- .../XMakeTasksUnitTests.csproj | 100 ------------- 5 files changed, 490 deletions(-) delete mode 100644 src/Tasks.UnitTests2/AssemblyIdentityTest.cs delete mode 100644 src/Tasks.UnitTests2/AuthoringTests.txt delete mode 100644 src/Tasks.UnitTests2/Properties/AssemblyInfo.cs delete mode 100644 src/Tasks.UnitTests2/UtilTest.cs delete mode 100644 src/Tasks.UnitTests2/XMakeTasksUnitTests.csproj diff --git a/src/Tasks.UnitTests2/AssemblyIdentityTest.cs b/src/Tasks.UnitTests2/AssemblyIdentityTest.cs deleted file mode 100644 index 5425479a9a6..00000000000 --- a/src/Tasks.UnitTests2/AssemblyIdentityTest.cs +++ /dev/null @@ -1,125 +0,0 @@ -using Microsoft.Build.Tasks.Deployment.ManifestUtilities; -using Microsoft.VisualStudio.TestTools.UnitTesting; -using System.Collections.Generic; -namespace XMakeTasksUnitTests -{ - - - /// - ///This is a test class for AssemblyIdentityTest and is intended - ///to contain all AssemblyIdentityTest Unit Tests - /// - [TestClass()] - public class AssemblyIdentityTest - { - - - private TestContext testContextInstance; - - /// - ///Gets or sets the test context which provides - ///information about and functionality for the current test run. - /// - public TestContext TestContext - { - get - { - return testContextInstance; - } - set - { - testContextInstance = value; - } - } - - #region Additional test attributes - // - //You can use the following additional attributes as you write your tests: - // - //Use ClassInitialize to run code before running the first test in the class - //[ClassInitialize()] - //public static void MyClassInitialize(TestContext testContext) - //{ - //} - // - //Use ClassCleanup to run code after all tests in a class have run - //[ClassCleanup()] - //public static void MyClassCleanup() - //{ - //} - // - //Use TestInitialize to run code before running each test - //[TestInitialize()] - //public void MyTestInitialize() - //{ - //} - // - //Use TestCleanup to run code after each test has run - //[TestCleanup()] - //public void MyTestCleanup() - //{ - //} - // - #endregion - - - /// - ///A test for IsFrameworkAssembly - /// - [TestMethod()] - public void IsFrameworkAssemblyTest() - { - bool actual; - IList listOfInstalledFrameworks = FrameworkMultiTargeting.GetSupportedTargetFrameworks(); - - // if 2.0 is installed on this computer, we will test IsFrameworkAssembly for 2.0 assemblies. - if (hasVersion(listOfInstalledFrameworks, "Version=v2.0")) - { - //if (hasVersion(listOfInstalledFrameworks - // Test 2.0 CLR binary - // "Microsoft.Build.Engine" Version="2.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" Culture="neutral" ProcessorArchitecture="MSIL" FileVersion="2.0.50727.3026" InGAC="true" /> - AssemblyIdentity clr2Binary = new AssemblyIdentity("Microsoft.Build.Engine", "2.0.0.0", "b03f5f7f11d50a3a", "neutral", "MSIL"); - actual = clr2Binary.IsFrameworkAssembly; - Assert.IsTrue(actual); - } - - if (hasVersion(listOfInstalledFrameworks, "Version=v3.0")) - { - // Test 3.0 CLR binary - // AssemblyName="System.ServiceModel" Version="3.0.0.0" PublicKeyToken="b77a5c561934e089" Culture="neutral" ProcessorArchitecture="MSIL" InGAC="false" IsRedistRoot="true" /> - AssemblyIdentity clr3Binary = new AssemblyIdentity("System.ServiceModel", "3.0.0.0", "b77a5c561934e089", "neutral", "MSIL"); - actual = clr3Binary.IsFrameworkAssembly; - Assert.IsTrue(actual); - } - - if (hasVersion(listOfInstalledFrameworks, "Version=v3.5")) - { - // Test 3.5 CLR binary - // AssemblyName="Microsoft.Build.Tasks.v3.5" Version="3.5.0.0" PublicKeyToken="b03f5f7f11d50a3a" Culture="neutral" ProcessorArchitecture="MSIL" InGAC="false" /> - AssemblyIdentity clr35Binary = new AssemblyIdentity("Microsoft.Build.Tasks.v3.5", "3.5.0.0", "b03f5f7f11d50a3a", "neutral", "MSIL"); - actual = clr35Binary.IsFrameworkAssembly; - Assert.IsTrue(actual); - } - - if (hasVersion(listOfInstalledFrameworks, "Version=v4.0")) - { - // Test 4.0 CLR binary - // AssemblyName="Microsoft.VisualBasic" Version="10.0.0.0" PublicKeyToken="b03f5f7f11d50a3a" Culture="neutral" ProcessorArchitecture="MSIL" FileVersion="4.0.41117.0" InGAC="true" /> - AssemblyIdentity clr4Binary = new AssemblyIdentity("Microsoft.VisualBasic", "10.0.0.0", "b03f5f7f11d50a3a", "neutral", "MSIL"); - actual = clr4Binary.IsFrameworkAssembly; - Assert.IsTrue(actual); - } - } - - private bool hasVersion(IList listOfInstalledFrameworks, string p) - { - foreach (string fx in listOfInstalledFrameworks) - { - if (fx.Contains(p)) - return true; - } - - return false; - } - } -} diff --git a/src/Tasks.UnitTests2/AuthoringTests.txt b/src/Tasks.UnitTests2/AuthoringTests.txt deleted file mode 100644 index 3eb1fca8202..00000000000 --- a/src/Tasks.UnitTests2/AuthoringTests.txt +++ /dev/null @@ -1,136 +0,0 @@ -========================================================================== - Visual Studio Team System: Overview of Authoring and Running Tests -========================================================================== - -This overview describes the features for authoring and running tests in -Visual Studio Team System and Visual Studio Team Edition for Software Testers. - -Opening Tests -------------- -To open a test, open a test project or a test metadata file (a file with -extension .vsmdi) that contains the definition of the test. You can find -test projects and metadata files in Solution Explorer. - -Viewing Tests -------------- -To see which tests are available to you, open the Test View window. Or, -if you have installed Team Edition for Software Testers, you can also open -the Test List Editor window to view tests. - -To open the Test View window, click the Test menu, point to Windows, and -then click Test View. To open the Test List Editor window (if you have -installed Team Edition for Software Testers), click Test, point to Windows, -and then click Test List Editor. - -Running Tests -------------- -You can run tests from the Test View window and the Test List Editor window. -See Viewing Tests to learn how to open these windows. To run one or more -tests displayed in the Test View window, first select the tests in that -window; to select multiple tests, hold either the Shift or CTRL key while -clicking tests. Then click the Run Tests button in the Test View window -toolbar. - -If you have installed Visual Studio Team Edition for Software Testers, you can -also use the Test List Editor window to run tests. To run tests in Test List Editor, -select the check box next to each test that you want to run. Then click the -Run Tests button in the Test List Editor window toolbar. - -Viewing Test Results --------------------- -When you run a test or a series of tests, the results of the test run will be -shown in the Test Results window. Each individual test in the run is shown on -a separate line so that you can see its status. The window contains an -embedded status bar in the top half of the window that provides you with -summary details of the complete test run. - -To see more detailed results for a particular test result, double-click it in -the Test Results window. This opens a window that provides more information -about the particular test result, such as any specific error messages returned -by the test. - -Changing the way that tests are run ------------------------------------ -Each time you run one or more tests, a collection of settings is used to -determine how those tests are run. These settings are contained in a “test -settings” file. - -Here is a partial list of the changes you can make with a test settings file: - - - Change the naming scheme for each test run. - - Change the test controller that the tests are run on so that you can run - tests remotely. - - Gather code coverage data for the code being tested so that you can see - which lines of code are covered by your tests. - - Enable and disable test deployment. - - Specify additional files to deploy before tests are run. - - Select a different host, ASP.NET, for running ASP.NET unit tests. - - Select a different host, the smart device test host, for running smart device unit tests. - - Set various properties for the test agents that run your tests. - - Specify to use data collectors that can collect various information as - the tests are running. - - Run custom scripts at the start and end of each test run so that you can - set up the test environment exactly as required each time tests are run. - - Set time limits for tests and test runs. - - Set the browser mix and the number of times to repeat Web tests in the - test run. - -By default, a test settings file is created whenever you create a new test -project. You make changes to this file by double-clicking it in Solution -Explorer and then changing the test settings. (Test settings files have the -extension .testsettings.) - -A solution can contain multiple test settings files. Only one of those -files, known as the “Active” test settings file, is used to determine the -settings that are currently used for test runs. You select the active test -settings by clicking Select Active Test Settings on the Test menu. - -------------------------------------------------------------------------------- - -Test Types ----------- -Using Visual Studio Team Edition for Software Testers, you can create a number -of different test types: - -Unit test: Use a unit test to create a programmatic test in C++, Visual C# or -Visual Basic that exercises source code. A unit test calls the methods of a -class, passing suitable parameters, and verifies that the returned value is -what you expect. -There are three specialized variants of unit tests: - - Data-driven unit tests are created when you configure a unit test to be - called repeatedly for each row of a data source. The data from each row - is used by the unit test as input data. - - ASP.NET unit tests are unit tests that exercise code in an ASP.NET Web - application. - - Smart device unit tests are unit tests that are deployed to a smart device - or emulator and then executed by the smart device test host. - -Web Test: Web tests consist of an ordered series of HTTP requests that you -record in a browser session using Microsoft Internet Explorer. You can have -the test report specific details about the pages or sites it requests, such -as whether a particular page contains a specified string. - -Load Test: You use a load test to encapsulate non-manual tests, such as -unit, Web, and generic tests, and then run them simultaneously by using -virtual users. Running these tests under load generates test results, -including performance and other counters, in tables and in graphs. - -Generic test: A generic test is an existing program wrapped to function as a -test in Visual Studio. The following are examples of tests or programs that -you can turn into generic tests: - - An existing test that uses process exit codes to communicate whether the - test passed or failed. 0 indicates passing and any other value indicates - a failure. - - A general program to obtain specific functionality during a test scenario. - - A test or program that uses a special XML file (called a “summary results - file”), to communicate detailed results. - -Manual test: The manual test type is used when the test tasks are to be -completed by a test engineer as opposed to an automated script. - -Ordered test: Use an ordered test to execute a set of tests in an order you -specify. - -------------------------------------------------------------------------------- - - diff --git a/src/Tasks.UnitTests2/Properties/AssemblyInfo.cs b/src/Tasks.UnitTests2/Properties/AssemblyInfo.cs deleted file mode 100644 index ca470e18458..00000000000 --- a/src/Tasks.UnitTests2/Properties/AssemblyInfo.cs +++ /dev/null @@ -1,33 +0,0 @@ -using System.Reflection; -using System.Runtime.CompilerServices; -using System.Runtime.InteropServices; - -// General Information about an assembly is controlled through the following -// set of attributes. Change these attribute values to modify the information -// associated with an assembly. -[assembly: AssemblyTitle("XMakeTasksUnitTests")] -[assembly: AssemblyDescription("")] -[assembly: AssemblyConfiguration("")] -[assembly: AssemblyProduct("XMakeTasksUnitTests")] -[assembly: AssemblyTrademark("")] -[assembly: AssemblyCulture("")] - -// Setting ComVisible to false makes the types in this assembly not visible -// to COM componenets. If you need to access a type in this assembly from -// COM, set the ComVisible attribute to true on that type. -[assembly: ComVisible(false)] - -// The following GUID is for the ID of the typelib if this project is exposed to COM -[assembly: Guid("de6f3aea-4f78-444d-9f24-6955d929c1f9")] - -// Version information for an assembly consists of the following four values: -// -// Major Version -// Minor Version -// Build Number -// Revision -// -// You can specify all the values or you can default the Revision and Build Numbers -// by using the '*' as shown below: -[assembly: AssemblyVersion("1.0.0.0")] -[assembly: AssemblyFileVersion("1.0.0.0")] diff --git a/src/Tasks.UnitTests2/UtilTest.cs b/src/Tasks.UnitTests2/UtilTest.cs deleted file mode 100644 index ff01de06a76..00000000000 --- a/src/Tasks.UnitTests2/UtilTest.cs +++ /dev/null @@ -1,96 +0,0 @@ -using Microsoft.Build.Tasks.Deployment.ManifestUtilities; -using Microsoft.VisualStudio.TestTools.UnitTesting; -namespace XMakeTasksUnitTests -{ - - - /// - ///This is a test class for UtilTest and is intended - ///to contain all UtilTest Unit Tests - /// - [TestClass()] - public class UtilTest - { - - - private TestContext testContextInstance; - - /// - ///Gets or sets the test context which provides - ///information about and functionality for the current test run. - /// - public TestContext TestContext - { - get - { - return testContextInstance; - } - set - { - testContextInstance = value; - } - } - - #region Additional test attributes - // - //You can use the following additional attributes as you write your tests: - // - //Use ClassInitialize to run code before running the first test in the class - //[ClassInitialize()] - //public static void MyClassInitialize(TestContext testContext) - //{ - //} - // - //Use ClassCleanup to run code after all tests in a class have run - //[ClassCleanup()] - //public static void MyClassCleanup() - //{ - //} - // - //Use TestInitialize to run code before running each test - //[TestInitialize()] - //public void MyTestInitialize() - //{ - //} - // - //Use TestCleanup to run code after each test has run - //[TestCleanup()] - //public void MyTestCleanup() - //{ - //} - // - #endregion - - - /// - ///A test for GetClrVersion - /// - [TestMethod()] - [DeploymentItem("Microsoft.Build.Tasks.v4.0.dll")] - public void GetClrVersionTest() - { - string targetFrameworkVersion = "v3.5"; - string expected = "2.0.50727.0"; - string actual; - actual = Util_Accessor.GetClrVersion(targetFrameworkVersion); - Assert.AreEqual(expected, actual); - - targetFrameworkVersion = "3.5"; - actual = Util_Accessor.GetClrVersion(targetFrameworkVersion); - Assert.AreEqual(expected, actual); - - System.Version currentVersion = System.Environment.Version; - System.Version clr4Version = new System.Version(currentVersion.Major, currentVersion.Minor, currentVersion.Build, 0); - - targetFrameworkVersion = "v4.0"; - actual = Util_Accessor.GetClrVersion(targetFrameworkVersion); - expected = clr4Version.ToString(); - Assert.AreEqual(expected, actual); - - targetFrameworkVersion = "v4.2"; - actual = Util_Accessor.GetClrVersion(targetFrameworkVersion); - expected = clr4Version.ToString(); - Assert.AreEqual(expected, actual); - } - } -} diff --git a/src/Tasks.UnitTests2/XMakeTasksUnitTests.csproj b/src/Tasks.UnitTests2/XMakeTasksUnitTests.csproj deleted file mode 100644 index 78562a2f182..00000000000 --- a/src/Tasks.UnitTests2/XMakeTasksUnitTests.csproj +++ /dev/null @@ -1,100 +0,0 @@ - - - Debug - AnyCPU - 10.0.10911 - 2.0 - {9EA71CF9-9A62-4ED8-AFE8-DD5753EE377B} - Library - Properties - XMakeTasksUnitTests - XMakeTasksUnitTests - v4.0 - 512 - {3AC096D0-A1C2-E12C-1390-A8335801FDAB};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC} - - - true - full - false - bin\Debug\ - prompt - 4 - - - pdbonly - true - bin\Release\ - prompt - 4 - - - - False - ..\..\Framework\objr\i386\Microsoft.Build.Framework.dll - - - False - ..\objr\i386\Microsoft.Build.Tasks.v4.0.dll - - - False - ..\..\Utilities\objr\i386\Microsoft.Build.Utilities.v4.0.dll - - - - $(SdkRefPath)\System.dll - - - False - ..\..\..\..\public\sdk\ref\v4.0\System.Configuration.dll - - - False - ..\..\..\..\public\sdk\ref\v4.0\System.Core.dll - - - False - ..\..\..\..\public\sdk\ref\v4.0\System.Data.dll - - - False - ..\..\..\..\public\sdk\ref\v4.0\System.Design.dll - - - False - ..\..\..\..\public\sdk\ref\v4.0\System.Drawing.dll - - - False - ..\..\..\..\public\sdk\ref\v4.0\System.Security.dll - - - False - ..\..\..\..\public\sdk\ref\v4.0\System.Windows.Forms.dll - - - False - ..\..\..\..\public\sdk\ref\v4.0\System.XML.dll - - - - - - - - - - - - - - - - \ No newline at end of file From 60746be6ff97701dafe6499be0ad3d96cb8cca04 Mon Sep 17 00:00:00 2001 From: Nirmal Guru Date: Wed, 12 Feb 2020 10:10:47 +0530 Subject: [PATCH 2/6] Remove unused 'netci.groovy' file Replaced with Azure Pipelines and Arcade Sdk --- netci.groovy | 89 ---------------------------------------------------- 1 file changed, 89 deletions(-) delete mode 100644 netci.groovy diff --git a/netci.groovy b/netci.groovy deleted file mode 100644 index b74d67b95a4..00000000000 --- a/netci.groovy +++ /dev/null @@ -1,89 +0,0 @@ -// Import the utility functionality. -import jobs.generation.*; - -// The input project name -project = GithubProject - -// The input branch name (e.g. master) -branch = GithubBranchName - -// What this repo is using for its machine images at the current time -imageVersionMap = ['RHEL7.2' : 'latest'] - -def CreateJob(script, runtime, osName, isPR, machineAffinityOverride = null, shouldSkipTestsWhenResultsNotFound = false, isSourceBuild = false) { - def newJobName = Utilities.getFullJobName("innerloop_${osName}_${runtime}${isSourceBuild ? '_SourceBuild_' : ''}", isPR) - - // Create a new job with the specified name. The brace opens a new closure - // and calls made within that closure apply to the newly created job. - def newJob = job(newJobName) { - description('') - } - - newJob.with{ - steps{ - if(osName.contains("Windows") || osName.contains("windows")) { - batchFile(script) - } else { - shell(script) - } - } - - skipTestsWhenResultsNotFound = shouldSkipTestsWhenResultsNotFound - } - - // Add xunit result archiving. Skip if no results found. - Utilities.addXUnitDotNETResults(newJob, 'artifacts/**/TestResults/*.xml', skipTestsWhenResultsNotFound) - - if (machineAffinityOverride == null) { - def imageVersion = imageVersionMap[osName]; - Utilities.setMachineAffinity(newJob, osName, imageVersion) - } - else { - Utilities.setMachineAffinity(newJob, machineAffinityOverride) - } - - Utilities.standardJobSetup(newJob, project, isPR, "*/${branch}") - // Add archiving of logs (even if the build failed) - Utilities.addArchival(newJob, - 'artifacts/**/log/*.binlog,artifacts/**/log/*.log,artifacts/**/TestResults/*,artifacts/**/MSBuild_*.failure.txt', /* filesToArchive */ - '', /* filesToExclude */ - false, /* doNotFailIfNothingArchived */ - false, /* archiveOnlyIfSuccessful */) - // Add trigger - if (isPR) { - TriggerBuilder prTrigger = TriggerBuilder.triggerOnPullRequest() - - if (runtime == "MonoTest") { - // Until they're passing reliably, require opt in - // for Mono tests - prTrigger.setCustomTriggerPhrase("(?i).*test\\W+mono.*") - prTrigger.triggerOnlyOnComment() - } - - prTrigger.triggerForBranch(branch) - // Set up what shows up in Github: - prTrigger.setGithubContext("${osName} Build for ${runtime}") - prTrigger.emitTrigger(newJob) - } else { - if (runtime != "Mono") { - Utilities.addGithubPushTrigger(newJob) - } - } -} - -// sourcebuild simulation -CreateJob( - "./build/build.sh build -dotnetBuildFromSource -skiptests -pack -configuration Release", - "CoreCLR", - "RHEL7.2", - true, - null, - true, - true) - -JobReport.Report.generateJobReport(out) - -// Make the call to generate the help job -Utilities.createHelperJob(this, project, branch, - "Welcome to the ${project} Repository", // This is prepended to the help message - "Have a nice day!") // This is appended to the help message. You might put known issues here. From 00f6f18142adc3d0c49af5a91041a05485b56032 Mon Sep 17 00:00:00 2001 From: Nirmal Guru Date: Wed, 12 Feb 2020 10:10:49 +0530 Subject: [PATCH 3/6] Remove unused 'RunApiPort.bat' file No longer needed. Replaced with dotnet tool. --- RunApiPort.bat | 7 ------- 1 file changed, 7 deletions(-) delete mode 100644 RunApiPort.bat diff --git a/RunApiPort.bat b/RunApiPort.bat deleted file mode 100644 index 4c147cc6cf0..00000000000 --- a/RunApiPort.bat +++ /dev/null @@ -1,7 +0,0 @@ -@echo off -setlocal - -msbuild %~dp0src\MSBuild.sln /p:Configuration=Port-Progress - -set ANALYSIS_PATH=%~dp0bin\Windows_NT\Port-Progress -%~dp0ApiPort\ApiPort.exe analyze -f %ANALYSIS_PATH%\Microsoft.Build.dll -f %ANALYSIS_PATH%\Microsoft.Build.Framework.dll -f %ANALYSIS_PATH%\Microsoft.Build.Tasks.Core.dll -f %ANALYSIS_PATH%\Microsoft.Build.Utilities.Core.dll -f %ANALYSIS_PATH%\MSBuild.exe --target "ASP.NET 5, Version=1.0" \ No newline at end of file From 2362b8c24473e6d52e77c7a67102399cb4d001e7 Mon Sep 17 00:00:00 2001 From: Nirmal Guru Date: Wed, 12 Feb 2020 10:10:50 +0530 Subject: [PATCH 4/6] Remove unused 'runApiCompat.bat' file No longer needed. Replaced with dotnet tool. --- runApiCompat.bat | 14 -------------- 1 file changed, 14 deletions(-) delete mode 100644 runApiCompat.bat diff --git a/runApiCompat.bat b/runApiCompat.bat deleted file mode 100644 index 34ad60930c5..00000000000 --- a/runApiCompat.bat +++ /dev/null @@ -1,14 +0,0 @@ -@echo off -setlocal - -set MSBUILD_ROOT=%~dp0 - -REM Copy .NET 4.6 reference assemblies to the same folder as the MSBuild reference assemblies so ApiCompat can resolve their framework references -mkdir "%MSBUILD_ROOT%ref" -RoboCopy "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.6" "%MSBUILD_ROOT%ref" -RoboCopy "C:\Program Files (x86)\Reference Assemblies\Microsoft\MSBuild\v14.0" "%MSBUILD_ROOT%ref" - -REM Run ApiCompat -\\fxcore\tools\bin\ApiCompat.exe "%MSBUILD_ROOT%\bin\Windows_NT\Debug-NetCore\Microsoft.Build.Framework.dll,%MSBUILD_ROOT%\bin\Windows_NT\Debug-NetCore\Microsoft.Build.Utilities.Core.dll,%MSBUILD_ROOT%\bin\Windows_NT\Debug-NetCore\Microsoft.Build.Tasks.Core.dll" -implDirs:"%MSBUILD_ROOT%ref" -contractDepends:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.6,C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.6\Facades" -out:Differences.txt -baseline:CompatBaseline.txt - -endlocal From f402d92bd743fd6120fd4458d1a4adcc10d9a29f Mon Sep 17 00:00:00 2001 From: Nirmal Guru Date: Wed, 12 Feb 2020 10:10:52 +0530 Subject: [PATCH 5/6] Remove unused 'DefaultTasks.bat' file This batch file was used to copy targets for VS insertion in the old MSBuild project in VS repo. This is no longer needed as we achieve this using custom build logic in the project file itself. --- src/Tasks/DefaultTasks.bat | 23 ----------------------- 1 file changed, 23 deletions(-) delete mode 100644 src/Tasks/DefaultTasks.bat diff --git a/src/Tasks/DefaultTasks.bat b/src/Tasks/DefaultTasks.bat deleted file mode 100644 index df9739c3429..00000000000 --- a/src/Tasks/DefaultTasks.bat +++ /dev/null @@ -1,23 +0,0 @@ -if exist ..\..\..\XMakeCommandLine\bin\Debug copy ..\..\Microsoft.Common.tasks ..\..\..\XMakeCommandLine\bin\Debug -if exist ..\..\..\XMakeCommandLine\bin\Release copy ..\..\Microsoft.Common.tasks ..\..\..\XMakeCommandLine\bin\Release - -rem Deprecated -- remove -if exist ..\..\..\XMakeCommandLine\bin\Debug copy ..\..\CSharp.targets ..\..\..\XMakeCommandLine\bin\Debug -if exist ..\..\..\XMakeCommandLine\bin\Release copy ..\..\CSharp.targets ..\..\..\XMakeCommandLine\bin\Release - -rem Deprecated -- remove -if exist ..\..\..\XMakeCommandLine\bin\Debug copy ..\..\VisualBasic.targets ..\..\..\XMakeCommandLine\bin\Debug -if exist ..\..\..\XMakeCommandLine\bin\Release copy ..\..\VisualBasic.targets ..\..\..\XMakeCommandLine\bin\Release - -rem Deprecated -- remove -if exist ..\..\..\XMakeCommandLine\bin\Debug copy ..\..\Framework.targets ..\..\..\XMakeCommandLine\bin\Debug -if exist ..\..\..\XMakeCommandLine\bin\Release copy ..\..\Framework.targets ..\..\..\XMakeCommandLine\bin\Release - -if exist ..\..\..\XMakeCommandLine\bin\Debug copy ..\..\Microsoft.CSharp.targets ..\..\..\XMakeCommandLine\bin\Debug -if exist ..\..\..\XMakeCommandLine\bin\Release copy ..\..\Microsoft.CSharp.targets ..\..\..\XMakeCommandLine\bin\Release - -if exist ..\..\..\XMakeCommandLine\bin\Debug copy ..\..\Microsoft.VisualBasic.targets ..\..\..\XMakeCommandLine\bin\Debug -if exist ..\..\..\XMakeCommandLine\bin\Release copy ..\..\Microsoft.VisualBasic.targets ..\..\..\XMakeCommandLine\bin\Release - -if exist ..\..\..\XMakeCommandLine\bin\Debug copy ..\..\Microsoft.Common.targets ..\..\..\XMakeCommandLine\bin\Debug -if exist ..\..\..\XMakeCommandLine\bin\Release copy ..\..\Microsoft.Common.targets ..\..\..\XMakeCommandLine\bin\Release From 0d464c6b65d40ae8ccc6f7973d964c4894add3e6 Mon Sep 17 00:00:00 2001 From: Nirmal Guru Date: Wed, 12 Feb 2020 10:10:53 +0530 Subject: [PATCH 6/6] Remove unused 'CompatBaseline.txt' file Used when merging xplat branch. No longer needed. --- CompatBaseline.txt | 8 -------- 1 file changed, 8 deletions(-) delete mode 100644 CompatBaseline.txt diff --git a/CompatBaseline.txt b/CompatBaseline.txt deleted file mode 100644 index a15e37c83dd..00000000000 --- a/CompatBaseline.txt +++ /dev/null @@ -1,8 +0,0 @@ -# This API is marked obsolete and has been removed from the reference assembly -MembersMustExist : Member 'Microsoft.Build.Utilities.ToolTask.EnvironmentOverride.get()' does not exist in the implementation but it does exist in the contract. -#These changes will appear in Update 1; They represent added support for Framework 4.6.1 SDK. -MembersMustExist : Member 'Microsoft.Build.Tasks.GetFrameworkPath.FrameworkVersion461Path.get()' does not exist in the implementation but it does exist in the contract. -MembersMustExist : Member 'Microsoft.Build.Utilities.TargetDotNetFrameworkVersion Microsoft.Build.Utilities.TargetDotNetFrameworkVersion.Version461' does not exist in the implementation but it does exist in the contract. -EnumValuesMustMatch : Enum value 'Microsoft.Build.Utilities.TargetDotNetFrameworkVersion Microsoft.Build.Utilities.TargetDotNetFrameworkVersion.VersionLatest' is (System.Int32)7 in the implementation but (System.Int32)8 in the contract. -MembersMustExist : Member 'Microsoft.Build.Utilities.ToolLocationHelper.GetPathToDotNetFrameworkSdk()' does not exist in the implementation but it does exist in the contract. -MembersMustExist : Member 'Microsoft.Build.Utilities.ToolLocationHelper.GetPathToDotNetFrameworkSdkFile(System.String)' does not exist in the implementation but it does exist in the contract.