I am trying to stop using ReSharper we got too slow for me. One functionality that seems missing is the ability to navigate through the previous edit locations. Is that not available?
There is Ctrl+Shift+Bkspce for Edit.GoToLastEditLocation but I can't seem to be able to go further.
Related
I was coding with razorpages when randomly about 2 days ago the razor pages now display boths the cshtml and cs right away. earlier I could expand the cshtml to get to the cs file and i think it was a more compact that way
i think its options somewhere in tools->options->environment () but there are so many
after a few different google searches I found nothing helpful.
here is a picture of the problem:
earlier I could expand the cshtml to show the .cs files now i just see all of them and its kind of overwhelming.
enable file nesting in solution explorer
They're not being nested, is all. It's literally two separate files, Visual Studio just recognizes that it's a Core project, and then shows them nested, since it understands that they're related. If that's not happening, then that means Visual Studio doesn't recognize it as a Razor Page, which could be a problem with VS, the project, or something else entirely. It's essentially impossible to say what the issue might be, so you'll just need to try stuff. A few things I can think of to try:
If you're not using VS 2019, upgrade. Ultimately, this is part of the ASP.NET Core tooling, and best version of that is always going to be in the latest release.
Verify that you solution is building correctly. You might also consider deleting all bin and obj directories and rebuilding to ensure the build is truly up to date.
Close Visual Studio completely and re-open it. You may consider restarting as well. (You've probably already tried this though).
Try running Visual Studio in "safe-mode", which essentially just means disabling all the extensions you have installed. You can either manually disable all your extensions and then restart or close Visual Studio and start it via the command like with devenv /safemode. If this fixes the issue, then there's an extension causing issues. You'll probably need to just disable each one by one to see which on is causing the problem, and then either remove it or see if there's an update that corrects it.
If all else fails, repair Visual Studio. Run the intaller, and click the "More" link under the installation you're working with. Then click "Repair".
I have been working in both Visual Studio 2015 and 2017 with TFS 2015.
I will often have issues where, when I add a new file, the window pops up to add the file to TFS automatically, but it just sets there. I try to click Cancel, and it just sits there saying "Canceling...". I end up having to kill the process and reopen. It usually works for a little bit after that.
None of my coworkers, using the same versions of VS and TFS, have this issue.
Any help would be appreciated. It is starting to get exhausting to deal with.
Try to clear the version control cache on your machine. It should be located in:
C:\Users\<yourusername>\Local Settings\Application Data\Microsoft\Team Foundation\. There will be numbered folders (6.0, 7.0, etc) in there, with Cache subfolders. Try deleting all of those.
It's going to be very difficult to give a definitive answer; the best anyone can give you are suggestions.
When i open Visual Studio i see on the top buttons: File, Edit, Selection, View, Go, Debug, Taks and Help. Whatever button i opened i couldnt find any restart button. I searched on the google and also on this website what should i do. I got few same answers- that i should download some sort of restart extension (i am new in programming, so im not quite sure what is the name of it). When i dowloaded it and inserted it in Visual Studio, there was this sentence thats says that VS wont open the file because its too large ( i think that there were another 2 reasons ). I googled that and still couldnt find anything helpful. In all of this searching i found out that this is might connected to option tools
and customize
but i cannot find them aswell. Can anyone tell me roughly what might be the problem? Thanks! :)
If you're looking for some way to restart visual studio, say after installing some plugins, all you need to do is Close and Re-Open it. There is no specific restart button
Is there a way to navigate between two Visual Studio Solutions?
For instance, I have two solutions: One with a various utility code and one comprising my actual app. When I hit F12 in the app solution, I am taken to a 'metadata' file, with function definitions only. Ideally, I would like to taken to the file in another instance of Visual Studio with the utility solution open.
Currently, I copy the thing I am seeking a definition on, then switch to the other instance of visual studio and conduct a search. Just curious if there's a faster way of doing this.
Not as far as I know. The only workaround that I know is to add the "utility" project(s) to your app solution. If you don't change them much VS won't try to recompile them all the time, and you'll have access to the code.
Using ReSharper and presumably a combination of the debug PDBs (generated with your Utility class build) then you're able to get right into the source of your libraries using F12 without needing to go to the other instance.
Is there a way to tell Visual Studio 2005 to just ignore source control binding when opening a solution? I sometimes need to load a solution for which I don't have access to the source control server, but Visual Studio insists on trying to connect anyway, meaning I have to click "temporarily work offline in disconnected mode" for every project in the solution (of which there are about 20) as it loads. For some reason, it also tries to check each project out immediately after I've told it to work offline, so I have to click past that dialog box too.
As I will never need to edit anything in this solution, is there any way I can open it and have Visual Studio just ignore the fact it has source control bindings in it?
Edit: Ideally, I'd like a way to do this without having to change the project/solution files. They change fairly frequently, so I'd have to redo any changes every time there was a new version (otherwise I'd just unbind them once and it wouldn't be a problem).
Thanks for the replies so far.
The source control bindings are stored in Visual Studio solution file (.sln). For TFS for example, it contains a global section for TFS information and the solution projects added to TFS. You can edit the solution file to remove these bindings manually. I would suggest making a copy of the solution file first. However, I would recommend removing bindins via Visual Studio. Open your solution and go through the offline scenario. Then go to File/Source Control/Change Source Control (VS 2008) to bring up the UI that shows you the source control bindings in your solution. There you can manage the bindings including unbinding them. Once unbound, the next time you open the solution, VS should not have a need to access the source control.
I've been looking for a way to disable Integration between SourceSafe 2005 and Visual Studio 2008. We are forced to use SourceSafe being in a corporate environment and all. SourceSafe is fine on its own if you treat it like a baby. As soon as you try to do anything approaching useful it starts to break. God forbid you try to use the integration with Visual Studio. Being that I didn't want the "Bindings removed" so that it doesn't confuse other devs on the team I needed to be able to tell Studio to ignore the solution and project bindings and continue on it's merry way.
I followed the registry hack suggested in the following post
Removing SourceSafe Integration from Visual Studio 6
Studio did what I wanted...sort of. It removed the SourceSafe integration. However when I opened up a source controlled solution it asked me if I wanted to remove the bindings.
"the projects will be treated as not under source control"
No I don't want you to remove the bindings from the files, I want you to IGNORE them. This dialog pops up every time you open the solution/project file and there is no way around it.
My solution at the moment seems to have worked...for now.
File->Source Control->Change Source Control...->Disconnect
I hope this helps anyone else in the position of having to use SourceSafe but can't remove the bindings from the files themselves. WHY, Microsoft, WHY would you put the bindings in the files themselves?
/rant