ReSharper Support | JetBrains

Victor Kropp

Total activity 245
Last activity January 17, 2016 22:30
Member since May 06, 2009 13:23
Following 0 users
Followed by 0 users
Votes 0
Subscriptions 95

Created January 27, 2011 09:10

CodedUI tests are not supported in ReSharper 5.Workaround is to copy 4 assemblies namely: Microsoft.VisualStudio.QualityTools.CodedUITestFramework.dll Microsoft.VisualStudio.TestTools.UITest.Common...
- 0 votes
Created February 20, 2014 19:33

Hi John,I've created an issue in our bugtracker http://youtrack.jetbrains.com/issue/RSRP-405630 for this. It's scheduled to be fixed in upcoming 8.2 release.
- 0 votes
Created April 23, 2014 17:33

Hi Eric,this issue is fixed in upcoming 8.2.1 update.
- 0 votes
Created April 23, 2014 17:32

Hi Juan,this is a known issue. Please refer to this request in our tracker: http://youtrack.jetbrains.com/issue/RSRP-334306
- 0 votes
Created April 04, 2014 12:39

Hi Kevin,you may control the order of references in your test file. Just put all///<reference path="~/scripts/jasmine/tests/BaseReferences.js"/>///<reference path="~/scripts/document/move.js"/>befo...
- 0 votes
Created April 04, 2014 15:10

Reference to jasmine.js is not required, this is correct. But if you reference it manually, than you may change the order of references, e. g. put jasmine.js. By default, it is referenced first.
- 0 votes
Created August 14, 2014 16:11

Hi Mike,I created an issue for this: http://youtrack.jetbrains.com/issue/RSRP-421045Please follow it.
- 0 votes
Created August 11, 2014 17:07

Search with Pattern is designed to work with pure code tree ignoring all whitespace, comments, etc. So we don't have any plans to support matching #region directives. Sorry for that.
- 0 votes
Created June 30, 2014 17:00

Looks like the problem is that jasmine.js is referenced before other dependencies.Could you please try to add jasmine.js to your project and than add reference to it after all other references in t...
- 0 votes
Created June 18, 2014 13:53

Hi, I tried solution you attached. Everything works as expected, I can explain the behaviour you see:First of all, NUnit tests are not affected at all, they all are loaded and runnable.MSTest howev...
- 0 votes