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
{{ message }}
This repository was archived by the owner on Jul 12, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 12, 2022. It is now read-only.
Well, that's fair enough, things move on. But, just in case it makes a difference, I hope those involved won't mind me tagging the last 3 committers to verify I should find another approach? - @jaredpar@alexsorokoletov@davkean
@kierenj indeed, I did not get any notifications on that project.
I guess Jared will have clearer picture. In my understanding, this approach (using Roslyn) is the most correct and straightforward. You can compile it against .NET/Mono and use the output.
I worked in a separate branch to run that thing using .NET Core but many dependencies are not yet there and there is some work to get them in.
I guess this project is alive in a way that you can use it. Lack of development is probably because recent .NET Standard 2 release.
This isn't a supported tool or product. It was a "hey we have a bunch of code that we are opening sourcing that has different code styles - let's fix that". Along the road we made changes as we open sourced more code. As we've stopped porting code - we stopped needing it as much.
We wrote it to scratch an itch - that itch has been scratched, so no focus on it anymore.
@davkean
First of all, thank you for sharing this code and "product". I'm grateful we have it (and assume many of people who contributed to issues and PRs).
What we need to understand is the future of this repo/code/tool.
There is a number of PRs ready to be merged and many good (as far as I can see).
Do we fork that repo and go there and contribute in a new place?
Wondering what are your thoughts.
Thank you
Reacted by Wayne Nilsen, Anders Wåglund, Jeffrey Rennie, Mani Gandham, csr-nick, Brian Lachniet, Wang Xiaoning, Vasili Puchko, Keith Hall and Joseph Kingry
When I was looking for an automatic C# style formatter, my used search engine showed up this project quite at the top. I am glad I looked further: dotnet-format is probably the tool you should use today.
Reacted by Darren Grayson, Erik LaBianca, Steven Volckaert, Nate Barbettini, Sean, Bruno Garcia, John Hagen, Lega, Victor Blomberg, Vlad Predovic and 8 more
Reacted by Victor Blomberg, Mo Doaie, Sergey Vershinin, irabeson, Chris Long and xdvarpunen
Activity
Ippo343 commentedon Aug 21, 2017
Seconded.
aweiker commentedon Sep 20, 2017
It appears the answer to that question is a clear 👎
schweinsbauch commentedon Sep 21, 2017
"We also use the .NET Codeformatter Tool to ensure the code base maintains a consistent style over time, the tool automatically fixes the code base to conform to the guidelines outlined above."
kierenj commentedon Sep 21, 2017
Well, that's fair enough, things move on. But, just in case it makes a difference, I hope those involved won't mind me tagging the last 3 committers to verify I should find another approach? - @jaredpar @alexsorokoletov @davkean
alexsorokoletov commentedon Sep 21, 2017
@kierenj indeed, I did not get any notifications on that project.
I guess Jared will have clearer picture. In my understanding, this approach (using Roslyn) is the most correct and straightforward. You can compile it against .NET/Mono and use the output.
I worked in a separate branch to run that thing using .NET Core but many dependencies are not yet there and there is some work to get them in.
I guess this project is alive in a way that you can use it. Lack of development is probably because recent .NET Standard 2 release.
danmoseley commentedon Sep 21, 2017
@karelz also.
davkean commentedon Sep 22, 2017
This isn't a supported tool or product. It was a "hey we have a bunch of code that we are opening sourcing that has different code styles - let's fix that". Along the road we made changes as we open sourced more code. As we've stopped porting code - we stopped needing it as much.
We wrote it to scratch an itch - that itch has been scratched, so no focus on it anymore.
alexsorokoletov commentedon Sep 23, 2017
@davkean
First of all, thank you for sharing this code and "product". I'm grateful we have it (and assume many of people who contributed to issues and PRs).
What we need to understand is the future of this repo/code/tool.
There is a number of PRs ready to be merged and many good (as far as I can see).
Do we fork that repo and go there and contribute in a new place?
Wondering what are your thoughts.
Thank you
SurferJeffAtGoogle commentedon Oct 24, 2017
FWIW, I wrote a 30-line powershell function that will convert a VS 2017 .csproj (including .NET core .csprojs) to a primitive VS 2015 .csproj, so codeformatter can still format my code. It's a hack and a half, but it works for my purposes. It's here:
https://github.com/GoogleCloudPlatform/dotnet-docs-samples/blob/442e0ef50e58acc5e0414cef31801e394b932724/BuildTools.psm1#L460
sbeyer commentedon Jun 13, 2019
When I was looking for an automatic C# style formatter, my used search engine showed up this project quite at the top. I am glad I looked further: dotnet-format is probably the tool you should use today.