A while back it was clear:
Roses are red, violets are blue … if you are a dev you use Visual Studio.
Now: Roses are blue, violets can be red … if you do SharePoint,Visual Studio is the right tool for you.
I am not a poet, nor do I pretend to be one on TV. But I have invested time in fine tuning virtual machines and physical deployments in figuring out what goes where and what is needed.
We see dependencies of every type, in every place and every product pretty much. If you are doing SQL Server 2008 R2, well SharePoint is there, If you are doing SharePoint, well SQL Server is there. Reporting Services … pretty much you get the idea.
Now, we have PowerShell everywhere, and there are different reasons an Admin will need to get into the Visual Studio thing, some of those include extending SharePoint Tools, exploring SharePoint Explorer and also understanding and working with the Feature and Package designer.
What to install?
When you get into the sea of options, the first thing to consider is … What do I need?
Chances are you are not going to be working with either C++ or F# (not discounting the languages, just their likelihood of being used for this purpose), we can then take those two out. Next, you do not need the express installation for SQL Server 2008, and there are other components you will not use.
When launching the installer, select custom installation and your selected items can look like this:
As for Visual Basic and C#, it will depend on your experience and level of comfort.
What resources are available to go deeper into this?
You should create a Virtual Machine, yes even if SharePoint 2010 does install on Windows 7… create a development VM.
There are several resources available already to make this happen.
Critical Path Training’s VM Setup Guide, a couple of things to mention:
- You will need to create a profile and an account to access the resource.
- The first portion is focused on Hyper-V, but you can use the virtualization technology you are most comfortable with.
MSDN has an article on creating the Development Environment.
Hope this helps as you get going, more to come with more details on the full process I used, including Team Foundation Server and Project Server.