-
Notifications
You must be signed in to change notification settings - Fork 12.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: tsc.exe exited with code 2 - for ASP.NET CORE only #10702
Comments
I'm getting it in one standard ASP.NET, but not another (VS 2105 Update 3) -- the file doesn't exist in either. |
Ok, it happens only when front-end app files are in subdirectory like "wwwroot" or something like this. Moving it all outside resolved problem... |
Exclude 'node_modules' from project, VsTsc task won't execute on all those tsconfigs -- ( I think -- VS goes into endless hourglass mode when I try to exclude folder from project, so I can't confirm yet -- so now I have a real VS issue discovered from a non-issue. ) Manually deleted all the node_modules from csproj, errors are gone. |
VS keep locking up on me when I attempted to exclude from project. So I deleted it instead from Solution Explorer and then went to the command prompt and did npm install to reinstall all dependencies. That re-added it to my base project file structure without making it part of my project. The error went away and my angular app works great now. |
I got the similar issue in VS2015 solution, .net 4.5. Severity Code Description Project File Line Suppression State |
@SGeorge007 are you still having this issue? Do you have a build log you can share? Thanks. |
Closing until we can get an up-to-date repro with more details. |
I try to run angular quickstart template under asp.net core project
https://github.com/angular/quickstart
When I build application I get MSB6006: "tsc.exe" exited with code 2.
From output I've got detailed problem info:
The problem occurrs only for ASP.NET Core Project, it works fine for standard ASP.NET project. I use VS 2015 Update 3.
Do you know what can be a problem here
The text was updated successfully, but these errors were encountered: