resharper

I find myself using Resharper's "convert to auto property" refactoring a lot to remove pre C# 3.0 boilerplate code. Is there a way I can apply this to all properties in a single class at once? The ReSharper can do this: Options -> Code Cleanup -> Use auto-property, if possible Run code cleanup for the class - and you should be done. Tanascius has the right answer, though you can tweak that a little bit by creating your own custom Code Cleanup script that would ONLY include the "Use auto-property if possible" refactoring. That would probably be preferable if you didn't want the rest of the

I find myself using Resharper's "convert to auto property" refactoring a lot to remove pre C# 3.0 boilerplate code. Is there a way I can apply this to all properties in a single class at once? The ReSharper can do this: Options -> Code Cleanup -> Use auto-property, if possible Run code cleanup for the class - and you should be done. Tanascius has the right answer, though you can tweak that a little bit by creating your own custom Code Cleanup script that would ONLY include the "Use auto-property if possible" refactoring. That would probably be preferable if you didn't want the rest of the

I currently use Chutzpah to run and debug Jasmine Unit tests that include AMD/require.js modules. I would like switch to the test runner of Resharper 2017. However, Resharper does not seem to fully support Jasmine Unit Tests? A. Example jasmine test: /// <reference path="../../bower_components/requirejs/require.js" /> /// <reference path="../../bower_components/jasmine-core/lib/jasmine-core/jasmine.js" /> describe('dummy example test', function() { it("should return bar", function () { expect(true).toEqual(true); }); }); The Test can be run with Resharper but the Debugging option is disabled:

I use ReSharper's code cleanup all the time, but sometimes I have code formatted in a way that makes it easier to read than ReSharper's formatter makes it. Is there a way to mark part of your file with comments or something to make it skip formatting that portion. (I'm not talking about inspections, I know how to have ReSharper ignore regions for inspections) I had a discussion with Resharper support about this, their answer: Thank you very much for this information! We will discuss if we can support such formatting style in one of the future versions. Probably not, but you can try writing

I'm writing unit tests for an MVC web app, and I've been getting null reference exceptions because the mocked-up test objects are only partly initialized. I know which line is throwing the exceptions, and it looks something like this: return Supervisor.RegistrationInformation.Registrations .Any(r => r.RegistrationCountry.IsUSAOrCandada() && (!DatesWorked.Start.HasValue || r.RegistrationDate <= DatesWorked.Start.Value) && (!DatesWorked.End.HasValue || r.RegistrationExpirationDate >= DatesWorked.End.Value) && //... There are a lot of references in there, and any of them could be the problem.

I have a class where FileHelpers is dependent on the field order in this class file. If the class file ever gets a code clean up run against it that will cause the fields to be sorted alphabetically and invisibly ruin my class. Since I would like to avoid this from ever accidentally occuring, is there a resharper comment directive to disable code cleanup for a class? Romain Verdier You can customize the default member layout XML file and specify a pattern you want to ignore during the "reorder members" step of a code cleanup. Have a look at the Type Member Layout section under the Resharper

I like how String.Format uses arguments to inject variables in to the string it is formatting. This is called Composite Formating and is discussed by MSDN here . I want this functionality with my logging facade: string foo = "fancy"; string bar = "message"; log.Debug("My {0} log {1}.", foo, bar) My ILoggerFacade has the following method signature: void Debug<T>(T message, params Object[] args); And, I know I can implement this quite simply: ILog m_Log = \\some logging implementation public void Debug<T>(T message, params Object[] args) { m_Log.Debug(String.Format(message, args)); } However, in