Skip to content
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

When building .Net Core projects prefer .Net Global Tool when available #523

Closed
7 tasks done
gep13 opened this issue Jul 5, 2020 · 0 comments · Fixed by #596
Closed
7 tasks done

When building .Net Core projects prefer .Net Global Tool when available #523

gep13 opened this issue Jul 5, 2020 · 0 comments · Fixed by #596
Assignees
Milestone

Comments

@gep13
Copy link
Member

gep13 commented Jul 5, 2020

At the minute, even though building a .Net Core project, some of the tools that are used are the full .Net Framework version. When building a .net core project we can assume that usage of .Net Global Tools are available, so we should prefer these when available.

  • GitVersion
  • GitReleaseManager
  • Codecov
  • Coveralls
  • Wyam
  • KuduSync
  • ReportGenerator
@gep13 gep13 added this to the 2.0.0 milestone Jul 5, 2020
@gep13 gep13 self-assigned this Jul 5, 2020
gep13 added a commit that referenced this issue Jul 5, 2020
Initially, just for ReportGenerator, which is currently causing a
problem when running on a Mac.
gep13 added a commit that referenced this issue Jul 5, 2020
gep13 added a commit that referenced this issue Jul 5, 2020
These will be used when running .net core.
gep13 added a commit that referenced this issue Jul 7, 2020
Switch to coveralls.net, rather than coveralls.io, as this includes a
.net Global Tool version.
gep13 added a commit that referenced this issue Jul 8, 2020
Rather than running the full .net framework version of the tool.
gep13 added a commit that referenced this issue Jul 11, 2020
The coveralls.net NuGet package is being used for both the full .net
framework version and the .Net Global tool version.  Pin to 0.7.0 for
the latest .Net framework version (which will mean it will run on Unix
systems) and also update to latest Cake.Coveralls addin which includes
a fix for a case sensitive issue.
AdmiringWorm pushed a commit to gep13/Cake.Recipe that referenced this issue Jul 11, 2020
The coveralls.net NuGet package is being used for both the full .net
framework version and the .Net Global tool version.  Pin to 0.7.0 for
the latest .Net framework version (which will mean it will run on Unix
systems) and also update to latest Cake.Coveralls addin which includes
a fix for a case sensitive issue.
AdmiringWorm added a commit to AdmiringWorm/Cake.Recipe that referenced this issue Jul 11, 2020
The current version of codecov-exe is broken when running
on windows when running builds for normal msbuild projects.
This commit updates codecov-exe to the latest bug fix
that fixes this issue.
gep13 pushed a commit to AdmiringWorm/Cake.Recipe that referenced this issue Jul 11, 2020
The current version of codecov-exe is broken when running
on windows when running builds for normal msbuild projects.
This commit updates codecov-exe to the latest bug fix
that fixes this issue.
gep13 added a commit that referenced this issue Jul 11, 2020
(GH-523) Update codecov to latest bug fix release
gep13 added a commit to gep13/Cake.Recipe that referenced this issue Jul 30, 2020
This is the last of the tools that can be moved to .net core.
AdmiringWorm added a commit that referenced this issue Jul 31, 2020
(GH-523) Use .Net Global tool version of KuduSync
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant