ReSharper Ultimate 2016.3 EAP 7

10 Responses to ReSharper Ultimate 2016.3 EAP 7

1. 

   tobi says:

   November 8, 2016

   Can you post sample code for the dispose pattern? There are a few variants. The Microsoft endorsed pattern with the virtual Dispose(bool) method often is not the right choice.

   • 

     Dmitry Matveev says:

     November 8, 2016

     Hello,
     ReSharper will generate both Dispose(bool) and Dispose(). So if you have a single filed IDisposable Logger in your class, the generated dispose pattern will look like this:

     class MyClass : IDisposable
{
private IDisposable Logger;
protected virtual void Dispose(bool disposing)
{
if (disposing)
{
Logger?.Dispose();
}
}
public void Dispose()
{
Dispose(true);
}
}


     If you have unmanaged members, ReSharper will additionally generate a destructor:

     class MyClass : IDisposable
{
private IDisposable Logger;
private bool _disposed;
protected virtual void Dispose(bool disposing)
{
if (_disposed) return;
if (disposing)
{
Logger?.Dispose();
}
// TODO free unmanaged resources here
_disposed = true;
}
public void Dispose()
{
Dispose(true);
GC.SuppressFinalize(this);
}
~MyClass()
{
Dispose(false);
}
}

     • 

       tobi says:

       November 8, 2016

       Alright, the virtual thing is only needed in case of inheritance. 99% of all classes are not inherited from, yet are not sealed (out of habit/ignorance). It’s not a good idea to include all this noise. In your example, it triples the line count.

       This should be default-off and a check box in the generate dialog. What’s your opinion? Could you please register this as a feature request?

       • 

         Andrew Karpov says:

         November 9, 2016

         https://youtrack.jetbrains.com/issue/RSRP-461649

2. 

   Chris Owens says:

   November 8, 2016

   Please start giving a longer expiration on the eap builds. 2016.3 eap 6 & 7 both have a significant performance degradation to the point of dramatically slowing my typing down or making me wait after clicking things.

   I tried to uninstall 7 and revert to 5 where I didn’t notice as much of a delay, but 5 is expired already and unusable – so I either have to give up on eap releases until you fix the performance hit, or revert back to the non-eap release just to be able to work at all.

   • 

     Mikhail Senkov says:

     November 9, 2016

     Could you please help us investigate performance issues with eap6-7? It will be great if you collect performance snapshot as described here https://confluence.jetbrains.com/display/ReSharper/ReSharper+Profiling+Instructions and create an issue in our tracker https://youtrack.jetbrains.com/issues/RSRP

3. Dew Dump - November 8, 2016 (#2362) - Morning Dew says:

   November 8, 2016

   […] ReSharper Ultimate 2016.3 EAP 7 (Dmitry Matveev) […]

4. Auf dem Weg zu ReSharper Ultimate 2016.3 - entwickler.de says:

   November 9, 2016

   […] gewohnt finden sich alle Neuerungen und Änderungen ausführlich aufbereitet im JetBrains-Blog; dort steht ReSharper Ultimate 2016.3 EAP 7 auch zum Download […]

5. 

   Dissapointed resharper user :( says:

   November 10, 2016

   A disappointing issue.
   When a “run all tests” command is chosen from a solution level tree – execution of tests is fast.
   But when one test or project is chosen from a window “unit test session”.
   An Execution is very, very slow. One test is longer than one minute for no reason.
   In this case, testing with Resharper are almost unusable.

   • 

     Dmitry Matveev says:

     November 16, 2016

     We’ll be happy to investigate that if you could help us by taking a performance snapshot of your actions. Alternatively, you could log an issue and attach a sample solution where this behavior could be reproduced.