Visual Studio 2022 and Angular Language Service
-
Sorry, couldn't find a more appropriate forum to post this. We have a Angular/.NET Core app that we are attempting to upgrade to .NET 8. I have the Angular Language Service installed and working with no problem in VS2019. With VS2022, not so much. Every time I load any project with Angular code I get this error, "Task Failed - Activating language client Angular Language Service Extension: The JSON-RPC connection with the remote party was lost before the request could complete." I've tried everything I can think of, including creating a ticket with MS. Surprisingly, they actually attempted to help resolve the problem. We renamed the cache folder, ran VS as admin, reset all options, disabled the extension auto update, repaired VS2022 (appropriate reboots), checked the Microsoft.VisualStudio.Default.err file, checked the log files (%temp%\VSLogs), uninstalled/reinstalled VS2022 (cleared temp files, rebooted), insure Node.js is installed, insure Win11SDK (both) are installed. I'm at a complete loss as is everyone else. Other devs working on Angular/.NET projects in VS2022 do not have this issue. I was seeing this error before attempting to upgrade anything on the solution. Oddly, break points in TypeScript files work, but viewing the value of TypeScript variables does not work nor does F12 in TypeScript code. I'd rather get this working in VS2022 instead of using VS Code for Angular development and VS2022 for .NET, that's just ugly and messy.
"...JavaScript could teach Dyson how to suck." -- Nagy Vilmos
-
Sorry, couldn't find a more appropriate forum to post this. We have a Angular/.NET Core app that we are attempting to upgrade to .NET 8. I have the Angular Language Service installed and working with no problem in VS2019. With VS2022, not so much. Every time I load any project with Angular code I get this error, "Task Failed - Activating language client Angular Language Service Extension: The JSON-RPC connection with the remote party was lost before the request could complete." I've tried everything I can think of, including creating a ticket with MS. Surprisingly, they actually attempted to help resolve the problem. We renamed the cache folder, ran VS as admin, reset all options, disabled the extension auto update, repaired VS2022 (appropriate reboots), checked the Microsoft.VisualStudio.Default.err file, checked the log files (%temp%\VSLogs), uninstalled/reinstalled VS2022 (cleared temp files, rebooted), insure Node.js is installed, insure Win11SDK (both) are installed. I'm at a complete loss as is everyone else. Other devs working on Angular/.NET projects in VS2022 do not have this issue. I was seeing this error before attempting to upgrade anything on the solution. Oddly, break points in TypeScript files work, but viewing the value of TypeScript variables does not work nor does F12 in TypeScript code. I'd rather get this working in VS2022 instead of using VS Code for Angular development and VS2022 for .NET, that's just ugly and messy.
"...JavaScript could teach Dyson how to suck." -- Nagy Vilmos
Just noticed Angular is "owned" by Google. For me, being a .NET (MS) "person", that would be a non-starter from day 1 in terms of future proofing any mission critical system. I know that doesn't help you; just saying if you have any future say while on the "leading" edge. "VS Code for Angular" it is then.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
Just noticed Angular is "owned" by Google. For me, being a .NET (MS) "person", that would be a non-starter from day 1 in terms of future proofing any mission critical system. I know that doesn't help you; just saying if you have any future say while on the "leading" edge. "VS Code for Angular" it is then.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
I don't mix my (obsolete) primary with "3rd party". Whatever floats your boat. Or sinks it as the case might be.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
Just noticed Angular is "owned" by Google. For me, being a .NET (MS) "person", that would be a non-starter from day 1 in terms of future proofing any mission critical system. I know that doesn't help you; just saying if you have any future say while on the "leading" edge. "VS Code for Angular" it is then.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
It wasn't my call. In fact I campaigned against is extensively. We have been a MS shop for years. It was brought in by the previous manager and his friend/buddy/pal/ex-employee/consultant that the company paid thousands of dollars for extra work even though they refuse to pay extra money to any current devs who are willing to do extra work from home after hours. Conflict of interest and all that, but paying a former employee who is buds with the manager is not. The current manager thinks it's great. Unfortunately we found out after the fact that it is less than secure. We were informed of this by a security consultant we hired, because we can't figure this out on our own apparently. But we're still using it. We have a new site that is again begin written in Angular, go figure.
"...JavaScript could teach Dyson how to suck." -- Nagy Vilmos
-
It wasn't my call. In fact I campaigned against is extensively. We have been a MS shop for years. It was brought in by the previous manager and his friend/buddy/pal/ex-employee/consultant that the company paid thousands of dollars for extra work even though they refuse to pay extra money to any current devs who are willing to do extra work from home after hours. Conflict of interest and all that, but paying a former employee who is buds with the manager is not. The current manager thinks it's great. Unfortunately we found out after the fact that it is less than secure. We were informed of this by a security consultant we hired, because we can't figure this out on our own apparently. But we're still using it. We have a new site that is again begin written in Angular, go figure.
"...JavaScript could teach Dyson how to suck." -- Nagy Vilmos
That sounds sooooooo familiar. Brothers. Cousins. Seen it all. (Custom) Frameworks are the remnants of someone else's project. (I had one "keener" lobby for a framework he saw in a book. For a national company project I was leading. NET 1.x). Every project I develop becomes it's own framework. SCADA. ERP. RTS. Nothing ever went begging for an "Angular" or Node.js or whatever. The frustration of dealing with someone else's "black box". (Unless they pay the bills; but that gets old too. As a contractor).
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
Sorry, couldn't find a more appropriate forum to post this. We have a Angular/.NET Core app that we are attempting to upgrade to .NET 8. I have the Angular Language Service installed and working with no problem in VS2019. With VS2022, not so much. Every time I load any project with Angular code I get this error, "Task Failed - Activating language client Angular Language Service Extension: The JSON-RPC connection with the remote party was lost before the request could complete." I've tried everything I can think of, including creating a ticket with MS. Surprisingly, they actually attempted to help resolve the problem. We renamed the cache folder, ran VS as admin, reset all options, disabled the extension auto update, repaired VS2022 (appropriate reboots), checked the Microsoft.VisualStudio.Default.err file, checked the log files (%temp%\VSLogs), uninstalled/reinstalled VS2022 (cleared temp files, rebooted), insure Node.js is installed, insure Win11SDK (both) are installed. I'm at a complete loss as is everyone else. Other devs working on Angular/.NET projects in VS2022 do not have this issue. I was seeing this error before attempting to upgrade anything on the solution. Oddly, break points in TypeScript files work, but viewing the value of TypeScript variables does not work nor does F12 in TypeScript code. I'd rather get this working in VS2022 instead of using VS Code for Angular development and VS2022 for .NET, that's just ugly and messy.
"...JavaScript could teach Dyson how to suck." -- Nagy Vilmos
In general I wouldn't be so over-commited to Microsoft stack as the other poster in this thread. Technology landscape changes. I can't state that it's always for good but at least it's useful to have understanding what tools are available. Regarding the original question: have you tried other editors? Say, angular language service for Visual Studio Code?