I think the title is very clear, but also i want to say why:
I already downloaded TFS 2010 and Team explorer 2010, but i'm still using VS2008 (with no short-time plans to change)
My question, can i use those toghether?
Also, my VS is just the professional version. I don't want to download the TE2008 because for my internet conection, it is just too big.
Thanks in advance
The 2010 client is backwards compatible with 2008 servers (though not 2005). Details: http://blogs.msdn.com/teams_wit_tools/archive/2009/10/19/compatibility-matrix-for-2010-beta-2-team-foundation-server-to-team-explorer-2008-and-2005.aspx
However, it will not integrate inside the VS2008 shell. If you want full source control integration you'll need to download TE2008 + SP1.
Related
OK, can't find a solution to this.
A client sent me his Microsoft Visual Studio Express 2012 for Web project. I have Microsoft Visual Studio Ultimate 2010 installed.
I get an error when I try to open his project saying "this project is not compatible with the current version of visual studio".
We'll be passing the project back & forth quite a bit, so I need a solution that meets that need please.
So, I figure I may be able to modify the project with a text editor to let me open it. If so, do I have to re-edit it back when I send it back to him?
Can I install VS Express 2012 for Web on a machine that already has VS Ultimate 2010 on it without any conflicts? Can I open it if I install VS 2012 Ultimate (keeping 2010 as well)?
I have another client that uses 2010, so whatever I do, I need to be able to still support him.
If I can't have 2 versions installed at the same time, and can't easily edit a file to make it compatible, then I guess my last option is a virtual machine.
Thanks in advance for any advice.
Microsoft Visual Studio has backwards compatibility since the version 2010 SP1.
So in this case you just need update your Visual Studio 2010 to SP1 and it will understand the new way files are versioned.
Based on my experience:
You do can edit it with a text file and send it back, but it's not compiled yet so it's your partners job.
Maybe, just maybe, you can edit the .sln and .(whatever the project file extension is) file to meet your VS10 env (I think it's going to be a bumpy road though)
Yes, I'm pretty sure you can have VS 10 and VS 12 installed on same machine, note that you have to have .Net 4.0 and .Net 4.5
We are a small design agency based on .net. The devs use VS and TFS. Is there a way of setting up the designer with some kind of way of getting source code and building it on their machines without the full version of VS which is pretty expensive for people who only want to change CSS and odd bit of HTML. The designers currently use Dreamweaver.
Visual Studio 2010 Express does not have a support for TFS.
But now you can use Visual Studio 11 Express which supports TFS.
Visual Studio 11 Express Features
In TFS2010, you can install the Team Explorer and use your favorite file editing tool. The designer then only needs a TFS CAL to connect to the TFS server.
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.
I have around 50 projects in Visual Studio 2005 that I am building a new development machine for and I'd like to slowly move those projects to VS 2008 but also have 2010 available for select new projects.
Can this work? Are there any gotchas for this sort of setup? Any general advice for running multiple versions of Visual Studio on the same system would be greatly appreciated. Specifically related to managing a controlled migration of projects to new versions but being able to selectively keep some on old versions.
I've got 7.1, 8, and 9 installed at the same time (well, and VB part of 6 as well) and I've not really had a problem opening projects file in the wrong version. The Visual Studio Solution files is "associated" with a particular version even if they all have the same extension of .sln, as you can see from its little icon. Microsoft Visual Studio Version Selector seems to handle individual project files (.vcproj) fine as well.
The only thing I've had is the individual source code files not opening up in the latest version like I want, but that's easily fixed with the click of a little button in VS Opions.
Microsoft have this to say:
Visual Studio supports the installation of Visual Studio .NET 2002, 2003, ... on the same computer.
In general, you should install the earliest release of Visual Studio first, and then install subsequent versions of Visual Studio in the order in which they were released.
Make sure when you open up the 2005 files you're doing it in 2005. To open them in another would require a conversion which would render them incompatible with the older compiler set-up. To aid this, structure whatever workspace you're using into 2005, 2008, and 2010 so as to minimize accidental chance of this.
Second, when you double click to open the projects, it will invariably attempt to open them with 2010. You'll have to start with VS#### instead of the solution/project unless you're in the 2010 workspace.
I have VC6, VB6, VS 2008, and VS2010 RC installed on Windows Vista. I cannot double click on the VC6 dsp files without VS2010 opening and asking to perform the conversion. The 2008 C# projects open in 2008 as long as I use the solution file. The 2008 project file opens in 2010 instead of 2008 even though the version selector is the default program. Most of the time I try to remember to open the desired version of Visual Studio and then open the project.
You can mitigate some of these issues by changing the default program associations in the control panel or the registry.
Update: This setup works on Windows 7 x64, with the addition of VS2013.
Yes it can work. I'm not sure if you have to install them in a particular order... but install them in order of the versions... 2005, 2008, 2010. Should be good to go.
I can't speak for 2010, but I have run 2005 and 2008 at the same time on my system without any fuss.
And I made the double-click mistake that wheaties warns about more than once :(
I have VS2005 & VS2008 running without any issues. I have had problems when working with betas, express editions & am assuming you don't have them.
I would say refrain from making too many changes to the setup of these editions, it should be fine.
I also had the same doubt. I work at my company which is still on VS 2008 and I want to personally use the VS 2010 and not risk the 2008. I installed the 2010 and it worked fine with the 2008. Just make sure you note the projects that are in 2005 and open them with the same accordingly.
The reason why it works is simple: if you open your solution file in Notepad, you'll see which version of VS is related to your project.
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.