madskristensen / WebAnalyzer

A Visual Studio extension
Other
55 stars 17 forks source link

Visual Studio 2017 support #51

Open paddyza opened 7 years ago

paddyza commented 7 years ago

Does Web Analyzer support Visual Studio 2017?

Thanks!

nunoleong commented 7 years ago

+1 request for VS 2017 support :)

MartynJones87 commented 7 years ago

👍 request for VS 2017 support please!

davidlmorris commented 7 years ago

Extreme +1 request for VS 2017 support :)

davidlmorris commented 7 years ago

A follow-up. I can see that Web Code Analysis is included with vs2017. (Under tools menu). However it is missing tslint. I didn't agree with every 'opinion' expressed in tslint, but I found it very useful. With vs2017 I feel I am coding naked. I even tried to go, back, but weird things started happening in vs2015. Is there a tslint inclusion coming (I compile ts with gulp, and use tsconfig.json is various view folders). Is this related to JavaScript "Salsa" Language Service?

What are the plans for tslint in vs2017 (if any)?

gh5692 commented 7 years ago

:+1: Please add support for VS 2017. I've had to go back to CLI :(

dneelyep commented 7 years ago

+1 more for VS 2017 support.

rich-newman commented 7 years ago

This was something I wanted too, so I upgraded this project to VS2017 and took out ESSLint, CSSLint and CoffeeLint as they are already in Visual Studio.

I've called it 'TypeScript Analyzer' to differentiate it from Mads' extension. It works exactly as the old extension did in VS2015.

It's now in the Visual Studio Gallery under TypeScript Analyzer, and the code's on GitHub.

I'm hoping this is just a temporary thing until full TSLint support is put into Visual Studio.

Mads - if you're reading and you have any objections let me know. I've used separate GUIDs and disabled the telemetry, so it shouldn't conflict. I think it's a separate project, but if you want a pull request let me know.

madskristensen commented 7 years ago

@rich-newman That's awesome. You just demonstrated the power of OSS. Thanks for doing this!!

davidlmorris commented 7 years ago

@rich-newman Brilliant! I'd gone back to VS2015 community because of this (well that, and Code lens). I'll try using vs2017 for a few days to see how it works out.

IF you are up for a challenge, the html link, from the code column which currently points to 'https://github.com/palantir/tslint?rule=[rule]#supported-rules' should point to 'https://palantir.github.io/tslint/rules/[rule]' -- e.g: https://palantir.github.io/tslint/rules/member-access/ rather than https://github.com/palantir/tslint?rule=member-access#supported-rules. [AFAIKT this is not an output from tslint, but something you have to massage in VS.]

@madskristensen Thanks for all the tools and the endorsment of @rich-newman's addition.

rich-newman commented 7 years ago

@davidlmorris I accepted your challenge and have released an upgraded version with the correct helpfile links. Thanks for pointing it out.

davidlmorris commented 7 years ago

That was quick! Thank you.

vladimir-djokic commented 7 years ago

Update: you can download extension on the markeplace.

There is a new extension (in-development) for Visual Studio 2017 named TSLint which I'm personally coding. It was done in a day or two (note that I haven't coded in C# for a few years), but I'm adding more and more as I learn how things are working in the VS extensions pipeline.

It is a start of (hopefully) worth-wile Visual Studio 2017 extension that can mark .ts code withing the editor, based on the installed tslint and tslint.json configuration.

It is not published on the marketplace yet (a lot more coding to do), but you can download and build it yourself. Give it a try, If you have the time. The more people try it out, the more data I will have to make it worth-wile.

304NotModified commented 7 years ago

@madskristensen I think it would be nice to link to https://marketplace.visualstudio.com/items?itemName=RichNewman.TypeScriptAnalyzer from GitHub and visualstudio marketplace.

Or is there an update planned for VS2017?

ghost commented 7 years ago

@madskristensen I forked this and updated it to support VS2017(as well as .NET update and NuGet package updates). What do you think?

madskristensen commented 7 years ago

@alan1099 I can't stop you, but I don't think that is a good idea. VS2017 already ships with ESLint, CoffeeLint and CssLint so it would conflict.

MJLHThomassen-Eurocom commented 6 years ago

Any updates on this?