i just installed visual studio 2010 and it is not opening any projects .I can make projects but i can not add any file in it and also it is not opening recent projects.
I am stuck here , kindly cooperate with me!
OK, sounds like the installaion got munged up.
first obvious questions: do you have any code that has actually been saved?
If "yes," copy that code to an alternate location, and use the simplest solution: use the Windows Control Panel to deinstall the MSVC instance and reinstall. If no code saved, just de-install and reinstall.
That's the obvious answer. You may also check the location for the project files, and the settings Visual Studios uses.
from the toolbar, click "tools".
From the drop-down list select "options"
Within the displayed list, scroll down to "projects and solutions"
expand that list (click on the little "+" box)
3 locations will be displayed.
Make sure you have write permission to all three locations
all the check boxes should be selected. Especially the one marked "save new projects when created"
click "OK" to accept the changes
Related
Modules in MS Office Project Explorer have always been grouped into forms, modules and classes, with "pluses" that allow to collapse or expand the groups. Either I have pressed some random hotkey, or the latest MS Office update messed it up, BUT now all my modules are just a list sorted by name (see the screenshot). It's the same in all Office programs. What has happened, and is there a remedy to this? I want my groups back :-(
I looked through all settings in VBA Editor, but I never found anything related to the problem.
Press the Toggle Folders button in your Project Explorer:
Alternatively use the Toggle Folders button in the context menu of the Project Explorer.
I was using the built in file compare utility in VS 2012 to compare two files in source code history. It did something to cause one side of the comparison to go away and I have gone insane trying to figure out how to bring it back. How do I make it so both files show side-by-side?
I have already tried: Closing all windows and re-opening them, restarting VS, Deleting the .SUO file and reloading the project. - No dice.
The toolbar at the top of the window will have a dropdown list button that looks like two papers side by side. Click on the button and select "Side-by-Side-Mode".
Choose the "Side by Side mode" in the tool bar.
After a lot of editing of my build templates (I recreated them in 2012 to avoid any issues.. but then I suppose I got sloppy and simply copy/pasted whole blocks from the old workflow, and I suppose that must have completely destroyed my versioning) I now have problems with just one build definition based on the build template I edited. (All other ones seem to be working fine.. so I suppose that one got a problem during all the editing. (I was mostly adding and removing Version=11.0.0.0 to the assemblies in the build template))
The exact error is:
Parameter Items to Build: cannot convert value
'Microsoft.TeamFoundation.Build.Workflow.Activities.BuildSettings' of
type Microsoft.TeamFoundation.Build.Workflow.Activities.BuildSettings
to type
Microsoft.TeamFoundation.Build.Workflow.Activities.Buildsettings,
reset to default.
It is displayed when editing the build definition and wanting to select the project/solution and configuration to build. Actually, with this now I cannot save (without error) any more and the value gets deleted again.
(I am using VS 2012 (VS 2010 still installed) against TFS 2012.)
How to fix?
Open up your XAML and look at the xmlns's on the Activity root node:
Here's a snipped version of mine:
<Activity mc:Ignorable="sads sap sap2010" <!--Removed-->
xmlns="http://schemas.microsoft.com/netfx/2009/xaml/activities"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
xmlns:mt="clr-namespace:Microsoft.TeamFoundation;assembly=Microsoft.TeamFoundation.Common"
xmlns:mtbc="clr-namespace:Microsoft.TeamFoundation.Build.Client;assembly=Microsoft.TeamFoundation.Build.Client"
xmlns:mtbw="clr-namespace:Microsoft.TeamFoundation.Build.Workflow;assembly=Microsoft.TeamFoundation.Build.Workflow"
xmlns:mtbwa="clr-namespace:Microsoft.TeamFoundation.Build.Workflow.Activities;assembly=Microsoft.TeamFoundation.Build.Workflow"
xmlns:mtbwt="clr-namespace:Microsoft.TeamFoundation.Build.Workflow.Tracking;assembly=Microsoft.TeamFoundation.Build.Workflow"
xmlns:mttbb="clr-namespace:Microsoft.TeamFoundation.TestImpact.BuildIntegration.BuildActivities;assembly=Microsoft.TeamFoundation.TestImpact.BuildIntegration"
xmlns:mtvc="clr-namespace:Microsoft.TeamFoundation.VersionControl.Client;assembly=Microsoft.TeamFoundation.VersionControl.Client"
xmlns:mtvc1="clr-namespace:Microsoft.TeamFoundation.VersionControl.Common;assembly=Microsoft.TeamFoundation.VersionControl.Common"
Look for Version Specific references (usually "10.0" or "11.0") and remove them so they look like the ones I have above.
Also, check you project references and ensure that they are not Version Specific.
Here is HOW to change the assemblies in your TFS Template:
In Source Control Explorer, browse to the BuildprocessTemplates and
open (double-click or choose "View" from the Right Click menu) the
template that your build is based on (the one giving you the above
error)
You should see a visual diagram of the workflow. At the bottom are
three tabs: Variables, Arguments, and Imports. Click on Arguments.
Select the BuildSettings Argument
Find the Properties box. The properties for an arguement are:
ArgumentType, Direction,IsRequired, Name, and Value.
Microsoft.TeamFoundation.Build.Workflow.Activities.BuildSettings
should be the selected Type but the problem is (typical) you can't
tell which version of this assembly is selected. Click the drop
down.
At the bottom of the list choose "Browse for Types..."
NOW you can see all of the available assemblies and their versions. Choose the one you want, most likely upgrade to the latest. Be sure to go through all of the various arguements and make sure their types are all are set to the same version to ensure compatibility.
You may encounter issues now saving the file. All may appear to be ok. TFS indicates it knows the file has changed, checkin seems to go smoothly, but when the file is opened the assemblies still reflect v 10. If you open the same file from the file system you may find that the assemblies in the file really are v 11. What give? No idea. Some sort of glitch in VS.
But here is a work around:
Uninstall VS 2010 Team Foundation Server Power Tools from your
development machine
Open VS 2012 and make sure the template has no pending changes (undo) and get latest version
CHECK OUT FOR EDIT (important) but do not make any changes in VS (it
won't open anyway since the 10 assemblies were uninstalled in a
previous step)
Close VS 2012 (important because if it is open it will appear that your change didn't take)
Open the template from the file system (I used notepad to eliminate any interference from VS) and perform a find/replace on "Version=10.0.0.0" with "Version=11.0.0.0" and save the file
open VS 2012 and now you should be able to see the workflow designer
Of course, check in the file
I'm working in TFS with my team for project and the problem occurs when I'm trying to make new modeling project for my classes, it doesn't show up in pending changes.
So here is how I go:
First I enter my folder where I keep my classes. I've tried from there many combinations: I've tried first right-clicking on my folder and putting "check-out for edit" and then continued to * (see later); next I've tried clicking on .csproj of my classes so I activate my project when I'll be adding modeling project and then moved to *; last I tried to activate whole solution of our whole projects which is connecting them and then to moved to *.
None of it worked. (I was always having last version)
here is what I did next for all the possibilities:
I went to Architecture -> New diagram (named diagram and left create new project) -> Create (then windows shows up for creating new project in which folder and I always select my folder where I keep my classes).
After when that was done, I went to check to "pending changes" in Team Explorer, because there should be some available since I created already Modeling project. But there was none. Since I couldn't do it like that, the last solution how I made it was by right-clicking to Source-control Explorer on my project and going to Add items to folder and selected my project which was created locally where I wanted it to be created.
But, this last solution was giving me errors while trying to open my modeling project after. I know I should activate first modeling project, so I clicked to .modelproj and while clicking to it, it was giving me this "notice" or rather "warning":
The solution you have opened is under source control but not currently configured for integrated source control in Visual Studio. Would you like to bind this solution to source control now?
--
What am I doing wrong? Why solutions are not integrated by default while creating my project (my friends are doing it automatically, they don't need to right-click in Source Control Explorer to add item to be able to see pending changes)?
I hope I made myself understandable.
It looks like your solution binding is broken. Either click yes on the question to bind your solution to source control, this is information that must be stored in the solution file and while Visual Studio does see that the folder is mapped to source control, it also sees that your solution isn't (did you check the add solution to source control checkbox when you created it?)
Optionally try opening file -> Source Control -> (optionally) Advanced -> Manage Source Control. You can select project in your solution individually and then click the bind button on the toolbar to bind them to sourcecontrol manually.
I had a similar issue and, in my case, the solution was to right click on my project and choose Source Control->Go online. Apparently I must have somehow been switched to the offline mode.
I have successfully checked in files from source control explorer instead of solution explorer in this case. Then after that it has worked again
VIEW > Other Windows > Source Control Explorer
Other way to do it:
File--> Source Control --> Advance --> Change Source Control.
In the window displayed select all the projects you want to bind to the TFS
I had the same issue and solve it by clicking:
File -> Source Control -> Advanced -> Refresh Status
In VS2013+, you can check if your solution is online. In my case, due to VSO service outage, my solutions went offline. I had to open the solution, File > Source Control > Go Online.
I recently installed Visual Studio 2012, and I've been banging my head against my desk looking for missing options.
I use the Recent Projects and Solutions menu option (under the File menu) a lot in Visual Studio 2010, but don't have anything like that in Visual Studio 2012. However, my boss does, so I know there's something wrong with my install or an option I've missed.
I've casually looked through registry settings for anything like "Project" that exists in my 2010 settings but does not exist in my 2012 settings, and came up empty handed. Does anyone know how to fix this?
It looks like some part of the upgrade process just removed this menu option for me. Following nithins link to this question, I followed the instructions the author created to re-create the Recent Projects and Solutions menu item.
For posterity, those steps were (performed in Visual Studio 2012):
Under the Tools menu, click Customize...
Click the Commands tab.
Change the Menu bar selected option in the drop-down list to File.
Click Add New Menu.
Click Modify Selection, rename to Recent Projects and Solutions.
Under the Menu bar drop-down list, select File | Recent Projects and Solutions.
Click Add Command...
(The Add Command menu should appear here.)
Under Categories on the left-hand side, click File.
When the Commands list (on the right-hand side) refreshes, click Recent Project list, and click OK.
Click Close.
Happy project switching!
I had the exact same problem, but I had the sense that other menu items were missing as well.
What I did was go into Tools => Import & Export Settings, choose Reset all settings, and then select the same profile as when I installed Visual Studio. (General Development Settings.) That fixed the issue.