As a workaround, you can run 'Restore NuGet packages' manually on the solution. We use SWEA, so after the solution opened, SWEA starts to analyze the files - and shows lots of unknown symbols. The message is given bellow (: Object reference not set to an instance of an object): I'm tried to change nUnit Runner in reshrper options, tried to disable option 'Shadow-copy assemblies being tested' but that doesn't help. I need the productivity gains of R# that so far DevExpress has not reached IMO. There is a minor timing issue when starting VS2022 (Preview 3.1) and opening the first solution. But I am rooting for DevExpress to pick it up … they certainly have some nice eye candy in their app … and they’re plug in support is superior to R#. Until it gets all the features of R# with the code analysis, pre-compile, etc to the level that R# does, I am sticking with R#. 15 258 downloads Free ReCommended Extension for ReSharper The ReCommended Extension for ReSharper augments the sophisticated code analysis engine by providing more rules not (yet) available from JetBrains. I try DevExpress’s tools about once a year hoping it will challenge R# for me, but it just has not given me reason to replace R# yet. I do a lot of Silverlight and WPF programming so its great to have their refactorings in place with XAML in addition to the VS intellisense. One of my favorite features is the XAML based refactoring. They state that they improved ReSharper to work better with Visual Studio 2008 SP 1, they improved ReSharper's performance, and they added better ASP.NET support.
You can download the new version, ReSharper 4.1, from here. The folks at JetBrains released a new version of ReSharper today.
0 kommentar(er)
