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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ If you are new to GitHub [here](https://help.github.com/categories/collaborating
16
16
17
17
As a first time contributor, you will be invited to sign the Contributor License Agreement (CLA). Please follow the instructions of the dotnet foundation bot reviewer on your PR to sign the agreement indicating that you have appropriate rights to your contribution.
18
18
19
-
Your pull request needs to reference a filed issue. Please fill in the template that is populated for the pull request. Only pull requests adressing small typos can have no issues associated with them.
19
+
Your pull request needs to reference a filed issue. Please fill in the template that is populated for the pull request. Only pull requests addressing small typos can have no issues associated with them.
20
20
21
21
An ML.NET team member will be assigned to your pull request once the continuous integration checks have passed successfully.
Copy file name to clipboardExpand all lines: README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Along with these ML capabilities this first release of ML.NET also brings the fi
18
18
19
19
ML.NET runs on Windows, Linux, and macOS - any platform where 64 bit [.NET Core](https://github.com/dotnet/core) or later is available.
20
20
21
-
The current release is 0.3. Check out the [release notes](docs/release-notes/0.3/release-0.3.md).
21
+
The current release is 0.4. Check out the [release notes](docs/release-notes/0.4/release-0.4.md).
22
22
23
23
First ensure you have installed [.NET Core 2.0](https://www.microsoft.com/net/learn/get-started) or later. ML.NET also works on the .NET Framework. Note that ML.NET currently must run in a 64 bit process.
In the SDK ImportAfter folder, this property is declared to point to Microsoft.TestPlatform.targets, which is the file containing the original VSTest target.
6
+
Since the Microsoft.TestPlatform.targets are in the ImportAfter folder, they would be imported after this file hence our empty VSTest target would be overriden,
7
+
in order to be able to override this target, we set the VSTestTargets property to an inexistent file path, so nothing will be imported and that way we successfully
8
+
overrode the VSTest target.
9
+
-->
10
+
<VSTestTargets>ignore.targets</VSTestTargets>
11
+
</PropertyGroup>
12
+
13
+
<!--
14
+
Copied from https://github.com/dotnet/arcade/blob/master/src/Microsoft.DotNet.Arcade.Sdk/tools/Empty.targets
15
+
16
+
Import this file to suppress all targets while allowing the project to participate in the build.
17
+
Workaround for https://github.com/dotnet/sdk/issues/2071.
18
+
19
+
The targets defined here are not sufficient for the project to be open in Visual Studio without issues though.
Copy file name to clipboardExpand all lines: docs/building/windows-instructions.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -46,14 +46,14 @@ You can use the Developer Command Prompt, Powershell or work in any regular cmd.
46
46
From a (non-admin) Command Prompt window:
47
47
48
48
-`build.cmd` - builds the assemblies
49
-
-`build.cmd -runTests` - builds the assemblies and runs tests
49
+
-`build.cmd -runTests` - called after a normal "build.cmd" will run all tests
50
50
-`build.cmd -buildPackages` called after a normal “build.cmd” will create the NuGet packages with the assemblies in “bin"
51
51
52
52
**Note**: Before working on individual projects or test projects you **must** run `build.cmd` from the root once before beginning that work. It is also a good idea to run `build.cmd` whenever you pull a large set of unknown changes into your branch.
53
53
54
54
### Running tests from the command line
55
55
56
-
From the root, use`build.cmd -runTests`.
56
+
From the root, run `build.cmd` and then`build.cmd -runTests`.
57
57
For more details, or to test an individual project, you can navigate to the test project directory and then use `dotnet test`
0 commit comments