Related
I faced the problem: whenever I open my working solution Visual Studio automatically starts build. I cannot find configurations to turn off this.
It looks like that problem is in solution, because I opened another solution and build did not start automatically.
This strange behavior is not expected one for VS2019. Please try:
1.Tools=>Import and Export Settings=>Reset all settings=>No, just reset settings to reset current VS settings to default.
2.Use vs installer to repair your VS if there's something broken with IDE.
3.Extensions=>Manage Extensions=>Installed=>Tools you can disable(don't need to uninstall) some third-party extensions and restart VS to check if this issue persists. To check if this issue is about VS itself or extensions.
4.Exit VS and delete the .vs, bin, obj folders of the projects in the solution, and then clear the cache, for VS2019, the corresponding folder is 16.0 instead of 14.0. After that, restart VS.
For me, this was a Resharper setting. When I turned this off it stopped happening. I think there is also a setting for Visual Studio to do this as well, but it is off by default.
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.
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.
Clean and rebuild solution worked for me.
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
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.
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
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.
I tried opening an old VS2010 vb project inside VS2013 recently and just ran into this problem. I got around it this way:
I went to the vb project's properties page
I clicked the "Debug" tab
In the "Enable Debugers" section, I saw that the "(x) Enable the Visual Studio hosting process" checkbox was already checked.
I tried un-checking the "( ) Enable the Visual Studio hosting process" option
I saved these changes (Ctrl+S)
I then checked the "(x) Enable the Visual Studio hosting process" checkbox once more
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>
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.
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.
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.
Clean and rebuild solution worked for me.
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
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.
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
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.
I tried opening an old VS2010 vb project inside VS2013 recently and just ran into this problem. I got around it this way:
I went to the vb project's properties page
I clicked the "Debug" tab
In the "Enable Debugers" section, I saw that the "(x) Enable the Visual Studio hosting process" checkbox was already checked.
I tried un-checking the "( ) Enable the Visual Studio hosting process" option
I saved these changes (Ctrl+S)
I then checked the "(x) Enable the Visual Studio hosting process" checkbox once more
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>
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.
I'm trying to add a Splash Screen to my form, but I'm getting the error -
'Application' is not a member of 'My'.
I've done some research and came across two possible solutions, but neither of them have worked for me.
Splash Screen Error "'Application' is not a member of 'My'." The answer here suggests ticking the 'Enable Application Framework' option in the Project settings, but that option is greyed out.
The 'My' Namespace in a VB.NET Application is Missing Members. This answer suggests that I need to add a Reference to the Project in the Project settings, but doing this does not fix the error.
Can anyone please suggest what I can do to solve this problem? Thanks.
That's a known issue for me. Open .vbproj file and change where it says
<MyType>Empty</MyType>
to
<MyType>WindowsForm</MyType>
We tried the suggestion above but it did not work for us with a Class Library in Visual Studio 2013.
After investigating another project that worked, we found that changing to using "Windows" instead of "WindowsForm" enabled that functionality
<MyType>Windows</MyType>
I recently ran into this issue as well. The solution in my case was that I had created a .NET Core app, rather than a .NET Framework app.
Copied my code into a new Framework app and it worked just fine.
VS2008 SP1, Winforms solution, VB.NET, compiling for x86 and .NET v2
I have about a dozen projects in the solution, with a couple of Windows forms projects and some class libraries.
If I rebuild the solution, it clears out and recompiles all the projects, as you'd expect...
... and then disappears without trace or error message. Since I'm reconnecting to VSS 2005 over HTTP across the internet, it takes all month to start back up with everything loaded, so it's incredibly irritating.
The compiled application itself works fine, and normal build and run after changes also works fine.
Any ideas why this might be? I've Googled without much success.
Thanks in advance.
EDIT: Just to clarify, No add-ins except Refactor! (I know, I guess I ought to try uninstalling it to see if it's that, but it's just too useful! - I will see if there's an update though).
And no custom build steps. It's just a vanilla Winforms app, with references between the projects (and some references to COM dlls for interop).
Thanks for the ideas so far..
EDIT AFTER PROBLEM SOLVED
Ok, guys, thanks again for all the ideas.
It turned out to be the version of Refactor! I was using. I installed the latest, and the crashing stopped... and Refactor! stopped working too. So I shut down VS, uninstalled Refactor! completely, and reinstalled the latest version... and now I no longer get the mysterious crashes, and Refactor! works again.
You might say, 'Duh, why didn't you try this ages ago', and it's a fair question... you know the way it is - something that happens intermittently... immediate pressures of urgent priorities... and of course the new version wasn't available then, and the benefits of the old version weren't trivial.
So, 3rd party addin the culprit.
Thanks again..
Do you use any third-party plug-ins, it will cause this too.
I had this issue with a couple of WinForms apps. I had to perform these exact steps in this exact order.
Close all of the designer files from the IDE. Or just close all of the files so your workspace is empty
Exit all instance of Visual Studio
Open VS, open project, do a full rebuild. That fixed me ... for awhile.
The common denominator for me is that all project that this happened to were created using older versions of Visual Studio. That's as far as I got tracking down the problem though.
I had no 3rd party plugins installed at the time.
Hope this little bit helps.
Try to debug Visual Studio, using WinDBG or Visual Studio. Attach to the faulting Visual Studio (before it crashes) and make sure that you stop on all exceptions.
If its a managed exception then you can probably understand what happened, if it's not try to see in the callstack who is the faulting dll.
Also try to work without source control, the quickest way is to disable the network card (no kidding).
reinstall Visual Studio...
Do you have any custom build steps for any of the projects you're building? They could be causing the crash.
You're forgetting VSS as a plugin.
I recommend you to change your source code control system to SVN. It will cost you a couple of days or may be weeks to get used to it but it worth the pain.
I know that's not always in your desition scope but if it is you will have lots of benefits with that change.