And the WiX toolset is the same way. I just need to rewrite the document.
Note: if you find inconsistencies in the code, we should fix them. My hope
is that overall the code base is extremely consistent so the answer is
always simple: "Make the code you add look like the code around you."
On Sun
Python eliminates a lot of the arguments by having the style guide be a part of
the specification. There's not much argument about max characters per line when
it's in pep8.
Bruce
On 19 May 2013, at 16:32, Bob Arnson wrote:
> On 18-May-13 17:25, Rob Mensching wrote:
>> We tried StyleCop for a
On 18-May-13 17:25, Rob Mensching wrote:
> We tried StyleCop for a while and found it was more annoying than not
> since we didn't use all of it's rules. However, that was a long time
> ago so maybe it is better.
Microsoft tossed StyleCop over the wall; it looks like there's a lone
dev working o
We do. Most of the code is very consistent and you can see the rules by
following what exists. There are some small things that are "in between"
and old style and a new style. If you see cases where it is not clear,
please ask. We should general fix it if it's wrong.
Plus: Mike Carlson has shown
Do we currently have any guidelines / rules / standards for code formatting
(for both the C# and C++)?
For C#, we have StyleCop as an option for ensuring the code stays in line
(there are even references to it in our existing targets). Do we have any
guides for enabling StyleCop and can we
