C# beautifiers for VS2012
-
I had to stop using such lovely tools because ... everyone here has their own preferred style and so Source Code Comparisons noted almost every line as a change. If you find a tool that prettifies C# on user preferences, but manages to avoid the issue with source control code comparisons - let me know!
MVVM # - I did it My Way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
A workaround it to keep two user preferences, one shared by everyone and one for yourself. Use the first one before a commit or a diff. Beautifiers save so many keystrokes that it is plain evil to have to give them up...
-
A workaround it to keep two user preferences, one shared by everyone and one for yourself. Use the first one before a commit or a diff. Beautifiers save so many keystrokes that it is plain evil to have to give them up...
Yeah - in another work environment I'd insist on that - here it's all too hard! We get some devs just manually going through code changing the bracketing to their preference. I suggested automating the build process on check in and was met with such negativity I've pretty much given up suggesting any improvements in process. Sorry - feeling particularly cynical today!
MVVM # - I did it My Way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
-
Franc Morales wrote:
My god.
Indeed I am.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. Those who seek perfection will only find imperfection nils illegitimus carborundum me, me, me me, in pictures
*Grabs popcorn*
You know the world is going crazy when the best rapper is a white guy, the best golfer is a black guy, the tallest guy in the NBA is Chinese, the Swiss hold the America's Cup, France is accusing the U.S. of arrogance, Germany doesn't want to go to war, and the three most powerful men in America are named "Bush", "Dick", and "Colon."
-
Link fail!
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
Lol, I've got no idea of what happened..... I may have written something wrong.. Well, here it goes again, but copied and pasted this time.. :-D http://www.narrange.net/[^]
-
You seem to be missing the point. Are you a programmer? How much time do you spend "beautifying with your eyes" tens of thousands of lines of legacy code?
Why would you even wanto to beautify legacy code? It's legacy code. Leave it be, or rewrite it. I don't beautify code. Code does not have to be beautifull. It has to work, and has to be readable. Make up and earrings will not make your code better. It will just distract you, and fool you into thinking it's perfect, untill it opens "it's" mouth and all that comes out is crap. Focus on better code, make it readable, add comments when needed. And structure it in the way you think it makes it easier to read and follow the logic behind it, but do it yourself and don't rely on tools. Who knows, maybe you'll catch a bug or two, or even identify flaws in the logic side.
-
Yeah - in another work environment I'd insist on that - here it's all too hard! We get some devs just manually going through code changing the bracketing to their preference. I suggested automating the build process on check in and was met with such negativity I've pretty much given up suggesting any improvements in process. Sorry - feeling particularly cynical today!
MVVM # - I did it My Way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
Well, it depends really. Tools like never really work in every case. It really depends on case to case. Sometimes it's nice to have it separated, makes it more readable. Sometimes you have some inline stuff, thaat if you separated in the same way would just confuse you.
-
Why would you even wanto to beautify legacy code? It's legacy code. Leave it be, or rewrite it. I don't beautify code. Code does not have to be beautifull. It has to work, and has to be readable. Make up and earrings will not make your code better. It will just distract you, and fool you into thinking it's perfect, untill it opens "it's" mouth and all that comes out is crap. Focus on better code, make it readable, add comments when needed. And structure it in the way you think it makes it easier to read and follow the logic behind it, but do it yourself and don't rely on tools. Who knows, maybe you'll catch a bug or two, or even identify flaws in the logic side.
You don't know what a code beautifier is or what it does, do you? That's fine, of course. Moving on...
-
You don't know what a code beautifier is or what it does, do you? That's fine, of course. Moving on...
-
Yes I do. Which is why I say that you should not rely on those. When you don't have a code beautifier on hand, and not even able to get one, what are you gonna do?
This is insane. I no longer recognize CP.
-
This is insane. I no longer recognize CP.
-
It sounded like you were saying that there's something wrong with him using a program to format his code instead of doing it himself manually. Is that the humor you say he is missing?
The difficult we do right away... ...the impossible takes slightly longer.
I didn't say there was anything wrong with using a program to format reams of legacy code. He never mentioned legacy code so I attempted a somewhat amusing response, albeit you can use your brain to decide how to format your own code.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. Those who seek perfection will only find imperfection nils illegitimus carborundum me, me, me me, in pictures
-
What disagreement? You are delusional. I am just looking for a tool and two fools are going on on tangents no one gives a crap about.
