I want to code a VSPackage and need to get the selected items from Source Control Explorer History. I'm pretty sure that I need VersionControlExt, but I can't find the namespace Microsoft.VisualStudio.TeamFoundation.VersionControl using Visual Studio 2013. Can you help me?
You can use a NuGet package Microsoft.TeamFoundationServer.ExtendedClient. I'm not sure if these are too new to work against VS2013 but it's easiest to test.
If the NuGet package doesn't work, you can get the DLLs on your machine. These DLLs are stored in the Private Assembly cache of Visual Studio. You can edit the register to allow Visual Studio to search through these folders. See the first step of this post for details: Step 1: Help Visual Studio Find Team Foundation Assemblies
Related
I'm new in Asp.net mvc, and I want to load this project but I can't see more folder projects in the solution explorer. somebody knows what I must to do?
this is my screen
Open your Visual Studio as an Administrator.
.cs project file
The project was created using Visual Studio 2010 and I am trying to open it in Visual Studio 2010 itself but still I am facing this problem.
I have opened this project in VS 2012 and worked for few days but it has created in Visual studio 2010. Is there anything which preserve the project details on local machine?
This is the specific project section in my solution file:
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2010
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Project Name", "Project Name\project name.csproj", "{48C1190E-7700-461B-ADCD-B5E0F1ECAD21}"
ProjectSection(ProjectDependencies) = postProject
{1F5440B3-9FD8-4FE2-B621-8697489ABDC4} = {1F5440B3-9FD8-4FE2-B621-8697489ABDC4}
EndProjectSection
EndProject
In Visual Studio it is possible to add Project Types, e.g. for creating an MSI, by installing an Add-On to the development machine. It appears that in the past this was done, and then that new Project Type was used to add a Project to the Solution. But now you are opening the Solution on a machine that does not have that new Project Type.
Look for the GUID of the missing Project Type, it should be part of the error you are getting. Then google "project type {the-guid}" to see which Add-On you need to install on your development machine.
It is also possible that a new Project Type was used in the Solution that simply can not work with VS 2010. In that case your options are either to keep using VS2012, or to start over with a new Solution in VS2010 and migrate the projects into it that are compatible (which may be a bit tricky or hard to do if VS2012 saved them).
Would it be too difficult to just recreate the project and include all the necessary files and references? Once the project was saved from VS 2012, the format may have broken compatibility with 2010. Sometimes this is fixable just by updating the version number in the project file, but I don't see it in your image.
I've referenced the latest Microsoft Team Foundation nuget packages found at https://www.visualstudio.com/integrate/get-started/client-libraries/dotnet but I cannot find a reference anywhere for TeamFoundationServerExt. Does anybody know if these have been moved to a nuget package too? If not where can I reference from (I was hoping not to use direct paths to Visual Studio 2015)?
You're looking for:
https://www.nuget.org/packages/Microsoft.TeamFoundationServer.ExtendedClient/
PM> Install-Package Microsoft.TeamFoundationServer.ExtendedClient
I'm not sure which Assembly you're looking for, Microsoft has never shipped a TeamFoundationServerExt assembly, all the functionality you need is broken into one of the at least 20 assemblies added to your project when referencing this package.
There is a class TeamfoundationServerExt, which is part of the assembly Microsoft.VisualStudio.TeamFoundation, that one is part of the Visual Studio SDK and/or full Visual Studio installation and is not available as a redistributable Nuget package as far as I am aware of.
I am using the nuget package Microsoft.TeamFoundation.ObjectModel I does have the down side of only being for .net 4.5
How can I use this Visual Studio Online source control with a visual foxpro (vfp) 9 sp1 project so that the VFP does automatic check in and check out as I change files and lets me undo or check in source code and view history like I can do in the Visual Studio 2010 IDE with dot net projects?
I see there's a free team explorer everywhere which i guess i can use outside of the vfp IDE - not sure how it will handle the SCX, FRX, LBX, PRJ files which are not textual.
May be you can't use VSO with Visual FoxPro 9, but surely you can use other SCM tools with Visual FoxPro, like SVN, Mercurial, PlasticSCM (which I use), etc.
For Diff and Merge you can use a new tool found on VFPx project, called FoxBin2Prg, that allow bidirectional conversion of VFP 9 binaries to text and vice-versa, so you even can modify the generated text version and rebuild the binary.
More info at FoxBin2Prg - Binary/Text Conversor for Microsoft Visual FoxPro 9.
Best regards!
I ran into this question while researching. Looks like Microsoft updated the MSSCCI to be used with Visual Foxpro
Install the Microsoft Visual Studio Team Foundation Server 2013&2015 MSSCCI Provider 32 bit : https://visualstudiogallery.msdn.microsoft.com/06c8e056-7f77-4a5c-9b8b-49318c143df8
It supports Visual FoxPro 9 SP2 connection to Visual Studio Online
Combined with the Team Explorer for Microsoft Visual Studio 2013, you can branch, forward integrate, reverse integrate. I'm still exploring it
You can't, and the main reason is that while PRG and other textual files are fine method code and other stuff is stored in DBF-format files, which your chosen source control software will treat as binary.
i did an upgrade and it caused lots of problems. unfortunately i didn't back it up. Is there anyway i can convert a 2010 solution file back into asp.net mvc 2008?
Make a backup of what's left of what you currently have before doing this ...
Create a new solution in Visual Studio 2008. Create new projects for the 2008 solution. Use the project menu or right-click the project and choose "Add Existing Items..." Choose all the code files .cs .vb, etc from your 2010 structure and include them in the 2008 structure.
Basically you're copying all the code back into a 2008 structure with the 2008 formatted project and solution files. The code shouldn't be substantially changed beyond repair. You might have to manually address some issues in the converted code but once you know what they are it will be a repetitive process more than anything.
If you are writing code of any importance you should be using a version control system like as SVN. I haven't tried Visual Studio 2010 yet, but can tell you from experience that the differences between 2005 and 2008 are laughably small. You can down convert a 2008 solution file by manually changing the first two lines from:
Microsoft Visual Studio Solution File, Format Version 10.00
Visual Studio 2008
to
Microsoft Visual Studio Solution File, Format Version 9.00
Visual Studio 2005
the project files are fairly trivial as well with the product tag changing from:
9.0.21022
to
8.0.50727
Please note the changes I have listed for project files may not be 100% accurate and I have not tested for differences between service pack releases. However, creating a new project in an earlier version of Visual studio, making a copy and then doing an upgrade should allow you to run a diff and provide a better answer than what is currently accepted.