

#VISUAL ASSIST FOR VISUAL STUDIO 2022 CODE#
But I had my hands on VS code the moment it hit open beta. This script does the following: Remove a temporary file 1489AFE4.TMP in the users temp directory used by VA. NET 2.0 since it was a huge pain to write the equivalent of method contracts - especially pre-WCF - by hand. Resets the trial period for Visual Assist X. During the installation I remembered that a VS2022 instance was still running and I closed it. I eventually migrated to VS exclusively for webservices in. Yesterday there was a prompt in my VS2022, 17.2.2: 'New Visual Assist Version Available' and I installed via VAXSetup24510.exe for VS2010, 2013, 2017, 20. NET 1.1, I would open VS (gosh, 2000? 2003?) for very specific rare tasks that it could accomplish faster than I could via the CLI. Prior to that, classic ASP was exclusively Notepad++ PHP was emacs or notepad depending on OS Perl was nano (pico back then - the laughter when I mentioned that got me to learn vi and emacs).īack in. Then again, my expectations for IDE performance are pretty strict.

Jury is still out, but they have optimized the hell out of it, removed a lot of bloat, and really upped the performance, while the opposite has been happening with VS Code. This is the first Visual Studio that I think could be as good as VS Code as an IDE. Besides, there is probably a setting in the project or solution I could adjust to change the behavior to a way I like more anyway. It's still got some idiosyncrasies (well, at this point I'd describe the situation more like I have the idiosyncrasies that intellisense is trying to correct, but still - the user is often correct, especially as the product targets more and more technical and power users).

It makes things like manually writing a bunch of props so much. It doesnt make huge code predictions, but it predicts things like method call arguments with a respectable amount of success, for a first version at least. It shows you a code prediction and you can accept it by pressing tab. It's the first time I haven't turned it off within hours of using a product, and I've used a lot of IDEs for MS languages. Our last release, 2021.3, was mostly focused on supporting the upcoming Visual Studio 2022 Previews. Yep, in 2022 they added a copilot-like functionality.
