Click here to Skip to main content
15,886,110 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
I have a solution developed in VS 2013 containing some 20 odd projects which used to build fine initially but now for past couple of days we are facing an issue where the build randonly hangs.

I looked up in Task manager and noticed the process CSC.EXE is running but not doing anything basically it is in hanged state. If I kill the process the rest of the Build for the other projects continous.

What I have tried:

1. The Build hangs on different projects, So not problem with one particular project in the solution.

2. I tried the same thing through Command line Argument og MSBUILD.EXE, it also exhibited the same behaviour where the build got hanged on some random project and once I killed CSC.EXE from task manager the rest of the build continued.

3. This problem is occuring even when I open VS in Admin Mode.
I have complete rights on the system, I am the admin.

4. If I build the projects individually in the same build order they get build, only when I build the complete solution this problem occurs.

Any suggestions/pointers are welcome.
Posted
Updated 21-Jun-17 9:59am
v2

1 solution

First thing I would do is check all running processes and close suspicious ones.
Then check the Build order.
Then check if there are no conflicts with x86 / x64 / AnyCpu.
Rebuild all.
If that fails then reinstall Visual Studio.
 
Share this answer
 
Comments
Member 13272039 21-Jun-17 15:58pm    
I checked all running process. Made sure I had closed all CSC and MSBuild process before doing build again.

Build Order is fine because if I build the projects individually in the same order they build.

We are facing the same issue on 10 systems so not sure if reinstalling VS will help.
RickZeeland 21-Jun-17 16:13pm    
Maybe it's an .NET framework issue, check if updates cause trouble. I had a very strange issue on Windows 10 that had to do with the country / region settings a week ago.
Member 13272039 21-Jun-17 23:40pm    
Could be. One more interesting observation I made today was the CSC.EXE is hanging only if I connect to the machine through Citric if I do a RDP it works fine.
Mysterious !
Richard Deeming 22-Jun-17 16:13pm    
It's not quite the same symptoms, but maybe this might help:
Error: Visual C# Command Line Compiler has Stopped Working[^]

There's also this thread, which suggests turning off CRL checking:
.NET 2.0/csc.exe/SoapHttpClientProtocol hangs for 15-20 seconds (compared to .NET 1.1) under Citrix[^]

Basically, it sounds like it's either hanging on a network request, or Citrix is trying to do something odd that csc.exe doesn't like.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900