John Dziurlaj

Supress Code Analysis Warnings for Generated Code

Generated code usually cannot be easily changed to conform to style guidelines set by JustCode Code Analysis. Thus code with the block below should not participate in Code Analysis Warning Generation.

//------------------------------------------------------------------------------
// <auto-generated>
// This code was generated by a tool.
// Runtime Version:4.0.30319.18408
//
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------
Idea by John Dziurlaj Status: New Comments: 0 Last update: 2014-08-28T14:43:29 by John Dziurlaj
0
Stuart Hemming

Pause analysis during compile

It would be nice if there were an option to pause anaysis until a build is completed.
Feature Request by Stuart Hemming Status: Reviewed Comments: 1 Last update: 2014-08-15T13:44:16 by Patrick Gendron
0
Eric Boumendil

Warning rule for "async void" method signature

It is widely recognized that we should almost never write a method signature like "async void MethodName()". The single exception I know to this rule is event handlers.
It would be nice if JustCode could take care of this.
Idea by Eric Boumendil Status: New Comments: 0 Last update: 2014-08-08T12:47:53 by Eric Boumendil
0
Brandon Campea

JustCode thinks string.Format() has unused variables when using a const for input

In C#, using string.Format() with a const string as the input for composite formatting will cause JustCode to grey-out the rest of the input parameters as 'unused arguments'. It does not seem to be able to "see inside" the const string to determine how many formatting anchors are present to check that the parameter count matches.

Please see the attached screenshots for examples.
Problem by Brandon Campea Status: New Comments: 1 Attachments: 2 Last update: 2014-08-07T15:44:04 by Vladimir Dragoev
0
Eric Boumendil

"Fix: Add Stubs for required members" with IDisposable: follow IDisposable pattern

I use a lot IDisposable. I would be nice if JustCode could follow IDisposable pattern (http://msdn.microsoft.com/en-us/library/b1yfkh5e(v=vs.110).aspx) when I press Alt+Enter on my class to prepare proper implementation of this special interface.
Feature Request by Eric Boumendil Status: New Comments: 0 Last update: 2014-08-07T14:26:24 by Eric Boumendil
0
Josh Schlesinger

Adjust namespaces on entire project

A common scenario I have is to move class files from another project into a new one. After doing this I have many class files with namespaces that do not match the project root/folder structure. I would like a way to have all namespaces adjusted for an entire project. Currently the only way to do this now is to go to each file individually and use the "Move type to namespace" function.
Feature Request by Josh Schlesinger Status: Reviewed Comments: 1 Last update: 2014-08-06T17:26:55 by Elijah Joel
0
Walden Leverich

Decompile Reference Assemblies just like non-reference assemblies on F12

Given that JustDecompile handles reference assemblies just fine, please enhance the decompilation in JustCode to decompile reference assemblies. Many times I am looking for a decompliation of a BCL method on an F12 and it takes me out of a nice development flow to have to go open JustDecompile and load the assembly and navigate to the right method when I was already there in the source editor.
Feature Request by Walden Leverich Status: New Comments: 0 Last update: 2014-07-24T15:11:01 by Walden Leverich
0
Ivan Spasov

Allow having more that one enum type inside Enums file

Do not show a warning for type does not matching file name if the type is an enum inside Enums file
Feature Request by Ivan Spasov Status: New Comments: 0 Last update: 2014-07-21T07:59:11 by Ivan Spasov
0
Ivan Spasov

Add abilility to convert fully quallified type to simple type

Consider the following example:
using MyNamespace;

class MyType
{
private MyNamespace.MyType _instance;
}

JustCode could provide a conversion (and a warning) from "private MyNamespace.MyType _instance;" to "private MyType _instance;"
Feature Request by Ivan Spasov Status: New Comments: 0 Last update: 2014-07-21T07:47:40 by Ivan Spasov
0
Coskun SUNALI

Ignore All Warnings in files in the same folder

Long story short; decided to work with a 3rd party JS library in a web project and there were tens of JS files provided by the 3rd party vendor.

However, as you might have already imagine, the syntax of the JS library's code itself does not match my settings in JustCode so they seems to be listed as "warnings". So far so good because this is one thing that JustCode really does well. However, I - naturally - don't want to change a 3rd party's code and just ignore all JS files and their code syntax by JustCode.

I think a further option under the "Ignore All Warnings" and "Ignore All Errors" options would be great. What comes to my mind is something like "Ignore All Warnings in files in the same folder". So, once that I click it, all other JS files would ignore all the warnings they have in themselves.

I don't think the same is necessary for "errors". If there is an error, someone has to take care of it, right. But if it is just a warning and if I don't care about the 3rd party's syntax problems, the option I mention could be a great time saver.

Trust me I had to go through 30-40 files, find a warning on each and say "ignore warnings on this file".
Feature Request by Coskun SUNALI Status: Reviewed Comments: 1 Last update: 2014-07-04T12:46:10 by Justin Buchanan
0
Displaying items 1 - 10 of 181