133 reputation
4
bio website
location Wichita, KS
age
visits member for 1 year, 7 months
seen Nov 12 at 20:59

Nov
25
comment When to use (Or not) C# myVariable { set; get; }
Thanks @MattD I like the summary of "Boilerplate" vs clean and that's really what I needed to know.
Nov
25
accepted When to use (Or not) C# myVariable { set; get; }
Nov
25
comment When to use (Or not) C# myVariable { set; get; }
@CodeART It is a general question on when which approaches are best or if there is a difference.
Nov
25
asked When to use (Or not) C# myVariable { set; get; }
Nov
21
awarded  Editor
Nov
21
revised Visual Studio versions and Team Etiquette
added 262 characters in body
Nov
21
awarded  Scholar
Nov
21
accepted Visual Studio versions and Team Etiquette
Nov
21
comment Visual Studio versions and Team Etiquette
@Ramhound I specifically said I do not believe he considered it, not that he did it on purpose. More importantly though, is this specific scenario only made me aware of the etiquette of something like this.
Nov
21
comment Visual Studio versions and Team Etiquette
I have 2010, 2012 and 2013. I prefer 2010 although there is no reason for the project to be on one or another. I just prefer the colors, icons and navigation of 2010. I realize not all developers have access to pro for all 3 though... If this effects your thought process at all
Nov
21
comment Visual Studio versions and Team Etiquette
@Ozz Good points, I know the plan is to add functionality and then fork back up to the source. I suppose I could diff the changes into the 2010 files, but it adds work for at least me this router.
Nov
21
comment Visual Studio versions and Team Etiquette
@DaveHillier Thanks, I am aware that 2013 is the latest, but the question was meant to be a little more in general about general etiquette, and 2013 does come to play there as someone could update the solution again to 2013 at any time.
Nov
21
awarded  Student
Nov
21
asked Visual Studio versions and Team Etiquette
May
20
awarded  Supporter