If I click on something (that is click and let go) in the solution explorer and move the mouse too quickly on two quickly or click on something else too soon, Visual Studio interpretes that as a move. I'm hooked up to Visual Source Safe, so most of the time it asks me if I'm sure. But every once in a while it doesn't, and I have no idea the file has been moved/copied. As a result I get compiler errors (or worse runtime issues) that are nearly impossible to track down. Is there a fix to this? Any suggestions? It is very annoying.
Try the VSCommands extension
They have a "Prevent accidental Drag & Drop in Solution Explorer" feature
Related
While in debug mode, the solution explorer has a Script Documents section. It is expanded by default. As the debugger runs, new ScriptDocumentxxx poll.txt files are added to this section. As I am navigating the explorer files, the adding of these new line items causes the entire contents of the explorer to shift downward. This is quite annoying if I am trying to find a file or trying to click something. I can collapse the section manually, but I'd rather not have to do this all of the time.
Right click the projects you are interested in working on and click on 'Scope to this'. This will hide everything (Including the scripts folder) except those projects you selected.
I got annoyed enough with this that I turned off JavaScript debugging. If you are willing to go that far, the scripts are gone.
The path for turn of JS debugging is:
Tools -> Options -> Debugging -> General -> Enable JavaScript debugging for ASP.NET (Chrome, Edge and IE) (Visual Studio 2017 and 2019)
Note: This method does not prevent you from stepping though JS in the Chrome inspection tools so you do not lose that ability. You lose both the scripts (of course) and that new Chrome window that pops up when you launch the debugger.
Yes, there is.
IIS Express > Script Debugging > Disabled
Right click then 'Scope to This' to hide everything but the project in the solution you want to view.
Click on the Home/House icon to reverse it.
Yes there is. One way is to create a visual studio add-in or extension which monitors the solution explorer tree and collapses the "script documents" -item if it is expanded.
If you need code samples and/or a fully functional add-in just let me know. You have Visual Studio 2013, ay? Is it the express edition or what?
This is confirmed bug in VS 2019. Just Microsoft is not so fast about fixing it.
https://developercommunity.visualstudio.com/content/idea/351537/provide-a-way-to-prevent-the-script-documents-fold.html
Is there any way to "pin" a document into a fixed position? I want to keep the "Source Control Explorer" tab on the far left and always open new documents to the right of it.
However, VS 2010 tends to add documents at the very left. I want "Source Control Explorer" on the very far left so I always know where to find it.
I can think of two different ways of doing this. The first one uses only options that are built into Visual Studio 2010 but is more limited and may not work 100% of the time. The other one requires that you install an extension, but is much more powerful, dependable, and even adds some other useful features.
You can configure Visual Studio to always open new tabs to the right of existing tabs, just like a web browser would. (Personally, I prefer this option.) To do this, open the options dialog (Tools → Options), expand the "Environment" category, click on "Documents" and check the "Insert documents to the right of existing tabs" box (see screen shot).
The key to making this work for you is to ensure that you always open the Source Control Explorer first before opening any other code windows, and then never close it. That way, it will always be on the far left, and all of the code windows you open will be inserted to the right of it.
Like I mentioned above, the advantage of this approach is that it uses a setting built into Visual Studio and doesn't require that you install anything extra. All you have to do is flip a switch. The disadvantage is that it isn't 100% dependable—if you close the Source Control Explorer and re-open it, you'll have to remember to drag it back into position at the far left or it won't be there when you go to look for it.
You can install Microsoft's Productivity Power Tools extension (available from the Visual Studio gallery), which adds the ability to pin tabs (among lots of other neat features) to the VS IDE. There's a great run-down of the features added specifically to the document tab well here, but the feature you're most interested in is pinned tabs. You can even show pinned tabs in a separate row!
This is as close to a perfect solution as it gets, but it does have the disadvantage of requiring you to install something extra. In some environments and for some people, that can be a deal killer. Too many extensions can also slow things down, and later versions of Visual Studio often seem to be slow enough already. (Though, for what it's worth, I use the PPT extension on about half of my VS installations and I haven't noticed that it has caused any significant issues.)
It's basically in the title.
Whenever you "select all" in the Visual Studio code editor, the editor will scroll down to the bottom of the file. Is there a way to prevent this?
I'm using Visual Studio 2008 at the moment, but this applies to all versions.
No, you cannot change this behavior.
Microsoft has been aware of this since at least VS 2010, but either doesn't think it's a bug or doesn't think it's important enough to fix.
From their response to a 2010 bug report filed on the issue:
We unfortunately do not plan to change Ctrl+A's scrolling at this
time, so we're unfortunately resolving this issue as Won't Fix for VS
2010. However, it will remain in our database to be revisited for a future release of Visual Studio.
Source: Microsoft Connect
A quick Ctrl-Z-Ctrl-Y will get you back to where you were. If you tend to do a Ctrl-S Ctrl-A Ctrl-C a lot then just get used to this whole chain instead: Ctrl-SACZY. Or, create a macro: https://msdn.microsoft.com/en-us/library/a0003t62%28v=vs.90%29.aspx
I was struggling with this myself, but the "undo" suggestion gave me an idea and I feel kinda dumb for not thinking of it earlier. Visual Studio includes "Navigate Backwards" and "Navigate Forwards" buttons (CTRL-, and CTRL+, respectively). So after you finish selecting and copying, simple click the navigate backwards button or type CTRL- and voilà! you're back where you were.
I know it doesn't stop the scroll to begin with, but at least it puts your cursor back exactly where you left it!
in Visual Studio 2008 it was possible to open a collapsed #region by simply double clicking somewhere behind (to the right) of the #region.
Now in VS 2010 you have to double click exactly the #region, double clicking behind it just selects the #region.
I've browsed the options but didn't find anything helpful and neither did google help.
Does anyone know of a way to switch back to the old behavior?
Thanks,
Florian
In Visual Studio 2010 the editor has been rewritten from scratch. It is quite likely that they just "forgot" to re-implement this functionality, thus causing a regression. If you feel strongly about bringing it back, I'd open a new bug at https://connect.microsoft.com/visualstudio/feedback
I don't think you can do it with the mouse anymore. Your best alternative is Ctrl+M, M (that toggles the current outline section).
When I open *.ashx files in Visual Studio, I don't have the helpful "Go to Declaration" context menu when right-clicking on a function.
How can I restore this functionality (this is a new install)?
Thanks very much.
Click on the text you want to go to and key F12 if it's not showing up for you.
Much like Windows Operation Systems need to reboot when things start breaking down, Studio sometimes needs a restart if that doesn't work.
Obviously this doesn't get your menu item back, but it's a fix that you might prefer over selecting that from the right-click mouse menu.
This is a shot in the dark since I do not work with ASP-related stuff.
Short Answer
If your *.ashx files belong to a project, open the project first.
Longer Answer
Most of my work in Visual Studio 2008 is with C++ and C# code. If I open a .cpp file or .cs file in VS2008 independent of the project it belongs to, VS2008 doesn't give me the Go To Declaration context menu either. When I open files independent of the project they belong to, VS2008 (or any Visual Studio version for that matter) is little more than a glorified editor. To get the benefit of Go To Declaration and other features, e.g., Intellisense, I have to first open the project and then open the file from within VS2008.
Alternate Answer
If you are already doing this, you might try deleting the .suo file in your project directory and letting VS2008 re-create it.
Apology
Sorry if this was simply stating the obvious. I know I've been frustrated at times when I've opened a file outside the context of its project only to realize what I want to do requires me to open the project anyway. Someone new to Visual Studio might not realize the project is sometimes required.