I'm in the process of upgrading from a 5.xx to a 2019 R2 version. After importation into the 2019 R2 My customization project editor screen ends up blank, as follows:
If I go to File > Edit Project Items, it shows all the items. The main problem here is that I can't update the dll and pdb files without that option on the left-hand pane.
Does anyone know how to get the items to show up on the main screen?
The problem was caused by SQL Scripts that were generated by a very old version (5.3) and were not readable by 2019 R2.
Related
I installed Visual Studio 2017 Professional on Windows 10. Then using the installer I saw that VS 2017 Enterprise was "available" so I installed it. Now all of VS (Blend, VS, etc.) are duplicated in the start menu. I would like to be able to remove the duplicate entries in the start menu but I don't seem to have that option. Does anyone know how to remove all of the "...(2)" entries in the start menu? And related why does VS installer create these duplicate entries?
Right click on the duplicate item in the start menu > more > go to file location. There will be shortcuts titled the same as the items on your start menu, just delete the shortcuts and your start menu will reflect instantly.
Or goto :
C:\ProgramData\Microsoft\Windows\Start Menu\Programs
and remove them directly
If I run an SQL Schema Compare in Visual Studio 2012 (part of the SQL Server Data Tools add-on), I can highlight text inside an object definition, and can right-click to select "Copy (Ctrl+C)", and it works. But actually pressing Ctrl+C doesn't work — absolutely nothing happens.
How can I fix this?
What I've tried: messing around in the Keyboard Shortcuts dialog, which doesn't seem to list that specific version of the copy command.
Other info: the default Edit.Copy command doesn't seem to be enabled; the Edit menu's Copy command is greyed out when selecting in the Object Definition panel, curiously.
This a bug in the July 2014 release, with no workaround right now. It's been fixed internally and will be included in the next SQL Server tooling update - for more information see this Connect bug.
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
I wass looking for quite some time now how I could see the file type icon of each file I have opened in visual studio 2012 tab well, like it was shown on previous versions of visual studio. This was completely removed from vs 12, couldn't find any option enabling this. This is something extemely usefull when having many open files.
I found that this option exists on the registry!
So you go here:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\DialogPage\Microsoft.CustomDocWell.Options
and change the IconInTabs property from false to True!
File type icons are displayed again next to each tab!!!!
Edit: In order for this to work you must have installed Productivity Power Tools 2012 plugin
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