soulblazer
soulblazer

Reputation: 1219

"GenerateResource" task CLR2 runtime error

My app keeps getting this error (I'm using VS 2013, VB.NET, and Windows 8.1, by the way):

Could not run the "GenerateResource" task because MSBuild could not create or connect to a task host with runtime "CLR2" and architecture "x86". Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "C:\Program Files (x86)\MSBuild\12.0\bin\MSBuildTaskHost.exe" exists and can be run.

The app is for .NET 3.5 (3.5 and lower versions get me this error). I try to run the app again. Sometimes, it works; sometimes, the error comes back.

I already tried looking up for answers at Google and the answer they gave me turned out to be: "Your build's username is too long" (they said that 20 characters or more cause the error), but it's not true. My user name is 5 characters only. Anyway, I don't think my build's username's length has anything to do with it; it makes no sense.

Does anyone know what is wrong with 3.5 and lower versions? Thank you.

Upvotes: 35

Views: 22968

Answers (8)

I'm using VS 2013, VB.NET, and Windows 10, 64 bits, by the way

Just change in XML properites , Services : .NET Framework 4.6 instead .Net Framework 2.0 (Default)

and working fine for me.

Upvotes: 1

Zaehos
Zaehos

Reputation: 185

None of the answers in this worked for me. I had to run Visual Studio as admin. Hope this helps someone in the future!

If you don't know how to run a program as admin on Windows, click this link.

Upvotes: 0

Nikhil Agrawal
Nikhil Agrawal

Reputation: 48568

Adding this in each project is a cumbersome task. So you can set it in the environment variables.

Click Start>> Right-click Computer >> Properties >> Advanced system settings >> Click Environment Variables button to open the dialog, then under the System variables section, click New… button, type the Variable name = DISABLEOUTOFPROCTASKHOST, and type the Variable value = 1, then click Ok.

More here

Upvotes: 3

Gurce
Gurce

Reputation: 664

I tried opening an old VS2010 vb project inside VS2013 recently and just ran into this problem. I got around it this way:

  1. I went to the vb project's properties page
  2. I clicked the "Debug" tab
  3. In the "Enable Debugers" section, I saw that the "(x) Enable the Visual Studio hosting process" checkbox was already checked.
  4. I tried un-checking the "( ) Enable the Visual Studio hosting process" option
  5. I saved these changes (Ctrl+S)
  6. I then checked the "(x) Enable the Visual Studio hosting process" checkbox once more
  7. I saved these changes (Ctrl+S)

My next re-build of the project was then successful.

Luckily, I was able to observe how the .vbproj file changed in my version control, and saw that it added the following line into it (which was not there before, despite the checkbox already being set initially):

<UseVSHostingProcess>true</UseVSHostingProcess>

Upvotes: 0

Andrew Stephens
Andrew Stephens

Reputation: 10201

I encountered this error when trying to build a sample solution that was included in some software that was installed under C:\Program Files\. Visual Studio prompted me to restart with elevated privileges (as it does when opening a solution in a "secure" location), however the build failed with the OP's error message.

Copying the solution to a "normal" folder (e.g. C:\Temp) solved it for me.

Upvotes: 0

Salvador Nieto
Salvador Nieto

Reputation: 21

I try adding the follow but didn't works

  <PropertyGroup>
        ...
        <DisableOutOfProcTaskHost>true</DisableOutOfProcTaskHost>
    </PropertyGroup>

this solve this issue for me, adding the same as enviroment Variable

DisableOutOfProcTaskHost=true

Upvotes: 0

Ruben Rivero
Ruben Rivero

Reputation: 303

Clean and rebuild solution worked for me.

Upvotes: 14

Stefan Steinegger
Stefan Steinegger

Reputation: 64628

This fixed the issue on my machine:

To resolve it, go to your csproj file and add the following line under the default property group:

<PropertyGroup>
    ...
    <DisableOutOfProcTaskHost>true</DisableOutOfProcTaskHost>
</PropertyGroup>

Found here.

Upvotes: 49

Related Questions