I've reinstalled Visual Studio Mac, deleted all bin and obj folders, cleaned and rebuilt my solution.
But I can't navigate to symbols. It says...
Cannot navigate to the symbol under the claret.
Any ideas? Is there a stash of VS data somewhere that I can delete with extreme prejudice?
Have you already searched your hard disk with "Visual Studio" or something? Maybe there're some files somewhere.
One project appeared twice in the solution file. I removed one of the references.
Related
Why would VS2019 (with VisualGdb) refuse to show added files the solution explorer?
I found some workaround, i will post as an answer. But i'm still quite interested in the explanation of the underlying problem.
Additional info: opening the project file (.vcxproj) shows that the files are actually added to the project, only they are "invisible" in the project explorer.
I'm not sure, if this issue is VS-related or VisualGDB-related, or even layer-8-related, but hopefully this answer will help some people anyway.
So after trying many things not leading to success, i found this workaround:
In the project file (.vcxproj), i actually found entries for theses "invisible" files, and after deleting them and re-opening VS, i added these files again in the soluton explorer. Only this time, they correctly showed up in the solution explorer.
Weird: a compare tool showed not the slightest change in the project file, so there got to be some underlying issue.
I'm running Visual Studio 2019 through Parallels on a Mac and my solution is not finding any references. I can browse to the location of the references on the Windows' C drive so I know they're there. But in the properties window of the project in VS, they all show as "The system cannot find the reference specified"
What's really weird is I can remove the reference, click "Add", browse to the DLL, select it, add it back to the project successfully, but it still shows as "The system cannot find the reference specified".
I tried the "update Nuget" tool which also just sort of hangs and doesn't do anything.
This has to be some sort of config issue with Parallels, but I'm not finding much info on how to resolve.
I manually copied the "packages" folder from the same solution on a real Windows10 machine into the "packages" folder on the Parallels/Windows10 and now everything seems to work.
What I don't get is that some of the references that were not being found are not even in that "packages" folder (!)
Yet doing that made VS see all the missing refs.
I am developing a C# project in Visual Studio 2019. I've read that it should produce .csproj.user files automatically, but it is not. How do I force Visual Studio to produce a .csproj.user file? Thank you.
As mentioned by Hans Passant above, this file is created when there exist user-specific settings. Typically it is created by changing any of the Project->Properties->Debug settings to non-default values (i.e. specifying command line arguments or setting an absolute path for the working directory).
However, as I already have pointed out in the other question, I believe you should not commit this file and find out why you have problems without it. Or rather, why VS adds some relevant information to this file instead of the main csproj.
In my case strangely some references that should have been in the SDK project had found their way into the csproj.user file. I don't know why this happened.
Once I put the references back in the SDK project I had no need for the csproj.user after all.
I kept having this annoying thing stop me from building my project over and over again even though I searched for years on stackoverflow trying to find solution but none of those I tried works. The problem just kept coming back!
The file having problem is system.web.mvc.xml, wont let me delete even I am the administrator.
Im running MVC 5 projects.
tried to close vs 2012 first then delete files : fine for the next build but then it came back after 1 or 2 builds
tried to un-check read-only option to my entire project folder : fine for the next try but , you know.
tried to close and re-open : same as above
tried to run administrator : same as above
So anyone have really get rid of this? like ever?
Same with me..
Finally I did this trick and work for me:
Close The Solution - Close Visual Studio. And Reopen Visual Studio and solution
Copy System.Web.Mvc.dll from bin folder to new fresh empty folder, I make Lib folder under solution.
Remove read only at the dll
Remove System.Web.Mvc from project reference
Re-add System.Web.Mvc.dll (the dll copied at Lib folder)
__
Hope This Help
Regards
i have created a windows service in visual studio c#.net ,and i am trying to create a set up and deployment for the service, when i am buiding the windows service project ,it is successful
i have added the Project Output Group as Primary Output with windows service project.
i have also added the custom action to the set up project,
when i try to build the set up project it displays"An error occurred while validating. HRESULT = '80004005'" i also noted there is nothing in the detected dependencies folder.
I had the error code 8000000A, so it might be different, and I'm not sure if this is any help for your problem. But re-adding references did not work for me. However, what worked for me was removing the .suo file (next to the .sln) and (re)building again.
(It might have been caused by accidentally opening a Visual Studio 2010 class library in a Visual Studio 2008 comapct project. I am not even going to try reproducing this!)
Removing the .suo will make you 'loose' your open files (and maybe some other settings?), but IMHO that's just a small sacrifice(?).
I just hope this will save someone some time...
I've just had exactly the same issue with a WinForms project. I had several projects in my solution, they would all build without an issue except for the set up project.
I overcame this by removing all the references to the other projects in the solution in the main project (the one that was being set as primary output) and then re-adding them again by going to add reference >> project. Once I had re-added the references to the other projects in the solution, the project dependencies re-appeared and all built fine.
Hope that helps
Richard