Does anyone have any experience with installing multiple versions of Team edition on the same machine? For example Team Developer and Team Architect at the same time? Is this possible? Do you have to open one version vs the other? Or do you end up with one installation with all the versions installed on top of each other.
You can happily install multiple versions. When you install the second one it simply add the features into the same Visual Studio 2008 instance meaning you get the features of both in the same instance of the IDE.
That said, the way licensing works it is usually cheaper to purchase Visual Studio Team Suite (which includes all the features) then purchasing 2 seperate SKU's.
My guess will be that each new installation will overwrite the previous in your instance. See this:
With Team system being on one level, my guess is only one can be installed.
Related
The question I have is more to see if I'm able to save 25GB of hard drive space. I currently have 2022 Version of Visual Studio Community installed, though the engine I'm working in requires 2019 to be installed. how ever I have all the same required packages installed in 2022 version. (the engine for some reason does not want to use the newest version of VSC and is trying to force me to revert back) so if I install the previous version will the workloads installed with VSC 2022 be used in VSC 2019 or must I install the work loads independently of each VSC edition in order for me to use it properly ? If they are able to use the same workloads am i required to connect them in some way? if they are not able to read the same workloads, is there a way to get it use the same sources?
TIA.
Visual Studio's installation is authored with two types of packages: "standalone" or shared packages, which are typically independent MSIs that are installed in a shared folder, or a component-specific location; and "per-instance" packages which are installed into the VS install location.
The former group is basically what you're asking for. However, different versions of VS may install different versions of those shared packages (e.g. VS2022 may have a newer version of a standalone component than what VS2019 shipped with, and both will get installed). The goal though is that as long as they use the same version, it will be shared.
The latter group is not shared, usually because they are tightly coupled to other Visual Studio components and attempting to re-use them across arbitrary versions of VS could lead to weird runtime behaviors.
So, to a large extent, VS does what you're trying to do, as much as it can (according to the people that create each component).
I work in the production team in a petroleum refinery, neither me or anyone i, the department works in IT or software engineering, but we love our VBA macros.
In order to go beyond what one can do with VBA, I started doing some small projects using Visual Studio Express and VB.NET
These projects are getting bigger and bigger, and I am starting to feel limited by VS Express and I am therefore building a business case for a VS Professional licence (my company is too big for Community).
I'll go with a stand-alone licence, since the subscriptions are way overkill for what I do, but even the stand-alone licence is divided in two parts (https://www.visualstudio.com/fr/vs/pricing/).
You can either buy a licence for a fee of $500, or subscribe for $45 a month. Since I plan on using the software for at least a year, the one-time-fee is cheaper, and the only difference between the two is access to older and newer versions. Hence the questions:
Is the inability to use the pro versions of previous iterations of Visual Studio a big downside? Will I be able to work without big issues?
Are newer versions a must-have when they come out, or can I sit on VS2017 for a couple years without issues?
Usage of older versions of visual studio like 2013-2015 depends on projects /solutions that for whatever reason can not be migrated to a newer version of visual studio. In my experience usually companies which do not wish to purchase new licenses. I see no reason why you need the older versions.
As for the newer versions. The main reason I have seen for a visual studio upgrade is the usage of newer .NET versions. A version X of visual studio can only run .NET up till version Y. When version Y+1 of .NET comes out this means if you wish to make use of the new features/changes in .NET Y+1 you would have to upgrade .
I currently have Visual Studio v2003, v2005, v2008 installed on my system. Things work fine...no issues.
I now have to install Visual Studio 2010 on my system and just wanted to know if anyone has a setup like mine or knows if there are any potential issues with so many versions existing on a system.
Really don't have a choice to remove older versions as we have a lot of legacy products written in these old versions and we are not upgrading them to new versions, only doing bug fixes on them.
Any ideas?
Thanks!
VS2010 supports targeting on multiple versions of .NET Framework (i.e. 2.0 or later), which mean it is designed to support the projects that were built with VS2005/VS2008 so-called backward-compatibility.
So I think no conflict here between these versions,
I've found a nice Myths and facts about VS 2005/2008/2010, check out this link here: http://msdn.microsoft.com/en-gb/ee679805.aspx
It should work.
I have vs2003, vs2008 and vs2010 installed and I see no issue (but vs2010 is not yet used for production code).
M.
All these versions of Visual Studio are independent.
You should have no problem (other than lack of disk space!) installing VS2010 as well.
Just make sure you install the service pack as well.
They cohabitate fine, I have a similar setup myself.
You should at least push for migrating away from 2003 and 2005 though, they use some pretty old technology, and pretty much everyone these days has .net 3.5 on their systems.
If you are able to use VS 2010 I would highly recommend you do for all new projects - even if you have to target an earlier version of .NET framework.
Keep the old versions of VS installed only for maintenance of projects that cannot be migrated to VS 2010 version.
By the way, the migration to VS 2010 is often very trivial and well worth an hour or two of effort!
We are currently using StarTeam as our source control, but I am looking into alternatives. We are licensed for Team Foundation Server so I am thinking of using that as I believe it can integrate with VB6 and VS2010 Prof? (StarTeam doesn't integrate with either - at least the version we have doesn't)
Looking briefly at the features of TFS it seems there is a lot in there. To start with I just want SourceCode control. Does anyone know of a good step by step idiot's guide to setting this up? What needs to be installed where, what needs to be backed up etc, etc?
Also do I need to install anything else on my client to get VS2010 to work with it?
I don't really care about migrating the data from StarTeam but if anyone knows how this can be done I would be interested!
For your Visual Studio clients, you'll have to install Team Explorer - there's an installer on the TFS media, or you can download it separately. Each Visual Studio has to have a matching Team Explorer version installed (so if you have VS2008, you'll have to install Team Explorer for 2008), but to access later TFS servers, you generally have to install an extra update. For VB 6 (or VS2003), you'll have to use the TFS MSSCCI provider.
As to installing the server, all I'd recommend is install it somewhere first and play around with it before you install it for production use - get some familiarity with it. The install process is relatively straightforward.
I'm trying to get started with building my own webparts, planning to follow this MSDN article.
I've downloaded Visual C# 2010 Express - I'm not quite at the point where I feel comfortable dropping 1000 big ones yet, and I installed Visual Web Developer 2010 Express via the WPInstaller.
Following through the tutorial, aside from the fact that I don't get the option to create a "Web Control Library", a gap I filled with this article, I can't seem to find the sn.exe tool (or the "Visual Studio 2005 Command Prompt"!).
I know it's not quite a direct programming related question, but I can't even get the thing going yet!
Any help is appreciated.
Thanks
EDIT:-
I think I may be jumping the gun quite considerably, I wrote a simple hello world example and tried to build it but it doesn't have any references to the Microsoft.SharePoint packages and they don't appear in my lists.
Am I understanding some more research I've done (namely this) correctly, in that I have to actually have a full installation of actual SharePoint on the machine I'm developing on?
sn.exe is part of the .Net Framework SDK tools - not actually part of Visual Studio.
If you've got the SDK installed (which I think you must have if you're using VS) then it will be in a directory such as (depending on which version of .NET SDK you've got installed)
c:\program files\microsoft.net\SDK\v2.0\Bin
You can develop SharePoint web parts with VS express but you won't be able to use extensions like VSeWSS which can make your life a little easier.
You don't have develop on a machine with SharePoint installed upon - you can just copy the Microsoft.SharePoint.dll assembly from a machine with it installed on and reference it in your project.
There are pros and cons to developing on a SharePoint machine.
Its easier to get started -
especially debugging locally rather
than remote debugging.
Harder to be
sure that you're code will work a
'real server' - are you sure you
don't have any dependencies that may
not be installed.
Harder to work with
multiple versions of SharePoint (2007
WSS and MOSS and 2010 foundation,
server etc).
If you do want to work with a locally installed SharePoint then
You can install windows server OS with SharePoint and Visual Studio.
there is a hack for installing SharePoint 2007 on vista (referenced in the SO article you link to)
you can install SharePoint Foundation 2010 on Windows 7 (but I am not sure what the licensing restrictions are - is this maybe something thats given through MSDN?)
If you decide to go with the remote server installation then save yourself some grief and use virtualization such as VMWare Server, Virtual PC or Hyper-V.
If you are doing SharePoint development trying to reference the Microsoft.SharePoint namespaces you need to have SharePoint installed on the machine if you want to do things like debugging, etc. For SP 2010 you CAN install SharePoint on a Win 7 machine. For previous versions of SharePoint, you will need to setup a Server that is Server 2003 or Server 2008 (you can't install SP 2007 and earlier on client machines). Generally this is a Virtual Machine for developers.
Having said all of that, there are relatively few reasons you need SharePoint to develop a WebPart. The vast majority of the WebPart functionality is part of the System.Web.UI.WebControls.WebParts namespace. Even if I am accessing SharePoint data, I generally use the ASP.NET web part.
If you are trying to use the new SharePoint VS 2010 functionality to create Visual Web Parts, etc, then you will need to install SP 2010, since that functionality is not supported in earlier version of SharePoint.
John