Visual Studio 2013 and ReSharper 8 support

Oct 18, 2013 at 10:15 PM
Visual studio 2013 is (unexpectedly) finally released. We're looking forward to adopting it as soon as Stylecop is supported. Do you have a release planned?
Great project, wouldn't be without it!
Oct 19, 2013 at 12:14 AM
We can't live without stylecop either, have to add a +1 on this one.
Oct 20, 2013 at 7:19 AM
+1. I love to start fresh with each major release.
Oct 20, 2013 at 11:45 AM
+1. Doesn't seem like a lot has changed in the Visual Studio SDK so probably this should be up to a simple recompiling with updated references
Oct 21, 2013 at 8:36 AM
+1. We want to update to VS 2013 too.
Oct 21, 2013 at 11:29 AM
+1. We are using the unreleased build. Any views on the release date of Stylecop fro VS2013?
Oct 23, 2013 at 7:27 AM
+1, I am sure Andy knows we'er all champing at the bit, but here's some more encouragement...
And again, if you want a pizza let me have your paypal email.
Nov 3, 2013 at 2:29 PM
Not to be a nag, but is StyleCop going to survive into VS 2013 and beyond? There's been no indication one way or the other, and that note on the front page doesn't bode particularly well.
Coordinator
Nov 3, 2013 at 2:32 PM
Yes it will.


~Andy.

Nov 3, 2013 at 4:27 PM
Andy,
Any word on my pull request for supporting VS2013? I haven't seen a response to either of my messages to you. I've never used messaging on CodePlex, though, so I guess I could be missing something?
Coordinator
Nov 3, 2013 at 4:49 PM
Hi

I'm back in the uk next week and hoping to sort it then


~Andy.

Nov 4, 2013 at 1:45 PM
Thank you, Andy, great to hear. :) We all really appreciate your work -- VS feels naked without StyleCop!
Nov 5, 2013 at 12:11 PM
Thanks csdahlberg for the updated msi (it is in the VS 2013 Preview issue, for those that missed as I did a week ago). Also thanks to you andyr for this great tool. Hoping to see this merged.
Nov 7, 2013 at 12:49 PM
Thanks, Andy! You definitely have my gratitude for all that you are doing for FREE. :)

Looking forward to the new 'official' release.
Nov 12, 2013 at 12:01 AM
I've been following StyleCop since it was an internal project at Microsoft right after NGWS became .NET :)

The only problem is - everybody else I work with hates it, even though they adopt the style. I can't live with out it.

The problem with it is I expect that it is a Visual Studio Add-In. It's highly useful the way it is - especially being able to click on a line in the Error output to go exactly to where the problem is, but it's not worth the hassle of being an Add-In.

I'll grab the source and try to make a stylecop.exe command line tool that dumps the output to stdout. Maybe I can wedge it back in VStudio somehow.

It's the rules that's important, not the U/I - and I'll be damned if I'll switch to some commercial tool to do this. The benefit of Stylecop has always been "1 way to do it." That's what has to survive and thrive.
Nov 12, 2013 at 12:13 AM
@TomBallard - you might be interested in this: http://sourceforge.net/projects/stylecopcmd/
Nov 12, 2013 at 1:24 AM
TomBallard wrote:
The problem with it is I expect that it is a Visual Studio Add-In. It's highly useful the way it is - especially being able to click on a line in the Error output to go exactly to where the problem is, but it's not worth the hassle of being an Add-In.
I'm not sure I understand that statement. You expect it to be a Visual Studio Add-In, but it's not worth the hassle of being an Add-In?
Nov 13, 2013 at 9:54 AM
andyr wrote:
Hi I'm back in the uk next week and hoping to sort it then ~Andy.
Andy, can you give us an estimate when code will be merged? Today is the launch of VS 2013, but we still do not have StyleCop build officially supporting it...
Nov 14, 2013 at 4:24 AM
TomBallard wrote:
I'll grab the source and try to make a stylecop.exe command line tool that dumps the output to stdout. Maybe I can wedge it back in VStudio somehow.
Hi Tom,
I am not sure what you intend to achieve with this strategy, I suspect it's flawed?

To me the most useful aspect of stylecop is actually not the "cop" part iteself, but rather the context fixes made available by the resharper plugin that allows our team to reformat large amounts of code very quickly.
It saves so much time, that I suspect we would revisit bothering with a lot of the style rules if it were not for the plugin.

It's a really great product
Nov 14, 2013 at 7:05 AM
+1
Nov 14, 2013 at 3:19 PM
@jimmymain: This is exactly how I use it too. Ability to use R# "Clean up Code" command use StyleCop to clean up. It's become such a habit that I find myself keep hitting CTRL+E+C in VS.Net 2013 to no avail. I'd go as far to say, I won't buy / renew R# licenses but for StyleCop.
Nov 15, 2013 at 1:09 AM
Edited Nov 15, 2013 at 1:28 AM
Nah, not interested. (I hope my humor comes through, I may sound cranky but I think in the stylecop discussion forum the joke should go over.)

I only like the COP part. I love the militant "I don't care, just do it this way" attitude of stylecop. It's so great to do a personality removal of other folks's code, while smart people can insert their own "code smells" and be stylecop clean. I never ever uncheck any of the boxes to ignore any rules, and at my place we frown upon suppressing the FxCop violations.

The funny part about dinking with the source is it is full of such suppressions even though it's stylecop clean. I've got it compiling in an alien environment (I've faked CodeProject and such, I think I need to pull in more of CodeReader however), but it's not running yet.

A commercial thing like Resharper would inevitably bend to the "will of the market" and deemphasize the rules that the "market" doesn't like.

I had this psycho guy I worked with before who just went la la la space new line space five lines between this code block, seven between this one, and he got highly insulted that I wanted to normalize them.

I could really care less about some "commercial hanger on to Microsoft", staffing a few ex 'softies, who's business model is to remora-like follow on to whatever Microsoft released last. It's why we don't buy components, it's why we still use the free Reflector, and it's why I like the COP part of stylecop.

It's not really that hard to manually make your code stylecop clean, although after inspecting the code closely, what you are describing Resharper can do, will never happen with the current stylecop codebase. It's an awesome character-level C# static source analysis tool though..

I'm glad I have the source so that apparently when this project dies for good, at least I can still use it. I was the only one who ever used it anyway.

Hope you all have a sense of humor. I expect there are a few Resharper devs and fans who disagree. You can have my stylecop when you pry it from my cold fingers :)
Nov 15, 2013 at 1:24 AM
Image
Nov 15, 2013 at 1:41 AM
Oh yeah, I expect Andy is having a really hard time due to the architectural changes in VS2013 - no more macros at all :). it's hard to be an add-in these days, and Andy probably doesn't feel like doing the work to make it a proper VSIX.

After looking at the source I can't say I blame him :)
Nov 15, 2013 at 2:25 PM
FYI, I installed csdahlberg's preview version (4.7.46.9999) from September and it works great with VS2013 RTM ! Thanks, Chris.
Nov 17, 2013 at 3:08 AM
Edited Nov 17, 2013 at 3:27 AM
Is there a way to compile it without having Resharper installed? I got the csdahlberg fork (commit 09e64cbb9238 from 9/29) and edited tools\scripts\Environment.cmd to change Visual Studio 10 path to Visual Studio 12.0, but OfficialBuild.cmd command complains that it can't proceed unless Resharper is installed.

This is a clean Win7 box w/ VS2013 ultimate installed, nothing else.

Thanks!
Coordinator
Nov 17, 2013 at 7:46 AM
The main branch will have support for vs2013 rtm and the latest ReSharper next week.


~Andy.

Nov 17, 2013 at 3:50 PM
Tom,

I'm not sure, as I haven't tried building it myself. However, I uninstalled ReSharper and StyleCop 4.7.46.0, installed the build of StyleCop that Chris posted in his SkyDrive account (4.7.46.9999, see below), and it worked fine. So, I don't know what other changes Chris made to that build, but you might download it and try it. Or just wait until Andy and the team post their release next week.

https://skydrive.live.com/?cid=8c21125447802b66&id=8C21125447802B66!134

Rob
Nov 18, 2013 at 7:45 AM
andyr wrote:
The main branch will have support for vs2013 rtm and the latest ReSharper next week. ~Andy.
Great, thanks!
Nov 20, 2013 at 8:45 PM
That's great news! You should add a donate button somewhere for us to send you some thanks for all the great work you do on this.
Nov 21, 2013 at 4:11 PM
Hey Andy, is there any update on this. Using StyleCop quite a bit to protect our applications and would greatly appreciate the drop.

Many thanks!
Coordinator
Nov 23, 2013 at 2:56 PM
Hi. Working on this again over this weekend. Trying to upgrade to VS2013, latest ReSharper build of 8. Also making the solution build with VS2013 RTM. Had some problems with my dev box but I'm on it again now.
Nov 23, 2013 at 8:51 PM
Really looking forward to it. Thank you Andy. :)
Coordinator
Nov 23, 2013 at 9:03 PM
Having a nightmare getting the tests to run in vs2013 :-(


~Andy.

Nov 24, 2013 at 1:36 AM
Using MSTest, right? That's what I gather from the source, anyway. What's the nightmare?

I'm no expert or anything but I've been using xUnit in VS2013 for several weeks now with relative success, maybe you could migrate (depending on the problem)?
Coordinator
Nov 24, 2013 at 9:42 AM
All done :-) https://stylecop.codeplex.com/releases/view/79972 adds support for latest ReSharper 8.0 build and will install into VS2013.
Nov 24, 2013 at 1:33 PM
Thank you!
Nov 24, 2013 at 2:10 PM
Ahh. Better! Thank you!
Nov 24, 2013 at 2:30 PM
Thanks for all your hard work, Andy!
Nov 24, 2013 at 3:33 PM
excellent, what is your paypal... will buy you a pizza!
Coordinator
Nov 24, 2013 at 3:42 PM
Edited Nov 29, 2013 at 3:32 PM
I'm andy at stylecop dot com (email) - and thanks :-)
Nov 25, 2013 at 5:18 PM
Edited Nov 25, 2013 at 5:18 PM
Andy,

Thanks for the new release! I just installed it and it's still complaining about compatibility with ReSharper version 8.0.2000.2660 during the installation. It thinks it's only compatible with v8.0.1000.something.

Rob
Coordinator
Nov 25, 2013 at 5:46 PM
You're welcome.

Are you sure you have the right one and have updated ReSharper correctly?

I read the registry to check which version so maybe an older one didn't remove correctly.

Anyone else seeing this?


~Andy.

Nov 25, 2013 at 8:50 PM
Nope mine complained about 8.0.1, I updated to R# 8.0.2, and it stopped warning
Nov 25, 2013 at 8:51 PM
felickz wrote:
Nope mine complained about 8.0.1, I updated to R# 8.0.2, and it stopped warning
I had exactly the same, works like a dream again now, thanks Andy
Nov 25, 2013 at 9:40 PM
Edited Nov 25, 2013 at 9:41 PM
Of course, we'll all be asking about Resharper 8.1 soon as it's now in beta! :P

The following guidance for extensions has been posted:

http://blogs.jetbrains.com/dotnet/2013/11/resharper-81-eap-guidance-for-extensions/
Dec 3, 2013 at 3:18 PM
Thank you Andy!!!!!! Many many many many many thanks for your work.
Dec 4, 2013 at 8:39 AM
Thanks Andy! Working like a dream now!
Dec 12, 2013 at 5:40 PM
Looks R#8.1 is out, hope changes from 8.0.2 -> 8.1 aren't big, so updating Stylecop for new version won't be difficult
Coordinator
Dec 12, 2013 at 8:06 PM
I hope so too.

-A.


Dec 13, 2013 at 9:28 AM
Edited Dec 13, 2013 at 9:28 AM
waiting a support of R# 8.1
Dec 13, 2013 at 9:35 AM
+1
Dec 14, 2013 at 4:25 AM
+1
Dec 14, 2013 at 4:52 AM
Edited Dec 16, 2013 at 12:53 PM
I haven't tested this much, but put together a quick build for R# 8.1 support. An unofficial build can be downloaded from (removed link). If a couple people can confirm it works I'll submit a pull request. Also let me know if there are any problems.

edit:
An official build has been released with R# 8.1 support.
Jan 2 at 1:37 PM
Hi, I didn't want to create a Work Item for this, but the ReleaseNotes.txt has not been updated with 4.7.48.0 change information.

I see from Source history that work on 4.7.48.0 began in November by AndyR, and I reviewed the checkins, but am not 100% sure what the changes are between .47 and .48.

Thanks.