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

Extensions - there are times when dotnet csharpier --version returns more than the version #533

Closed
belav opened this issue Dec 27, 2021 · 0 comments · Fixed by #566 or #579
Closed

Comments

@belav
Copy link
Owner

belav commented Dec 27, 2021

I had an instance of testing csharpier with VS2022 where the output contained a "welcome to .net 6" sort of message and ended with the version. This caused the extension to not figure out the csharpier version.
Working around it would just require reading the last line of the output.
This may also be affected by #531

belav added a commit that referenced this issue Jan 23, 2022
Use DOTNET_NOLOGO - fixes #533 and #549
Use a custom tools path to allow csharpier to be updated/installed while running - fixes #563 and #531
Use the solution version of csharpier - fixes #493
belav added a commit that referenced this issue Jan 23, 2022
Use DOTNET_NOLOGO - fixes #533 and #549
Use a custom tools path to allow csharpier to be updated/installed while running - fixes #563 and #531
Use the solution version of csharpier - fixes #493
belav added a commit that referenced this issue Jan 23, 2022
Use DOTNET_NOLOGO - fixes #533 and #549
Use a custom tools path to allow csharpier to be updated/installed while running - fixes #563 and #531
Use the solution version of csharpier - fixes #493
belav added a commit that referenced this issue Jan 24, 2022
* Updates to the rider plugin

Use DOTNET_NOLOGO - fixes #533 and #549
Use a custom tools path to allow csharpier to be updated/installed while running - fixes #563 and #531
Use the solution version of csharpier - fixes #493

* Self code review

* Hide or disable the reformat with csharpier action.

closes #567

* Some minor changes after testing

* One more little fix
@belav belav reopened this Jan 30, 2022
belav added a commit that referenced this issue Jan 30, 2022
Use DOTNET_NOLOGO - fixes #533 and #549
Use a custom tools path to allow csharpier to be updated/installed while running - fixes #563 and #531
Use the solution version of csharpier - fixes #493
belav added a commit that referenced this issue Jan 30, 2022
Use DOTNET_NOLOGO - fixes #533 and #549
Use a custom tools path to allow csharpier to be updated/installed while running - fixes #563 and #531
Use the solution version of csharpier - fixes #493
belav added a commit that referenced this issue Feb 2, 2022
Use DOTNET_NOLOGO #533
Use a custom tools path to allow csharpier to be updated/installed while running - fixes #563
shocklateboy92 added a commit that referenced this issue Feb 6, 2022
* Updates to the VS extensions

Use DOTNET_NOLOGO - fixes #533 and #549
Use a custom tools path to allow csharpier to be updated/installed while running - fixes #563 and #531
Use the solution version of csharpier - fixes #493

* Self code review

* Adding install actions, testing everything

* formatting code

Co-authored-by: Lasath Fernando <devel@lasath.org>
belav added a commit that referenced this issue Feb 6, 2022
* A couple fixes

Use DOTNET_NOLOGO #533
Use a custom tools path to allow csharpier to be updated/installed while running - fixes #563

* Some minor tweaks

* Some fixes after code review

* fixing issue

* Get proper version number

Co-authored-by: Lasath Fernando <devel@lasath.org>
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