I believe they've rewritten many parts of them, including complete 圆4 rebuild etc. I mean the code base of their Office suite is probably more ancient but they've made enough rework over the years to keep them fairly stable. How much technical debt MS must have had accumulated in Visual Studio over the years? I know VS Code is a lot more "modern" and likely more stable, but it simply doesn't offer the full feature set of VS 2019 yet. Weird editor errors all over the place and he just shrugged them off and kept going ("this is a new update so some things may be a bit buggy."). It's funny because the other day I was participating in this online virtual ASP.NET Core/C# meetup/bootcamp kind of event, and the instructor's VS 2019 is visibly bugged. The thing is plain unusable so had to go back to the old inferior editor. Like rename/refactor of anything (not even in Razor files) will do it. But once the new Razor editor is turned on, VS cannot last more than 10 minutes before throwing some kind of exceptions. It does have several major improvements compared to the current Blazor Razor editor, which by itself is buggy to begin with (sometimes need restart to clear bogus compile errors). The latest annoyance is with the "Experimental Razor Editor". Of the couple of ones I do use, none is the cause (verified by having them disabled). It's not the extensions, I barely use any. But once ASP.NET CORE mixed UI/HTML text editor stuff is involved, it turns into a train wreck. I found that when working with C# only codes (like class libraries etc) it's relatively more stable. I've even clean installed (not just the program, but the whole Windows 10 OS) a couple of times in the past few months.
I take great care in keeping my PCs and software environments squeaky clean.īut VS 2019 throws more exceptions than any other programs I've dealt with lately, more than some of those legacy programs written for DOS/Win3.1 that some of my clients have been using since the 90s. I'm new developer with a long time sysadmin background. No crashes so far (especially the renaming crush fix alone is saving me lots of grief) and the "preview" Razor editor is noticeably snappier (though it still could be even faster! ).
I installed and used preview 3 since its release and am happy to report that it's indeed working very well. He took a few bug reports from me and also let me know that v16.10 would be a significant improvement - starting from preview ver.3. He was very helpful and gave me some insights on the improvements being worked on for VS within Microsoft, especially the new Razor editor.
Soon after I made the original post below, a Microsoft employee who works on the Visual Studio team DM'ed me.
0 kommentar(er)
