At restart the PHP explore project is collapsed. I cannot find any setting to keep it from collapsing each time I restart. The window has only a "collapse all" functionality. For a deeply branched project is really useful to start where you left from, like in Netbeans.
Related
I turned off lightweight for solution inVS2017, in Tools->Options->ProjectsAndSolutions->General,
But projects is loading in lazy mode (only when i clicked on the project):
Also i clicked disable light weight solution load mode in the solution context and it doesn't help.
It is hard to work in VS with such bug, because i need to open all 62 projects manually to start working/. Without these 62 steps, code editor thinks that interfces and classes declared in uloaded projects do not exist.
How to turn off the 'lightweight' mode?
Right click on solution, go for “Disable Lightweight Solution Load” context menu option and then re-open the solution.
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
How do people generally deal with TFS when you've got to work with multiple solution files? If you've got one instance it's easy because you can always go to that window for the source control explorer, pending changes, check on builds or work items. But when you have 4-5 solutions, it becomes tricky to deal with. You might expand some folders or check some pending items on one VS instance but you have to remember which one you did it on.
Having a separate instance dedicated just to TFS tasks is tempting, but there's only one window state for the whole program. If that instance is closed last, all instances will come up with all the TFS windows open.
How do other people deal with this? Can you use separate profiles somehow and cordon off a "TFS" instance of Visual Studio?
Use the Pending Changes window. View -> Other Windows -> Pending Changes. This has a toolbar option to show only those changes pending for the current solution also. It's the last toolbar button in the Pending Changes window. I usually make this a full document in VS and then memorize the keyboard shortcut to it: ALT+V, E, H. Obviously you could bind your own shortcut, but what fun is that.
Eclipse has a similar perspective/view to Pending Changes, but it's name escapes me and I don't have my Ubuntu VM up at the moment.
Solution Explorer and Source Control Explorer are definitely not my recommendation for check-in activities. I personally like to clear out all of the checkboxes on Pending Changes and then Diff each file. This keeps me from A) waiting too long before a checkin (it sucks to compare 20 files 1 by 1) and B) avoids checking in a change I didn't intend.
If you have multiple instances of Visual Studio open at one time (which I'm not quite sure why you would need to do this), your changes are "synchronized" across all instances of Visual Studio. Don't do your check-in from the solution explorer, do it from the Source Control explorer, then you're sure to get all your updates in a single check-in.
You might find VSCommands useful when working with VS/TFS - it can be configured to display the Solution and TFS Branch name in the title bar, this indication is invaluable when working with multiple instances of VS (or multiple branches of the same project).
My "Start debugging" button and element menu are greyed out... but only on one of my projects (an ASP.NET website). I have no idea what I have done to disable it.
I already checked everything in the Property page of both the solution and project. I even compared it to another project, but nothing seems to do the trick... maybe I missed an option ?
It sounds like your startup projects are all set to "start without debugging", since that would cause the button and element to grey out.
This can be fixed from Solution -> Set StartUp Projects.
Is it a startup project? You can only debug projects that can actually be started.
Right click on the project and click properties. Then click on Start Options (or something similar) to see the settings. If it's an executable project, you probably want to choose the option that will start the project output.
If you're able to start the project, you can usually attach the debugger using Ctrl+Alt+P (Or choose Attach to Process from the Debug-menu) and then choose the process from the list that comes up.
Do you have the COM+ Event System service running?