I was very excited to hear TFS 2012 made a step towards distributed source control in allowing source code to be modified (without major issues) when TFS is offline.
I currently use a hosted TFS service, so im hopeful the migration to TFS2012 should be painless. At least for me anyway.
So my question is simple, is there such a thing as TFS2012 powertools for VS2010 or is TFS2012 only available for VS2012?
Appreciate your comments.
You can connect to TFS 2012 from VS 2010, but you'll need the compatibility GDR. Local workspaces (which support the improved off-line experience you described) are only supported in VS 2012 since they required significant client changes.
Related
We are currently in a position to move up from Visual Studio 2008 to Visual Studio 2010. Unfortunately, we don't have a server allocated for a TFS upgrade yet (should happen in about 6 months), so we are stuck with TFS 2005 for now. Will VS2010 be compatible with TFS 2005? If so, any potential issues we need to consider?
Visual Studio and Team Explorer 2010 do not officially support TFS 2005 servers (see http://msdn.microsoft.com/en-us/library/dd997788.aspx for the compat matrix). I don't think it is actively blocked, though, and it may work just fine for the mainstream scenarios. I don't have TFS 2005 server to try it.
Currently using VS2010 and TFS2005 here and they work well together.
Ok, I have looked around on SO and haven't been able to find an answer to this question, but forgive me if I missed one out there. It's difficult to refine the search terms for this one.
But anyways, I have VS 2010 C# Express. I'm planning on doing some collaboration in my code (that was made entirely in Express) with someone who owns VS 2010 Ultimate. I have been putting off upgrading to the paid version of VS 2010 because of the price - if at all possible I would rather not upgrade. We are going to collaborate using Tortoise SVN as our version control software.
Will it be an issue for me to continue to work with the Express version while my collaborator works on VS 2010 Ultimate? To what degree will it be an issue, etc?
Follow-up question: If I have to upgrade to a paid version, would I have to upgrade to Ultimate, or would Professional be sufficient?
I have no experience with VS 2010 yet, but can offer observations based on VS 2008, using svn for source control.
I have only had one minor issue with using both the VB Express edition and VS2008 Standard and Professional versions on the same project. The express version does not support solution folders. I use a solution folder to allow quick access to some configuration files from the ide. The express version does not display the solution folder, but the remainser of the solution loads sucessfully, including all the included projects.
Well, my collaborator and I have started work, and no issues so far. Visual Studio 2010 Ultimate and Visual Studio Express are pretty much compatible, except for the Solutions folders, as described by B Pete.
I've been using the trial edition of Visual Studio 2008 Team System to develop projects and work with my client's Team Foundation Server. I am using the Team Explorer integration / source control plugin.
My trial is expiring and I'm having trouble finding information on what exactly I need to purchase. I don't need to actually run a TFS server myself, but I do need the ability to connect to my clients and get/put files, and the integration with Team Explorer in VS is really nice, hence I'd rather not have to use an external 3rd party tool.
Do I need Team System to accomplish this or does Visual Studio 2008 Professional have the same TFS Plugin, and if so does it work the same?
I can't believe I'm having such a hard time finding the differences between the versions... if anyone has a good resource that'd be nice before I shell out $3,000 on something I don't need. I develop mainly ASP.NET Solutions if that matters. Thanks!
Visual Studio 2008 Product Comparison Guide
I don't need to actually run a TFS server myself, but I do need the ability to connect to my clients
Whoever is running TFS should procure CALs (Client Access License) so that any client that works with this server is covered. I believe you buy them separately per client machine (somewhat around 400$ each). Also VS Team System editions have one or two CALs included. That may be or may not be worth it for you.
And yes, you can access TFS from VS 2008 Pro, just need to install the integration plugin.
I don't know if that is possible at all for you, but if you can, I would wait for Visual Studio 2010 (to be released in march 2010). Not only is it a better product than VS2008 but also they have simplified the versioning/licensing part, also Team Foundation Server 2010 Basic may be suitable for your source control needs.
If you want to take a look, you can download the beta versions of VS2010 and TFS2010.
I'm currently in the process of investigating TFS 2010, as it's been agreed that we'll be getting VS2010 Professional when it's released and it comes with TFS Basic (we're currently stuck with VSS, and were considering moving to SubVersion prior to the TFS Basic announcement).
I've downloaded an installed the Beta 2 of TFS 2010 and installed it using the Basic installation, which I'm led to believe is what the actual TFS Basic would be equivalent to. I configure it all, install the Team Explorer into Beta 2 of VS2010, and begin nosing around. I see lots of interesting looking options, and turn on one for my test project that says Check-in Policy - Code Analysis. I then try checking in something to that project, and a little dialog pops up saying
Evaluation of Code Analysis Policy
requires Visual Studio 2010 Premium
Beta 2 or Visual Studio 2010 Ultimate
Beta 2 to be installed
However, I can't find any reference to this or other limitations online anywhere. The MS VS 2010 feature comparison page gives all three versions 4 stars for TFS product features, and the pages I've read on the limitations of TFS Basic only say it lacks Sharepoint and Reporting capabilities.
Am I missing something here? Is there an article somewhere on the limitations, or perhaps some confusion between a product TFS Basic and a basic install of the full version?
Sorry this is so confusing. Few things first of all.
VS 2010 Professional with MSDN comes with TFS. Not just TFS "Basic" but a full server license to TFS and a CAL (client access license) to access it. When you install TFS you can then pick what installation option you require. You can go for "Basic" which configures all the pre-requisites for you (such as IIS, SQL Express etc). Or you can go for Advanced if you want the more traditional TFS installation where you can install IIS, MOSS, full SQL Server with reporting services etc first and then install a full TFS that is integrated with these products. You can think of "TFS Basic" - as "Easy TFS". It's the same TFS, just easy to install (including on non server operating systems such as Windows 7 etc). You can move your project collection created on a basic installation of TFS to a full blown TFS installation in the future if you find you outgrow the basic installation.
Check-in policies are bits of client side code that run every time you perform a check in. The particular one that you selected actually runs some features in visual studio to do with code analysis. The problem you are running into is that those features are only available with the premium editions of Visual Studio and is not included in Professional. The feature on the TFS (server) side is just being able to run check-in policies. The feature on the client side is what the check-in policy is calling. Confusing I know.
My tip with check-in polcies would be to not enable them at first and switch them on gradually (see http://www.woodwardweb.com/vsts/policy_override.html for my rationale behind this).
Hope that helps.
Martin.
What reasons are there for continuing to run Visual Studio 2005 when 2008 is available?
I work on a project where the environment is dictated to be Visual Studio 2005. Are there good technical reasons for this? Can I use Visual Studio 2008 and build an app that is 100% indistinguishable from the same app build with Visual Studio 2005?
I think there are two questions here
Can I use VS2008 to create apps compatible with VS2005
Generally speaking the answer is yes. I do this frequently with several internal and external hobby projects with great success. You may encounter an odd ball tooling issue but so far none has cropped up for me.
Is there any reason not to use VS2008 over VS2005
The best reason I can think of is a large developer environment. Once you make the switch to using VS2008, it will upgrade all of the projects in your solution to the new format. This will no longer be usable for anyone using VS2005. They will be forced to upgrade or maintain parrallel versions of the project file. In general, I find it's best to upgrade in groups rather than individuals.
We are currently migrating from 2005 to 2008. If you open and save a project while in VS2008, you will not be able to open that solution/project in VS2005 (at least we couldn't find a way easily). If the rest of your team is still in 2005, you should stay there. You CAN, however set up a project in 2008 and keep it compatible with 2005... as long as everyone opening it is using 2008. You keep the .NET version at 2.5, and don't convert most of the stuff that it wants you to convert.
The only time you CAN'T migrate to 2008 is if you are using a report project and SQL Server 2005. VS2008 will only let you integrate a report project with SQL Server 2008. What did we do?
We migrated to 2008 and all the Team Server stuff, except for the database and reporting. Those we kept on 2005, and so I end up having to open both versions on a daily basis... but that's why they pay me the (somewhat??) big bucks!
Not really, the new version of Visual Studio has the compilers for the new language versions and all the libraries for .NET 3.5. Since they all target the 2.0 CLR and Visual Studio 2008 allows you to target previous versions of the framework I don't see any reason to stick with 2005.
The obvious answer is: No license for Visual Studio 2008.
My company is "saving money" but not upgrading...
One reason might be interaction with existing products.
I write code for AutoCAD in C#.
They (Autodesk) "officially" support VS 2005 but I've been using 2008 since...well 2008.