Comments on: ReSharper 6.1: The Finish Line

By: Justin

Justin — Tue, 20 Dec 2011 18:05:43 +0000

Hmm, the Fixes link for nightly build 30 lists those bugs as fixed in that build.

By: Jura Gorohovsky

Jura Gorohovsky — Tue, 20 Dec 2011 17:42:02 +0000

@Justin We’re past the 6.1 inclusion deadline. The two fixes will apparently be available in the next ReSharper update after 6.1.

By: Justin

Justin — Tue, 20 Dec 2011 17:31:27 +0000

RSRP-286341 and RSRP-286345 both show fixed in 6.5 but the issues persist in the latest 6.1 nightly build. Will the fixes for those bugs get merged into the 6.1 branch before 6.1 is released?

By: Jura Gorohovsky

Jura Gorohovsky — Tue, 20 Dec 2011 11:37:06 +0000

@Phil
Sorry but we don’t currently support custom build actions at all, meaning that RSRP-284665 can’t be implemented right now.

By: Phil

Phil — Tue, 20 Dec 2011 08:06:49 +0000

RSRP-284665 is a show stopper for us. Any chance this can be fixed?
RSRP-279821 is also a problem.

By: orangy

orangy — Fri, 16 Dec 2011 20:56:15 +0000

@Mark, of course we have plans to support WinRT. The problem is there is no build suitable for integration work. Developer Preview has some critical API missing (or non-functional), so we are waiting for something to work with.

By: Jura Gorohovsky

Jura Gorohovsky — Fri, 16 Dec 2011 20:56:11 +0000

@Mark
Absolutely. Not in version 6 though.

By: Mark Monster

Mark Monster — Fri, 16 Dec 2011 19:35:17 +0000

Are you guys at Jetbrains planning to support WinRT?

By: Jura Gorohovsky

Jura Gorohovsky — Thu, 15 Dec 2011 16:20:04 +0000

@Joe No that means that this particular change was initially committed to trunk before being merged to the 6.1 branch

By: Joe White

Joe White — Thu, 15 Dec 2011 12:29:46 +0000

@Jura: that root exception has a “Fixed in build” of 6.5.1.431. Does that mean it won’t actually be fixed in the 6.1 release, and we’ll be stuck with background analysis occasionally seizing up (now with no warning) until VS is restarted?