No updates of any kind have been applied to my computer except for early last week. And yet, somehow randomly I am no longer able to build 32-bit executables with Visual Studio Professional 2015. I am currently running said product, version 14.0.25431.01 Update 3 and I have version 4.6.02001 of .NET. The project I'm trying to build however is targeting .NET Framework 3.5. I tried to build the project using "Any CPU" and while it was building a window came up saying "MSBuildTaskHost.exe has stopped responding". Afterward, the build console spits out these errors:
Task host node exited prematurely. Diagnostic information may be found in files in the temporary files directory named MSBuild_*.failure.txt.
The "GenerateResource" task's outputs could not be retrieved from the "FilesWritten" parameter. Object does not match target type.
The diagnostics file it is referring to had this to say:
UNHANDLED EXCEPTIONS FROM PROCESS 10128:
=====================
10/3/2016 12:14:01 PM
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at Microsoft.Build.Tasks.GenerateResource.CreateOutputResourcesNames()
at Microsoft.Build.Tasks.GenerateResource.Execute()
at Microsoft.Build.CommandLine.OutOfProcTaskAppDomainWrapperBase.InstantiateAndExecuteTask(IBuildEngine oopTaskHostNode, LoadedType taskType, String taskName, String taskLocation, String taskFile, Int32 taskLine, Int32 taskColumn, AppDomainSetup
appDomainSetup, IDictionary`2 taskParams)
at Microsoft.Build.CommandLine.OutOfProcTaskAppDomainWrapperBase.ExecuteTask(IBuildEngine oopTaskHostNode, String taskName, String taskLocation, String taskFile, Int32 taskLine, Int32 taskColumn, AppDomainSetup appDomainSetup, IDictionary`2 taskParams)
at Microsoft.Build.CommandLine.OutOfProcTaskHostNode.RunTask(Object state)
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj)
===================
I've already repaired VS and restarted multiple times. Could this be a hardware issue? It seems odd, considering that it builds just fine for 64-bit. Any help would be greatly appreciated.