-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update ReSharper integration to support v6.1 RTM #297
Conversation
per discussion at http://groups.google.com/group/openwrap-devel/browse_thread/thread/9ba81705260e1645 * Add same DLLs (v6.1.37.86) as v6 * Introduce new v610 project which defines v610 compile-constant * Adjust existing v600 checks to include v610 case There's a compilation error with ResharperTests5.cs relating to turning on solution-wide analysis; that property no-longer exists in the 6.1 API I guess.
The issue probably comes from a missing compilation variable check on Resharper5Tests.cs line 63 that's missing from this. |
As in, a new one that should be added? I noticed that right after I pushed, and pushed again. It isn't that. |
No, look at the file, there's already one that checks for v600 and doesnt have a check for v610 |
Ping. Adding the check for v610 did not yield green. |
This gives us compilation, and passing 'Tests', but various failures in 'Tests.VisualStudio'
Regarding ResharperTests5.cs: what you need to do is set the |
Just to clarify a little bit, what this implies is that before doing a time measurement on SWA you would have to enable it with code similar to the following:
|
Would you mind also fully-qualifying the types? OpenWrap has a set of redirects so that the same code can service multiple ReSharper versions. Thanks! |
Please ignore the deprecation warning for now. As for the types mentioned above, they are:
The |
In Oh - note the assembly namespace-alias going on in the reference - JB R# assemblies are referenced via |
The assembly you're looking for is |
I also couldn't find |
I suggest you make an empty plug-in project using the SDK and then use Ctrl+T or Ctrl+Shift+T to locate the types and references that are needed. The best practice for writing R# plugins is to reference every single assembly that R# comes with. This is precisely what the SDK does with its |
Ah, yes - that makes it easier. When I'm done I can analyse references and remove unused ones, too. Thanks :-) |
Yep, that should help as well. Just keep in mind that removing unused references for SDK projects doesn't actually do anything :) |
So Also, |
…teruk (thanks!) * figure out which assemblies the required types live in, and reference them. * copy and paste example from @dnesteruk into #if v610 block. Compilation achieved; now for tests...
@serialseb At this point, I get:
This is the same as when I checkout 19d2843 (the revision that I forked from), when running with ReSharper 6.1 (I haven't run these with ReSharper 6.0). How to proceed...? |
Just issue the pull requests. The VS tests are notirously unreliable and slow, until I automate them we can live with them breaking for now. Seb From: Peter Mounce [reply@reply.github.com] @serialseb At this point, I get:
This is the same as when I checkout 19d2843 (the revision that I forked from), when running with ReSharper 6.1 (I haven't run these with ReSharper 6.0). How to proceed...? Reply to this email directly or view it on GitHub: |
(so it has a different Guid; it started life as a copy of .600) add similar references as v600 integration, but for v610. Now compilation fails again, saying `SiteManager` class is defined in multiple assemblies, which I don't know how to debug.
And now, compilation. The VS tests still fail (the output window pane is null during How do I test this in anger, in a solution that isn't OpenWrap? |
@serialseb From tweet:
It Works On My Machine! |
I got a yellow line during the update-wrap call; here's the output: That outputs:
|
per discussion at http://groups.google.com/group/openwrap-devel/browse_thread/thread/9ba81705260e1645 + what seemed necessary code-change-wise.
There's a compilation error with ResharperTests5.cs relating to turning on
solution-wide analysis; that property no-longer exists in the 6.1 API I guess.