I've got a problem with my Visual Studio for Mac 2022 version 17.0.4 (build 23) when running my application and trying to debug my project. It seems that when I try to debug the project, it gives me an error screenshot below.
with it I can't seem to run my project in Debug mode because of this. Does anyone able to fix this issue? Please let me know sooner.
It seems the issue is the IDE itself, I tried installing the 2019 version of Visual Studio for Mac and it seems work perfectly! I think the main reason why in Visual Studio for Mac 2022 has this problem is because doesn't support the .NET Core 3.1 because it is about to be deprecated. I think this is why it doesn't work as expected. Anywho, it is been solved! Hopefully anyone who across the same issue knows this. Thanks!
Related
I have error in my project on time of build csc.exe exited with code -2146232797 visual studio 2017(Professional) in other Team's computer project building and running fine, so I not want to update nuget compiler,
Is there any permanent solutions there?
This issue happened for some people with vs 2017. you need to reinstall .net via
microsoft site
as requested and if the above link does not help, there is a thread in visual studio development community stating they fixed the issue in visual studio 2017 v15.5:
We have fixed this issue and it's available in Visual Studio 2017
version 15.5. Thank you for helping us build a better Visual Studio!
more over, there is another solution stating:
using the 2.2 compiler made the problem go away.
Multiple times I got this issue in VS 2019. I closed other VS projects and then build successfully.
I've Visual Studio 2017 community edition. I have a C# project created using Visual Studio 2015. When I try to open the project in VS 2017 I get an error message prompt:
--------------------- Microsoft Visual Studio
Project 'dataStructureInCSharp' could not be opened because the Visual C# 2017 compiler could not be created.
Please re-install Visual Studio.
--------------------------- OK
I'm trying to obtain help if anyone else has faced similar issue. I feel going the uninstall and then reinstall route is very costly for me and would try that option last if I've got no other resort.
What I've done so far :
Tried starting visual studio with administrative privileges
But problem remained same.
I tried creating a new console project solution from scratch but in that case I get very same error and an additional error error also shown below:
System Environment: Windows 7 Ultimate Service Pack 1
You can try to close all VS 2017 instances and delete the folder %localappdata%\Microsoft\VisualStudio\15.0_xxxx\ComponentModelCache, then open VS to create a new Console project.
Or
please re-run the VS 2017 installer as administrator, click the icon beside ‘Launch’ button and choose ‘Repair’ to repair as shown below:
Just to brief the history of my problem, I had first installed Visual Studio(VS) 2017 community when it was in RC stage. This was first time when I saw the workload based UI of visual studio installation. Initially I simply chose .Net desktop development workload to get started as I was interested in creating only console applications to get my hands dirty.
Initially it was all working well. One fine day I added all other workloads I was interested in namely Universal Windows Platform Development, Azure Development, ASP.NET and web development,Node.js development, and Mobile development with .Net. I'm not sure if there any of the specific workloads to be blamed for the issue I've posted.
Just to avoid the case if RC and RTM release builds might not have messed up my entire environment, I simply uninstalled the entire stuff, rebooted my machine and installed it again from scratch from latest RTM release for Visual Studio Community.
I would strongly recommend that you first try possible solutions suggested by #Sara-MSFT before doing clean reinstall just in case if it works. It can save you couple of hours required in whole reinstallation process if it works.
I am trying to install Monogame on VS 2017 however the option on the installer for VS 2017 is greyed out, even though I have VS 2017 installed. I also have VS 2015 and VS 2010 however I am not sure if it is those that are causing a problem. The version of MonoGame is 3.6.0.1625 and I currently have the directory: C:\Users\MY NAME\Documents\Visual Studio 2017\Templates\ProjectTemplates\Visual C#
Please help thanks
If anyone have this problem and is trying to install on non Admin account then just copy over whole Visual Studio 2017\Templates structure from your Documents to Administrator's Documents. (or the account with admin right you use in UAC prompt to install)
That solved it for me :)
This problem often happens when your templates are in the wrong directory.
The path you provided seems to be the right one tho.
Are your VS2015 templates in the C:\Users\MY NAME\Documents\ directory aswell ?
If not, try to move your VS2017 templates to the same directory as your VS2015 templates.
If those two are both in C:\Users\MY NAME\Documents\, look into Documents\Visual Studio 2017\Templates\ProjectTemplates and try to find the Visual C# folder. If it is missing add a new folder with this name and try again.
OK, simple answer is, that until MonoGame 3.7 drops, you are going to need to download the latest MonoGame Development build from the download page. This is fine as the dev build is still very stable and based off the current MASTER version of MonoGame from source.
I did a short Video on my "Darkside of MonoGame" channel a while back which walks you through everything you need to know to get up and running using VS017. (there is even a version there for VS2015 :D)
https://www.youtube.com/watch?v=zphaylhOrm0
Hope this helps.
I was having this same issue. Uninstalling MonoGame then Visual Studio, and reinstalling Visual Studio then MonoGame worked for me.
I've tried to build https://github.com/DEVSENSE/Phalanger, but after the build process it shows build errors. I tried VS 2015, maybe there it just a question of a wrong version?
It is outdated project, unload the Tests projects for now.
It is not the version of studio, see https://github.com/DEVSENSE/Phalanger/blob/master/Solutions/Phalanger.sln it says Studio 14 which is VS 2015.
Would be worth checking the readme, see https://github.com/DEVSENSE/Phalanger/tree/master/Source but this looks more like an issue in the code to me.
I recently upgraded my visual studio from 2012 to 2015 every thing was working perfectly fine on VS 2012 but i am getting
"An unhandled exception of type 'System.StackOverflowException' occurred in WebGrease.dll" when i run my application/code
below is details about version
package id="WebGrease" version="1.1.0" targetFramework="net40"
Update: the fix i found
There seems to be compatibility issue of webgrease(1.1.0) with vs2015 updrading it to WebGrease 1.6.0 solved the problem
I recently ran into this, but for a very specific use case. I am using Syncfusion products in a project for a client.
My dev machine has(had) Visual Studio 2013 Ultimate and Visual Studio 2015 Enterprise installed, side by side. My WebGrease package was fully updated to 1.6.0.
When I updated to the latest version of Syncfusion, I started receiving the WebGrease StackOverflowException shown above, but only when I was in VS 2015. 2013 did not give me the same error.
I also did not get the error unless I added a specific Syncfusion JS file to my bundles. Everything ran as expected until I added that one bundle.
I even went through the trouble of removing the built-in bundling support of the project, by removing Antlr, WebGrease, System.Web.Optimization, etc. Doing that fixed my error, but it was not the solution I was looking for.
After some back & forth with Syncfusion support, they stated that they were able run the project on their machines that were using Visual Studio 2015. They stated that the problem must be on my machine.
I keep a very clean dev machine, only installing software that I absolutely need and nothing else. I was certain that the problem wasn't on my end and was in denial about the whole thing.
I tried to repair Visual Studio 2015 as well as uninstall/reinstall Visual Studio 2015. Neither worked.
Yesterday, I bit the bullet and wiped my machine and reinstalled everything. Now the project runs without error.
It's not the fix anyone wants to hear, but it is what ultimately solved my problem.
Cliff's Notes: I had the same problem. The fix ended up being wiping my machine and starting from scratch.