How do I transfer the window layout in Visual Studio 2010 from design mode to debug mode? I have a window layout I am fairly happy with in design mode, and would prefer to not have to do all that work all over again just to change a few details in it.
I found some questions that were kinda-sorta about this, but not quite.
Any suggestions? I know about import/export settings and use it religiously (switching between single-monitor and dual-monitor window layouts) but that doesn't really help me in this particular situation, as far as I can tell.
VS shell's ViewManager serializes the window profiles in your %AppData%\Microsoft\VisualStudio\10.0 directory in *.winprf files (which are basically just XAML files).
There are 5 profiles: Debug, Debug-Fullscreen, Design, Design-Fullscreen and NoToolWin (when no solution is open). You can experiment with replacing your Debug*.winprf with your Design*.winprf.
Please note that any manual modification of these files is entirely unsupported, so if you break something, you're totally on your own here.
Export your settings:
Choose General Settings/Window Layouts (in VS 2013) and save the file.
Open the file in an XML editor (or whatever... it's an XML file)
Find /UserSettings/Category/Design/WindowProfile and copy the entire node.
-- This assumes your Design view is the one you want to use for both modes.
Find /UserSettings/Category/Debug/WindowProfile and replace it with the one you copied from Design.
Save and re-import.
I have one of these settings files for home, remote, and office.
Related
When an app stops in debugging mode and I make changes to the code
Is there a way to save the code with the changes, without stop the app?
Although the VB6 IDE does not provide this natively, an add-in for the IDE called MZTools has been around for ages which adds this feature.
Personally I've used MZTools 3.0 for many years, and this works really well.
This is what its help system says:
Shortcut To Save File At Debug-Time
The Shortcut To Save File At Debug-Time feature allows you to define a keyboard shortcut (Options
window, Shortcuts tab) to save the selected file at debug-time. The
Visual Basic IDE does not allow to save files at debug-time, but often
it is useful to save the modifications that you have made to the
source code at debug-time.
Remarks:
This feature is not available in the VBA version of MZ-Tools. This
feature only works at debug-time. Since Visual Basic disables buttons
or menus of add-ins at debug-time, the only way to save a file at
those times is through a keyboard shortcut. The file must be
previously saved at design-time, that is, MZ-Tools does not prompt for
a name to save the file (it shows an error message instead).
This is the options window for how I have it configured locally:
Note that originally MZTools was free in version 3 and later they switched to a paid version; if I hadn't gotten v3 originally however it would be well worth paying for, not only for this feature.
The short answer is you can't.
If you make the project before the crash, maybe this piece of code can be found in a ".tmp" file. But searching in .tmps is often a waste of time.
I particularly always force myself to stop the debug and save my progress.
And I always use this setting which forces me to remember to save:
Background
I am working with VB6 legacy code and I am using an external editor because of the features that it has. Unfortunately, those changes aren't refreshed in the IDE because VB6 doesn't monitor loaded code for changes.
I have done some extensive searching on the subject including looking for alternative editors, a fairly exhaustive internet search including following all of the links on this StackExchange link and haven't found a way to refresh the code window to reflect the external file changes.
My company doesn't have access to the latest edition of Visual Studio and will not be purchasing it anytime in the near future. Until then, there is code to fix.
Question
Aside from restarting the program are there any methods that can be used to refresh the code displayed in the VB6 editing window?
Check out vbAdvance add on. It will prompt you to reload source file in case of external modification.
I think a found one possible solution.
The MZ-Tools set has an function called Reload file from Disk. It also allowed me to create a shortcut for this function through the MZ-Tools options menu, so I assigned it to the shortcut keys of my choosing.
It's a solution, but I'm still looking for anything that might be better.
Question:
Is there a way to make all files that are open in visual studio be highlighted in the solution explorer?
(I know there is a filter that you can filter it to show only open files but this dos me no good sense I am looking for a file that may not be open, I am not even sure what the name of the file is until I open it up and say there it is.)
Example Imagined GUI result: (Different colors are fine)
https://docs.google.com/file/d/0B31DHM9TkK99S3pWSms3QXR2Qk0/edit?usp=sharing
(image of what i am thinking, can not post image right now)
Solution Explorer
-Solution
+Stuff
+More stuff
-Code
+MyOpenFile.cs (Highlighting)
+MyNotOpenFile.cs
+MyOtherOpenFile.cs (Highlighting)
+MyCurrentlyOpenFile.cs (Highlighting, maybe a different color)
(the one with the red under line could be the active tab)
Background:
I don't know if this happens to any one else, but I have been doing it a lot for years now. While working on something I go to open up a file in the solution explorer and it turns out that the file is already open, and so visual studios just sets that file as the active tab. If I were working In just one window that would be fine, but I have few tab windows open beyond the main window and they are normally on a diffident monitor, so when the tab becomes active I do not see it at all, because it is not on the main window. This is even worse when I go to preview a file.
Icing on this cake:
-If it would have an option to highlight the parent nodes of open files, i the example "controllers" and "content" folders would be highlighted as well.
-If there was something that would do this for vs 2010 as well would be great.
I am looking for all most any thing at this point, an extension, a style sheet some where to edit, or as a last resort a good reference to a "How to code Extensions for Visual studios" website.
Edit:
As a point Of clarification I am not looking for a way to locate a specific file in the solution explorer, I am looking for a way to make the files that are open look visually different, so that I know to look around a bit before thinking that VS2012 is crashing or the file is messed up.
try an extension called VS commands. It will help you locate the files in solution.
Or this extension:
http://visualstudiogallery.msdn.microsoft.com/d0d33361-18e2-46c0-8ff2-4adea1e34fef/
My VS2010 environment has the start page come up if I'm not opening a solution. From there, I can open one of the several items on the recent projects list or I can open a project from the link/button in the upper left. When I do that, I get an Open Project dialog that's pointed at my C:\workingvss (which is a convention that everyone on my team follows for where our code lives locally). But I virtually always want to browse to the project in a VSS database and I have to scroll up in the left-hand pane of the dialog to bring 'Microsoft Visual SourceSafe' into visibility. It seems dumb that I can't make it just start at the top of the pane, but if there's a way, I haven't been able to figure out how.
So I'm turning to you. Is there something I can do to avoid this click and drag every time I want to open a project?
I realize it's defaulting to the Projects location parameter set through Tools > Options > Projects and Solutions > General. But I think I need to leave that as is because I do want my stuff saved to that location during checkout.
I also think that if I removed ten (in my case) folders from the root of my C:, the left pane would show my VSS option, but I don't think that's even possible in this machine's case and not a reasonable solution in any case.
My question is related to, but not a duplicate of, How to change the default open file dialog path.
Thanks for your time!
This isn't a great answer, but it's my current no-tech work-around. If I make the Open Project dialog large enough to accommodate all of the lines it wants to display, then my VSS line is visible and I don't have to navigate to it. Luckily, Visual Studio remembers the size from use to use.
Do you wish to reload the project? Where's the Reload All option.
Vote for this question and hopefully MS will implement a fix in VS2020.
With pleany of projects in a solution I for one dread doing an svn update.
This has been an issue from VS2003 but after a decade of clicking mindlessly on buttons it's getting on my wick.
Does anyone have a hack / registry entry / secret way of saying yes short of saying ignore (quick), closing and reloading the solution?
There are a couple of options you can tweak for this scenario. Both are under the Documents Options
Tools -> Options
Environment -> Documents
The first option is to just uncheck "Detect when files changed outside the environment". This will stop the reload dialog but will force you to manually reload.
The second option just below it is a bit better "Auto-load changes, if saved". This will just automatically load the changes without prompting you for every project.
Personally though I would go a slightly different route here. The problem is occuring because your managing your source code control outside of Visual Studio. If you switched to using an addin to manage within Visual Studio it would remove these problems altogether. For svn there are several free packages available including Ankhsvn which is fairly popular
http://msdn.microsoft.com/en-us/library/ms165643(VS.80).aspx
DetectFileChangesOutsideIDE
Get/Set (Boolean)
Determines whether the environment automatically reloads files opened in the IDE when the operating system notifies the IDE that the files have been modified on disk.
EDIT:
Some clarification, as that page isn't immediately obvious.
Tools Menu->Options -> Environment->Documents->Uncheck Detect when file is changed outside the Environment