I have reformatted my machine and am running Window 7 Ultimate (64-bit). I anticipate needing to do some SharePoint development. I'm currently in the process of installing my software. I've read this MSDN article. However, what the article doesn't tell me is which order I need to install the following:
SQL Server 2008 R2
Visual Studio 2010
SharePoint 2010
Office 2010
Can anyone tell me which order I need to install these items in? I want to make sure that I get it right. Normally, I would do SQL Server 2008 R2, Visual Studio 2010, Office 2010 However, with SharePoint 2010 thrown into the mix, I'm not sure what the order should be. Can anyone provide some insight?
Thank you!
Good question, one I should've asked before setting up SharePoint. I recall wishing I had installed VS prior to SharePoint, and the database has to exist for SharePoint to use, so I would recommend:
1.) Office
2.) Visual Studio
3.) SQL Server
4.) SharePoint
Also, you have the advantage of Windows 7. Create a step-named restore point before each installation (it will save you loads of trouble if you have to back up). In fact, if I were in your position I'd create a restore point and try the Easy Setup Script they link in that MSDN article. Good luck, hope it helps.
SQL Server before Sharepoint.
Rest in any order.
Related
Does anyone have a walkthrough or video on how to use Sync Framework in VS 2013? I've seen nice examples using VS 2010 but some important items like local database cache object have been deprecated.
For what I have read is that LocalDB will be replacing the Sql Compact (which is deprecated). But have not found a site explaining how things should work. My solution for what I understand would be a LocalDB syncing with a SQL Server with IIS using WCF. Any pointers would be appreciated.
there's no equivalent for the Local Database Cache project wizard in VS 2013. if you want to do what the wizard does, you can hand code it yourself. but that will be using the older sync providers.
you can find a walkthrough of how to achieve this with the newer sync providers here. The SqlSyncProvider should work with SQL Server/Express/LocalDB/Azure. You can also still SQL CE if you want to.
I'm in the middle of what Microsoft calls an advanced TFS 2013 installation on new hardware. I want to point it at my current database running TFS 2010 on a different server and wanted to know if I can do this or if there are any tools available to upgrade the existing database.
I upgraded the SQL Server running the TFS2010 databases to SQL Server 2012 and can connect so that is not an issue. I'd like to keep the same databases for obvious reasons and could not find any info on a road map to do so.
Anybody have any insight?
Thanks.
Just in case anyone comes in here and is looking for an answer. It is possible to install TFS2013 on one box and point to databases that were created in TFS2010, but those databases must be converted to SQL Server 2012.
What I did was to upgrade our SQL Server from 2008 to 2012 and the tfs databases were still accessible to users on tfs 2010. Then you go to the tfs 2013 administrator and attach a collection. You put your server name into the available servers edit control and you'll see your project collection database. The first part of the attach process is an evaluation and if something bad happens, at least it's in the analysis phase. Make sure you have a database backup and then click through so that the operation starts.
After the database is attached through tfs, you have some work in sql server to do. First detach the collection in tfs 2013. Then, in sql server, backup the project collection database again and copy it to your new tfs 2013 server running sql server. Then, again in sql server, detach the database.
Then go back to tfs 2013 and in sql server restore from the backup you created. Once that is done, in the tfs 2013 interface attach the collection and you're good to go.
Hope this helps.
I need advise on what can be best way to setup/configure SHAREPOINT 2010 Environment for 6-members teams (with 3-working at onsite and 2-working at offshore)
Currently I only had two team members but team is now increasing. What we have is DEVELOPMENT SERVER - with Visual Studio and SharePoint Server installed. Developers remote VNC to the box and do their development.
But with number of developers are increasing what should be ideal, so that team can communicate from offshore/onshore
Is this Ideal (installed on each developer laptop)
Visual Studio 2010
and
SharePoint Server (Installed on Windows Server 2008) and developers will use this rather than installing SharePoint locally (enterprise edition is very expensive)
We start to developing with SharePoint 2010 in the team one and half years ago. We try different environment structures for developing, but had many conflicts. Today everyone work in his own environment (HV) with SP enterprise edition, just sharing the code via Team System. The problem is in this set-up the content, everybody has his special content, but if it is critical for you, make backup in every environment.
So we have one SQL server, and for every developer a server with SP and VS.
By the way I think you don't need to purchase SharePoint Server for development environment. If I'm right it is free. You need purchase OS, Sql, VS, but not the SP. Please check with your Microsoft seller.
I'm relatively new at creating custom content for Sharepoint 2010 and have been having some difficulty understanding how to get non-design related components (ie. web parts, custom classes, ...) into a Sharepoint site. I have created a new visual web part on the company's development server and deployed it successfully from Visual Studio 2010 and also packaged the solution into a WSP file.
What is the best way to go about getting that web part onto the production server? There is currently no Visual Studio install on the production server but from searching around I get the feeling that it might be possible to do this remotely using Powershell or STSADM. Has anyone faced a similar situation?
Use PowerShell. Stsadm is considered to be obsolete and is included in SharePoint 2010 only for backwards compatibility with SharePoint 2007. So, since you are new to SharePoint, pretend Stsadm doesn't even exist.
My PowerShell scripts keep evolving, but they are based on samples from Ted Pattison:
Chapter 2: SharePoint Foundation Development (scroll down to Using Windows PowerShell Scripts to Automate Tasks in Visual Studio)
PowerShell Boot Camp for SharePoint Professionals
I plan to have VS 2010 on my local box, and I'm building a VM with SP 2010 and SQL Server 2008.
What hard drive size should I shoot for on the VM?
I would recommend to create a fixed-sized(for better performance) hard drive which is at least 50GB big.
I've built SP2010 development machine the other day and after installation of VS2010, SP2010, SQL Server 2008, Office 2010, Sharepoint Designer and some other tools I had about 15-20 GB of empty space which is quite good to have for other stuff.
UPDATE: If you have a chance, take a look at this book. In first chapter author describes in details how to set up a perfect sharepoint2010 development machine.