Announcing the general availability of IntelliCode plus a sneak peek
We’re excited to announce the general availability of Visual Studio IntelliCode and offer a sneak peek at an up-and-coming feature we think you’ll love! With the release of Visual Studio 2019 Version 16.1, IntelliCode will be included with any workload supporting C#, C++, TypeScript/JavaScript, and XAML. However, only the C# and XAML models are currently generally available. C++ and TypeScript/JavaScript remain in preview at this time. We’ve learned so much from all of you in during our year in public preview and are thrilled for this next step.
If you haven’t heard of IntelliCode, it’s a set of AI-assisted capabilities that aims to improve developer productivity with features like contextual IntelliSense, code formatting and style rule inference.
General Availability with Preview Perks
IntelliCode is growing fast so we’ve also packed in some preview features you can try out if you’d like, no extra installations required. Preview features, such as such as C++ and TypeScript/JavaScript support and argument completion, will be disabled by default but you can easily enable any preview features via Tools > Options > IntelliCode. Check out our updated docs for a full list of preview features.
A Quick PEEK: finding repeated edits
Have you ever found yourself making a repeated edit in your code, for instance when you’re refactoring to introduce a new helper function? You might consider creating a regular expression search to find all the places in your code where the change is required – but that seems like a lot of work, so you resign yourself to the tedious and error prone task of going through the code manually. What if an algorithm could track your edits (locally of course), and learn when you were doing something repetitive like that after only a couple of examples? Repeated edit detection does just that, and suggests other places where you need that same change:
This feature is under development right now, and we’re looking to make it available in a future release of IntelliCode.
Want to hear about new preview features like this first? Sign up to receive regular updates!
Let us know what you think!
IntelliCode has benefitted greatly from all the customer feedback we’ve received in the past year and we hope you’ll help us continue to improve by letting us know how IntelliCode is working for you! Feel free to let us know what you’d like to see next by filing feature requests or reporting issues via Developer Community.
Light
Dark
11 comments
Great news but please support VB.NET
🦄 Hip-Hip!
You can’t leave behind the first and BEST, most inclusive, aproachable language ever actually designed for the purpose! 🧙🏽♂️When we are eventually speaking to the AI to produce code: Do you think anyone wants to say ‘closing curly-brace’ instead of ‘End If’??Come on Allison, I’m activly promoting IntelliCode – do us right –> get me VB.net pretty please!
‘Course I understand how much worse javascript needs it… 8 )
This comment has been deleted.
I have many projects and large libraries that are in vb.net. Even new projects use it as it would take years to convert the libraries for no benefit.
VB.NET has no purpose to exist. Yes, its syntax is closer to human language, but that’s it. C# code looks cleaner and goes very well with C++ during learning process. It would be better if Microsoft spent that time on VB.NET to C# converter and killed VB.NET. Having multiple syntaxes is a little bit like having different mobile chargers i.e. people are wasting money on duplicating things and half of them, sooner or later ends up in a landfill.
I like VB the best because I can produce fastest with it.
However, if MS has made the decision that VB will not receive some of the improvement that C# will receive, then I believe MS should produce a converter that would convert complete projects from Vb to C++
This comment has been deleted.
Conveting VB to C++ has no benefits to anyone but maybe for you and another 10 folks. Try to embrace new and proven languages.
To C++? I’m not even sure this is possible, but why would you want that? VB.NET can be converted to C# pretty easily, you get all the benefits of .NET, without the verbose syntax of VB.
I prefer the VB verbose syntax than the C# less readable syntax.