We have a TFS 2008 server that we are using for source control having migrated away from VSS :D This is great for all our web projects as they can all be migrated to VS2008.
My problem is that VS2008 doesn't support development of SQL2005 SSIS packages.
It is possible to check SSIS packages into TFS2008 from VS2005? Would this conflict with the VS2008 install on the same workstation?
Thanks in advance....
Looks like you'll be fine if you install Team Explorer 2005 onto Visual Studio 2005.
Out of the box, Team Explorer 2005 works very well with most of the TFS 2008 capabilities. Work Item Tracking and Version Control function the same as they always had for TFS 2005. End users wouldn't even notice the difference, except in some rare cases the increased performance.
From : http://weblogs.asp.net/dmckinstry/archive/2007/08/27/considerations-on-using-tfs-2008-with-visual-studio-2005.aspx
Related
I have legacy projects bound to Visual SourceSafe and done with Visual Studio 2003. Now, I have recently installed Visual Studio 2017 and TFS in the same machine.
Now when I try to open a legacy project that is bound to Visual SourceSafe I get a sequence of errors. Below the screenshots (pixeled for confidenciality reasons).
It seems like when open a legacy project (bound to Visual SourceSafe) with legacy visual studio 2003, it tries to connect to the TFS server (obviously it cannot). It is happening since I have installed new Visual Studio 2017 and TFS in the same machine, it seems like they cannot live together in the same machine. So how can I keep both VSS and TFS installed in the same machine? Is it possible?
UPDATED:
It seems like VS2003 does not allow to switch SCC providers. The only way is to hack the registry to switch.
I have found some interesting things that explains how to do it and it seems to work, the problem is that some links are broken, they are too old and not available anymore.
Source safe with Team Foundation Server in VS.2003
Installed TFS Version Control Provider and Now my VS 2003 Projects lost connectivity to VSS 2005?
MSSCCI Provider installation error
In above links it is provided a solution that consists on hacking the registry but the link they provide is broken:
Switch SCC providers
UPDATE 2:
As Edward Thomson has suggested in his answer, I have created a new key 'HKCU\Software\Microsoft\VisualStudio\7.1\CurrentSourceControlProvider\ ' and set it with a string value: ProviderRegKey="SOFTWARE\Microsoft\SourceSafe". Below screenshot, but it is not working:
MSSCCI is the Microsoft Source Code Control Integration API, it was the original API provided by Visual Source Safe for IDE tools like Visual Studio. Early Visual Studio versions (like 2003) only spoke MSSCCI, and expected a version control provider to provide MSSCCI. As a result, you can only have one version control provider speaking that protocol.
The Team Foundation Server client APIs provide MSSCCI (for Team Foundation Version Control only, not Git). As a result, if you want to use Visual Source Safe, you will need to configure Visual Studio to speak to that set of libraries instead of the TFS set of APIs.
In slightly more recent versions of Visual Studio (like Visual Studio 2008), you can choose your MSSCCI provider on the fly, in Options > Source Control > Plug-In Selection. All the MSSCCI providers will be enumerated and you can select between Visual Source Safe and Team Foundation Version Control.
If you're using an earlier version of Visual Studio that did not have this option, then you can change your MSSCCI provider by updating the registry directly.
Find the registry key:
HKCU\Software\Microsoft\VisualStudio\7.1\CurrentSourceControlProvider\
And set:
ProviderRegKey="SOFTWARE\Microsoft\SourceSafe"
Update 7.1 in the key with the version of Visual Studio that you have installed (Visual Studio 2003 corresponds to version 7.1.)
Once you have made this change, you will not be able to use Team Foundation Verson Control from Visual Studio 2003 without changing that back.
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.
At SO, I searched "identify version visual studio" but failed to find an answer.
Scenario:
A generally accepted best practice is to install all service packs related to the software that one is using.
The applies to Visual Studio 2008 too. In some cases, it is absolutely essential, for example VS2008 SP1 is required if one wants to install ASP.NET MVC v1.0 RTM.
For most software, "Help, About ____" will reveal the version and often includes SP level.
With my VS2008, I get a lot of information, some of it is clear:
Microsoft .NET Framework
Verson 3.5 SP1
and some of it which is less clear:
Microsoft Visual Studio 2008
Version 9.0.30279.1 SP
The problem is that it is difficult to tell whether VS2008 SP1 has actually been installed.
The same information appears to be displayed in Help, About on computers that have vs2008 SP1 as well as those that have not been upgraded.
Likewise, different editions, example "Development" and "Professional" show the same results via Help, About.
--
QUESTION: how does one correctly identify her/his vs2008 version level?
edit: found this:
How do the .NET Framework, CLR and Visual Studio version numbers relate to each other?
I wish Microsoft would make this easier.
#nos ... your QFE is a hotfix ... http://en.wikipedia.org/wiki/QFE.
AFAIK, you've likely applied a security patch.
I guessing the "30279" part of 9.0.30279.nnnn means SP1 and the "nnnn" is a subsequent update level.
edit #2:
MORE INFORMATION
The challenge I find is to identify the version easily.
While this may seem strange, and while unfortunately
I lack a time machine, at least once I was certain that
I already had vs 2008 SP1 but ASP.NET MVC would not install.
At that time I applied the MS SP1 upgrade;
while executing, the upgrade said it was upgrading SP1 !!
After upgrading SP1 to itself, ASP.NET MVC did install.
Ergo, I find this so confusing. It would be so
much easier if Microsoft showed via Help, About, this instead:
Microsoft Visual Studio 2008
Version 9.0.30279.nnnn SP1
edit #3:
http://blogs.msdn.com/bharry/archive/2008/04/19/a-new-home-for-visual-studio-hotfixes.aspx
There are currently 169 hotixes:
http://code.msdn.microsoft.com/Project/ProjectDirectory.aspx?TagName=Hotfix
at least two to the hotfixes apply to vs2008 sp1:
http://code.msdn.microsoft.com/KB957912:
"KB957912 - Update for Visual Studio 2008 SP1 Debugging and Breakpoints"
http://code.msdn.microsoft.com/KB957507:
" KB957507 - Loc Intellisense to replace all Loc Int shipped with VS 2008 SP1"
"Please be aware [hotfixes may have
NOT] gone through full Microsoft
product regression testing nor has it
been tested in combination with other
Hotfixes."
UPDATE: on a windows 2008 web server R2,
I have Microsoft Visual Studio 2008 Version 9.0.30279.1 SP
which is "in theory" SP1 ~~ however, installing SQL 2008 Web Server
failed with the mysterious explanation that I required vs2008 SP1!!!
UPDATE CONTINUED: after applying the MSDN update to my
windows 2008 web server R2, I still have
Microsoft Visual Studio 2008 Version 9.0.30279.1 SP
which now really should be SP1 ~~ and I assume it must be
because the pre-install validation "rules" for SQL 2008 Web Server
passed and the SQL server installation then ran and completed successfully.
I have the same information. You're running Visual Studio 2008 SP1. This runs on top of .NET 3.5 SP1. Service Pack 1 for Visual Studio and .NET 3.5 is installed.
Well actually you can identify it with the given version. In your case the 9.0.30279.1 is really VS2008 SP1, it redistibutes Microsoft DLLs with this version (see C:\Windows\Winsxs for all of them).
So I suggest that you google for the version number. That should give you the correct VS2008 version.
Does anyone have any basic instructions for setting up a first MVC project in Visual Studio 2008? I just installed Visual Studio 2008 and I am finding various instructions on how to set up the programming environment, but it's very complicated and there is no way to tell if the route I am taking is the best one.
If I want to start developing a MVC project, what do I need to do in order to get it going?
I am very confused by the "Web Client Guidance" instructions. For example, they don't say where to put the Microsoft.Web.Mvc.dll file.
Use Visual studio 2008 sp1 to get mvc installed...
Here is the download link
To get started With MVC
System Requirements
Supported Operating Systems: Windows Server 2003; Windows Server 2008; Windows Vista; Windows XP
.NET 3.5 SP1. Visual Studio 2008, Visual Studio 2008 SP1 or Visual Web Developer 2008 SP1 are required to use certain parts of this feature.
The official Microsoft MVC links for Visual Studio 2008 now seem to be dead.
To get this working on my old Vista laptop (with Visual Studio 2008) in 2013, I did this:
- Upgraded to Visual Studio SP1
- Followed this link to download and install "AspNetMVCRC-setup.msi" (1.74 MB):
http://go.microsoft.com/fwlink/?LinkID=141184&clcid=0x409
Once that was in place, my old Visual Studio let me create "Web | ASP.NET MVC Web Application" projects. Took about an hour and a half from end-to-end.
All I did was install the MVC installer and I opened their example app and it worked.\
MVC Installer
First of all, you need to download MVC from here.
After that, proceed with the installation.
You might want to refer to the tutorial for starters.
We are setting up a new TFS 2008 implementation as our first usage of TFS for source control. We have several projects in Visual Studio 2003, 2005 and 2008, as well as other script/non-Visual Studio based projects.
My question is, for the Visual Studio 2003 and 2005 projects do we have to install Team Explorer 2003/2005 and make use of them to add projects to source control and to check out/in files, or, can we just use Team Explorer 2008 to add projects and check in/out files? The thought being that the developer could use 2008 to check out any thing and then open the appropriate visual studio version to work on their local instance of the project before then checking it back in using team explorer 2008 within their local visual studio 2008 application.
The concern is that by using team explorer 2008, that visual studio 2008 might impose changes on the older systems solutions dll or control details.
Thanks for any guidance.
This is possible. I have colleagues who are using Team Explorer for non-code files (Word documents, help files, etc.) and use it like they would VSS or any other SCC.
As an added bonus, I'm pretty sure that TFS Server 2008 is backwards compatible to at least 2005 (haven't run against 2003 in awhile). IIRC, I've run VSTS 2005 For Developers against a 2008 TFS Server.
I would double-check for you, but I've recently recently re-imaged my dev machine and haven't re-installed 2005 (working on new stuff!).
As an aside, I've found TFS to be a huge timesaver as far as the whole dev process. The IDE integration is top notch, and the linked bug/task tracking and changesets, with alerts, notes, built-in queries and reports had me wondering how I ever got along w/o it.
HTH.
The Team Foundation Client for VS 2005 and VS 2008 can be installed side by side so there's no issue there (there isn't one for VS 2003, but you could probably use the MSSCCI provider).
You can however, if you want to, do all of your source control operations in VS 2008 (or the Windows Explorer extensions in the latest power tools) but work on the projects from VS 2003/2005 without any issues. You just need to make sure you don't accidentally open the project files from within VS 2008 because that will upgrade the project format.