All the Recently worked projects will be available in Visual Studio Opening window.
Even if the projects are removed from our file explorer, those names will exist in the VS Opening Window.
I'm able to delete those recent projects entries/history one at a time by using this option:
My Question is:
How to delete all those history/entries at a time to see like the below window (screen)?
I have posted the same question on Super User and that answer helped me to clear the recent projects history after opening the Visual Studio IDE.
Also, while searching for this information, I learnt a lot from many other solutions like How many recent entries we have to keep when opened the VS and the other ways to delete them.
One of the references contains many ways to this issue is C#Corner Article.
But the ClearRecent extension in Visual Studio is a better solution as given in the above answer.
Related
I am building a project using ASP.NET MVC CORE. I want to be able to run my project and see the impact of my code changes in real time, i.e., I see the changes on the browser as I tweak things in Visual Studio 2022.
What extension do I need for this?
I realise this question has probably been asked before but I haven't been able to find the answer here or through Google.
I discovered the answer to this question this morning. I only need to hit F5 in the browser and the code changes will show.
I know there are already many threads on stackoverflow about this problem but they are all old and all the solutions work only for Visual Studio 2012/13. I'm using Visual Studio 2015 and I have the same problem.
I'm learning ASP.NET from a book and I've installed everything they have, and created the project exactly as they have but still can't see the 'Add Controller/Add View' options.
I've tried altering my ProjectGuids and that stuff but it is all incompatible since every solution I've found online is regarding older versions of Visual Studio.
Any ideas?
I'm working on a few Umbraco projects that use MVC4. The MVC intellisense doesn't work within visual studio and I get lots of errors underlined. But when I run build the project, I don't get any errors, and when I run the site everything works fine.
I'm using Visual Studio 2013 and I created a new MVC4 site and compared the web.configs within the Views folder and they're identical.
I'm pretty sure it's not a code problem as my colleague is using the same code and he doesn't have this problem.
I've just done a fresh install of Visual Studio 2013.
Any ideas?
This could be a clue:
When I hover over #Htmlit tells me that my HtmlHelper is a System.Web.WebPages.Html.HtmlHelper instead of a System.Web.Mvc.HtmlHelper
The common one is to ensure that it is switched on (Visual Studio menu: Tools > Options > Text Editor > All Languages (or C# if you want it just for that language) > Tick "Auto list members", Untick "Hid advanced members", tick "Parameter information")
Once you've checked this, sometimes if you're using one HDD on Windows, because the disk has its bandwidth used up (particularly if using ReSharper then you need two or more drives ideally with the pagefile going to the non-OS drive I find). This is the case if the red lines do disappear after up to two minutes of not touching the IDE.
Finally check you project's references folder to make sure where the paths for your includes are coming from and that Visual Studio has permission to read from there. Permission issues cause all manner of problems I find, so when you launch VS, right click and choose "run as Administrator".
Hopefully one of these solves your problems. If not, then please update your question to explain how you create your project. Do you create an empty site or an MVC site? Do you then use Nuget to install Umbraco through the Package Manager Console like this?
Install-Package UmbracoCms
I'm working on a project in Visual studios 2013. I was trying to figure out how to do something and was recommended to look at another project on TFS that does something similar. When I got latest version of this other project, I found out it was made in VS2010. It migrated it to VS2013, and locked the file to me. I undid the changes because I don't want to modify this other program. I was unable to find a way to open that file without it trying to lock the file to me with migrating to VS2013.
As an attempted solution, I copied the file elsewhere on my computer and tried opening it without connecting to TFS. I assumed this would allow it to migrate to 2013 without updating the database. It still had issues and gave me this error: Solution file '%s' cannot be migrated because the solution cannot be checked out from source code control. To migrate the solution, make sure the solution file can be checked out and re-open it.
How can I open this solution without updating the TFS solution and locking the file to myself?
I just ran into this same problem. I checked the permissions on the solution files I was trying to open and saw that it was set to 'read-only'. I deselected read-only and the solution opened.
If everyone else is using VS2010 with Service Pack 1, then upgrading the solution isn't a problem. People will still be able to open it in VS2010 SP1, even if you check it in. See the Visual Studio 2013 Compatibility notes on MSDN for specific things to watch for.
Alternatively, after checking the files out but before opening the .sln file, create a copy of it in the same folder calling it MyProject2013.sln (for example). Add this new solution to source control using Source Control Explorer and then open it, letting Visual Studio upgrade the .sln file as it would normally. The 2010 .sln file will be left untouched and you should be OK to do what you like with the 2013 solution.
Disclaimer:
I apologize if this is not an appropriate question to ask here... I saw some similar ones that were answered on here but not this exact question.
Question:
Anyway... Does anybody know how I can delete a workspace in Visual Studio 2003? I brought a project over from source control but now I'm trying to change the local path that it gets brought into, but the field is now grayed out.
Thanks in advance.
I got it... VS2003 doesn't appear to have a very good interface for TFS, so I discovered that I'm able to blow away the workspaces in VS2008.