1-10 of 194 < Previous ... Next >
Discussions for StyleCop
Latest post:
Fri
11:13 PM
3 Posts
First post: papadi wrote: Hi, in the following block rule SA1122 does not fire as expected. Can you please confirm if this is a bug? switch (commandLineArguments.Command) { ...
Latest post: 280Z28 wrote: Case statements must have a constant expression. The string.Empty field is a static readonly (non-const) member, so it's not allowed there.
Jump to: First Post    |Latest Post
Latest post:
Fri
10:20 PM
13 Posts
First post: serega wrote: Fix the cause not the symptoms. The tool is just not flexible enough. The rules must be customizable. For example, DoNotUseTabs should be IdentationOptions with settings like InsertSp...
Latest post: 280Z28 wrote: Here are the problems I have currently: I'm implementing a documented API, and some of the publicly visible items in the API violate the StyleCop rules. There's nothing I can do about ...
Jump to: First Post    |Latest Post
Latest post:
Fri
7:07 AM
6 Posts
First post: thomykay wrote: A lot of rules (spacing, empty lines, comments spacing etc.) could be fixed automatically with a code formatter. Would be good to have that global for files and a 'Fix this' menu item in ...
Latest post: olivier34 wrote: I do think that retro fit files tasks could be made with StyleFix, no ? http://stylefix.codeplex.com Hasn't you tested this tool? Regards, Olivier.
Jump to: First Post    |Latest Post
Latest post:
Jun 30
7:00 AM
4 Posts
First post: davedev wrote: SA1513: Statements or elements wrapped in curly brackets must be followed by a blank line. except for a get property accessor, right?
Latest post: Gebb wrote: Documentation to SA1513 seems to be misleading.
Jump to: First Post    |Latest Post
Latest post:
Jun 28
10:16 PM
1 Post
First post: 280Z28 wrote: Currently, the context menu for a folder in a C# project in Visual Studio shows "Run StyleCop" as the first item (in its own group). For anyone used to using this context menu to add item...
Jump to: First Post
Latest post:
Jun 26
12:33 PM
1 Post
First post: dan_thomas_ wrote: REMOVED
Jump to: First Post
Latest post:
Jun 25
10:09 PM
1 Post
First post: 280Z28 wrote: I propose adding the following rules concerning operators as static members of a class: 1. Operator methods should be placed after static non-operator methods. 2. Conversion operators sh...
Jump to: First Post
Latest post:
Jun 25
9:35 PM
1 Post
First post: Underdeveloper wrote: Using StyleCop 4.0.20.4 via its MSBuild task to analyze code like Dictionary<string, object> domainArgs = new Dictionary<string, object>() { {ass...
Jump to: First Post
Latest post:
Jun 25
5:06 AM
3 Posts
First post: peli wrote: I'm looking for the ways to disable StyleCop on particular files. Our tools generate a file name yyy.Designer.cs but StyleCop still decides to analyse it so there might be more magic to t...
Latest post: JohnBates wrote: Add a header like this at the very top of each generated file (like the ASP.NET designer.cs files): //------------------------------------------------------------------------------ // <a...
Jump to: First Post    |Latest Post
Latest post:
Jun 24
3:53 PM
23 Posts
First post: Johnnylightbulb wrote: Among the useful messages Source Analysis for C# reports I see many instances of: Tabs are not allowed. Use spaces instead. I understand this tool is very rigid, as is the entire point o...
Latest post: hfrmobile wrote: Tabs are not bad! Tabs (default setting) are OK for indenting code blocks. The use spaces instead (two, four?) is horror for me .... Pros for tabs: Each developer has the choice f...
Jump to: First Post    |Latest Post

Configure View

Sorted by Latest post
Search
Filter
(by tag)
All tags
1-10 of 194 < Previous 1 2 3 4 5 6 7 8 9 10 ... Next >
Updating...
Page view tracker