Visual Studio error: The “GenerateResource” task f

2019-01-25 01:38发布

I am trying to build a solution with many projects, and I'm getting this error for a Windows Service project:

The "GenerateResource" task failed unexpectedly.
System.Runtime.InteropServices.COMException (0x80070050): The file exists. (Exception from HRESULT: 0x80070050)
   at Microsoft.Build.Shared.NativeMethodsShared.InprocTracking.WriteContextTLogs(String intermediateDirectory, String tlogRootName)
   at Microsoft.Build.Utilities.FileTracker.WriteContextTLogs(String intermediateDirectory, String taskName)
   at Microsoft.Build.Tasks.GenerateResource.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask, Boolean& taskResult)   ImportProcessorWindowsService

As suggested in another similar question, I tried deleting my .suo file, but that did not help.

I have been able to build this solution in the recent past. How do I fix this?

5条回答
神经病院院长
2楼-- · 2019-01-25 01:58

I checked out (VSS) the obj folder in Solution Explorer and I got a dialog stating that a couple of files and or folders were missing and did I want to create them. I clicked OK and then rebuilt the project without errors.

查看更多
叛逆
3楼-- · 2019-01-25 01:59

In the more recent versions of Visual Studio it's quick and simple to use the clean and rebuild solution options available on the build toolbox

查看更多
不美不萌又怎样
4楼-- · 2019-01-25 02:10

Run Visual Studio with as administrator.

查看更多
贼婆χ
5楼-- · 2019-01-25 02:19

I figured this out. It seems to have been caused by some files being marked Read Only in the obj/x86 folder.

Lovely how TFS likes to mark files as Read Only.

I deleted the contents of obj/x86 and the error went away.

查看更多
一夜七次
6楼-- · 2019-01-25 02:19

in my case I re-opened the same project with VS2013 instead of VS2010, so I successfully rebuild it (it creates a new file (*.v12.suo). Then I back with VS2010 and finally all was ok. Hope this helps

查看更多
登录 后发表回答