![]() It used to display the node.js messages such as "the server is running" and other compiler messages, but now it only displays the. One thing I did notice is that the usual Server Messages are not showing in the Output Window. I'm not sure if it's related, but when I tried to run the Angular Application again it looks like Angular is pointing at another (random) port than is set in the debug settings in the project. I noticed that two windows will pop up, however: First a blank one, then the actual Angular server window. Update 3Īlso not sure if this helps, but I tried setting the node.exe properties to "Run this program as an Administrator" to see if it happen to be a permission issue. The only difference is killing the Node.js processes doesn't let Visual Studio shutdown. ![]() NET Core Web Application, except this time selecting the Angular Template and it works better: The Hot Reload works and it seems to run much faster. If I kill the Node.js process then Visual Studio will finally shutdown, but it leaves the Console Window Host and VBCSCompiler running which have to be shut down manually. Any time I try to run any kind of JavaScript using the SPA Templates, the Node.js processes don't shut down. I completely uninstalled Visual Studio and all other components, installed Node.js, and then Visual Studio, but the problem still persists. NET Core Web Application without any changes, I received an error saying that Node.js was not installed-even though I was able to find a node.exe in the MsBuilds folder under Visual Studio. One interesting thing I found when doing this: I originally only installed Visual Studio and selected both the "Web Development" and "NodeJS Development". Should I install node before Visual Studio, or visa versa? Is there possibly some setup that I need to perform with Visual Studio or Node to get things working correctly? Update 2Īfter not finding any fix I tried a complete reinstall of Windows, including a disk format, and then only installed Visual Studio and Node.js. This happens even if I run Visual Studio as an administrator. If I manually shut down the Node processes, then Visual Studio will finally shut down-but it leaves other processes like the VSCompiler and Consoles running. UpdateĪfter some messing around, it looks like Node is causing the problems. NET Core 3.0 and it looks like only Visual Studio 2019 is supported for that. Prior to this install, only projects created in Visual Studio 2017 seemed to work as expected. ![]() If these hang unexpectedly and are not shut down they will continue to use the old versions of the code and nothing that is done will update until the processes are shut down, causing complete insanity.Ĭould there a specific install procedure I need to perform as a workaround? Or am I possibly missing NuGet packages or Add-Ons? Since this is a fresh install of the operating system, are there Windows Features that I need to install? Or other configuration/permission changes that could be causing this? ![]() I am very hesitant to continue working with this install as I have had several issues when these processes. I have tried debugging in Firefox and Chrome, both with the same results. But after updating the JavaScript code and refreshing the browser things seem to update, so it does seem to be recompiling. I have tried installing Visual Studio 2019 with the Node.js provided by the Visual Studio Installer, in addition to installing Node.js V12.4 and V13.6 manually with the same results.Īnother problem: If I update the project from JavaScript to TypeScript using npx create-react-app client-app -typescript, Hot Updates stop working entirely. Things seemed to be working alright, except that after updating JavaScript code the browser updates after a fairly long pause things seem to be lagging.Īfter closing Visual Studio 2019 from the default Web App (no updates) there are several processes that seem to hang, and have to be shut down manually: I created a default React.js ASP.NET Core Web Application and ran the project. NET Core 3.1 Web Development but am running into several issues. I am working on a fresh install of Windows 10 Pro (2) and trying to get Visual Studio 2019 setup and configured for.
0 Comments
Leave a Reply. |