Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
/ corefx Public archive

Adding more details for how to build and test for the corefx repo #4

Merged
merged 1 commit into from
Nov 11, 2014
Merged

Adding more details for how to build and test for the corefx repo #4

merged 1 commit into from
Nov 11, 2014

Conversation

Petermarcu
Copy link
Member

No description provided.

@nguerrera
Copy link
Contributor

👍 Looks good to me.


* By default, the core tests are run as part of the build. A test report for the build will be output on the console at the end of a successful build.
* To view the tests for a solution in Visual Studio you need to install **xUnit.net runner for Visual Studio**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, we'd like to remove this requirement in the future.

@FiveTimesTheFun
Copy link
Contributor

Looks good :shipit:

@FiveTimesTheFun
Copy link
Contributor

It looks like this information is partially duplicated in the developer guide. These should probably be combined.

https://github.com/dotnet/corefx/blob/master/docs/Developers.md

@stephentoub
Copy link
Member

Looks good. Just curious, regarding "Visual Studio Solution (.sln) files exist for related groups of libraries", did we consider and dismiss the idea of having an additional .sln that includes all of the projects, covering the equivalent of what gets built by the root build? Or is that not possible for some technical reason?

@mellinoe
Copy link
Contributor

I think we were hesitant to create a "big giant solution" just because it gets a little too hard to maintain, especially when there are lots of projects. Adding, removing, merging projects into the solution also gets problematic. We also talked about possibly adding a script that would auto-generate a solution so we didn't have to worry about those kinds of issues.

@dotnet-bot dotnet-bot merged commit c26ee75 into dotnet:master Nov 11, 2014
pgavlin pushed a commit to pgavlin/corefx that referenced this pull request Aug 11, 2015
@karelz karelz modified the milestone: 1.0.0-rtm Dec 3, 2016
krwq pushed a commit to krwq/corefx that referenced this pull request Mar 2, 2017
DnlHarvey added a commit that referenced this pull request Apr 13, 2017
Olafski pushed a commit to Olafski/corefx that referenced this pull request Jun 15, 2017
kasiabulat added a commit that referenced this pull request Aug 9, 2019
* Specification (#4)

* specification consisting of following sections added:
  - introduction
  - goals
  - todos
  - example scenarios
  - design choices
  - implementation details
  - open questions
  - useful links
* review comments included
akrisiun added a commit to akrisiun/corefx that referenced this pull request Sep 29, 2019
akrisiun added a commit to akrisiun/corefx that referenced this pull request Sep 29, 2019
macrogreg pushed a commit to open-telemetry/opentelemetry-dotnet-instrumentation that referenced this pull request Sep 24, 2020
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
* Specification (dotnet/corefx#4)

* specification consisting of following sections added:
  - introduction
  - goals
  - todos
  - example scenarios
  - design choices
  - implementation details
  - open questions
  - useful links
* review comments included

Commit migrated from dotnet/corefx@7ec3954
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants