Exceptional for 2016.3 about exceptionalresharper HOT 13 CLOSED

v0.8.0.0 is now pushed to the extension gallery. Please check if everything works for you...

from exceptionalresharper.

I think this shouldnt be a big effort ..

from exceptionalresharper.

I also failed to update dependencies from nuge.org. It seems that some dependency is really missing. I reported an issue on Youtrack and ask you guys and gals to vote:
https://youtrack.jetbrains.com/issue/RSRP-462458

from exceptionalresharper.

Same problem! Please release 2016.3 compatible version.

from exceptionalresharper.

Is there any estimates for the 2016.3 compatible plugin? I might downgrade the R# otherwise

from exceptionalresharper.

I think this shouldnt be a big effort ..

Then fork it and try it. I tried for a couple of hours and I couldn't get the Nuget dependencies right. Your turn, because that's how open source works.

Ahem: #35

OH LOL at me with only 1 coffee in me. Sorry @RSuter 🥇

from exceptionalresharper.

eb9f977

from exceptionalresharper.

It seems that we cannot release a new version for R# 2016.3 because of this problem... @pedromagueija and me are trying to create the project but we cannot upgrade the NuGet packages.

@citizenmatt: Can you have a look at this?

from exceptionalresharper.

Thanks for your efforts so far, guys! The Youtrack issue submitted by @borismod has been bumped up to Critical by Jetbrains, so hopefully they'll sort it out soon

from exceptionalresharper.

Just seen this, replied on the issue. I think it's because you're a .net 4.0 class library, and you now need to be .net 4.5. Update framework version, reinstall existing packages, then update to latest SDK. That should do it.

from exceptionalresharper.

@citizenmatt Hi Matt,
I've finally installed the new SDK and Wave, but now I'm having an issue with API changes.

• ICatchVariableDeclaration no longer has a SetDeclaredTypeUsage method
• IReferenceExpressionReference no longer has a CurrentResolveResult property
• ICatchClause no longer contains has a ConditionClause property

Are these documented somewhere that I can use to adjust the code to the new API?
As always, thanks for your help

from exceptionalresharper.

@pedromagueija about IReferenceExpressionReference.CurrentResolveResult - you should never use it, it's internal property. Invoke Resolve() to get result.

from exceptionalresharper.

@derigel23 Thanks for the tip. I've replaced the call to CurrentResolveResult with Resolve();

from exceptionalresharper.