-
Notifications
You must be signed in to change notification settings - Fork 15.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump target frameworks of C# programs from netcoreapp1.0 to netcoreapp2.1 #5838
Merged
anandolee
merged 12 commits into
protocolbuffers:master
from
ObsidianMinor:csharp/project-runtime-bump
Mar 11, 2019
Merged
Changes from 1 commit
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
d96bec2
Bump target frameworks from netcoreapp1.0 to netcoreapp2.2.
ObsidianMinor 5808f00
Re-add curl install
ObsidianMinor ad28622
Change all exe target to 2.1
ObsidianMinor afae499
Fix incorrect versions in global.json and Dockerfile
ObsidianMinor e4dc27d
Downgrade version to 2.1 to match exe targets
ObsidianMinor c24ec68
introduce separate testing Dockerfile for C#
jtattermusch 7d246f6
revert changes to the shared Dockerfile
jtattermusch b2e8f97
use netcoreapp2.1 for C# conformance tests
jtattermusch dfb873a
use language specific dockerfile for testing C#
jtattermusch 0efbd9a
Edit compatibility tests script to use parameters instead of file copies
ObsidianMinor 5e3e9fb
install dotnet SDK on windows before running the tests
jtattermusch da2db2a
update csharp_EXTRA_DIST
jtattermusch File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we call the dll directly instead of
dotnet run --no-build
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I personally feel more confident that this will really only run the pre-built dll as opposed to to running a dotnet command that can potentially do something extra. No reason to change this in this PR.