SharePoint Use Cases

  • Home
  • About
  • Our Tools
  • Contact me
SharePoint

Question about your article – Setting up SharePoint Environment

Toni Frankola - August 17, 2009

Stan emailed me with few questions about setting up SharePoint Development Environment. I am posting edited version of that conversation here. The post is general and it applies to any SharePoint environment e.g. testing, educational… you might have in your company.

In your article “Team-Based Development in Microsoft Office SharePoint Server 2007 – Part 2 – Building a development lab” you say that developer has 64-bit Server on the machine and VPC and develops in VPC. Why do you need VPC? The max RAM I can get out of my VPC is 2.3GB, while you can have 3.3 on the server. Can you explain?

32bit Windows XP operating system can only address up to 4GB of RAM. This is the limitation you are hitting here. You should switch to 64bit operating system. Check this article for full list of maximal RAM addressed by various Microsoft operating systems.

Thank you Toni. The other question was about whether to use virtualization or not. Once PC has server OS, why not just develop on it?

If possible you should run your host operating system on 64bit platform and on Windows 2008 if possible. It can address a lot of RAM and it is much faster than other virtualization technology. You do not expensive hardware, any entry-level server or more powerful desktop will do.

The problem with SharePoint is that it is not a simple .NET application. For example you cannot revert certain actions easily (like installing Service Packs, new versions and stuff). In case you are doing everything on top of your server (without virtual machines) it would be much harder to revert to previous state. It can be done, but not easily. And sometime you might figure out that after weeks of testing you cannot use SharePoint Service Pack 2 because some 3rd party application does not work correctly. You will not be able to go back. Sometimes you even need to work on old system while you are testing a new upgrade, if you have only one machine than this might be a problem…

In case you need to support more than one client, you should stick with virtual machines. Each client has a different SharePoint installation; here are some of the options:

1) Operating systems: Windows 2003/2003 R2/2008/2008 R2

2) Platform: 32bit / 64bit

3) Service Pack: None / SP1 / SP2

4) Edition: WSS/SharePoint Standard/SharePoint Enterprise

5) SQL: 2000/2005/2008 (plus Service Packs)

6) Farm configuration: Basic, Single Server, Farm…

and the list goes on and on.

Some clients might also have some additional software on top of SharePoint…

So my advice is: always use Virtual Machines. Recreate exactly the same environment as your client does and stick to it as much as possible.

Thanks a lot for the very detailed answer. We are in the process of building SharePoint lab and were debating the issue of VM / no VM when I came across your article on the web. It is exactly what we need! We’ll go with Win 2008 Standard Edition w Hyper V (x64) as a development environment. The only kicker I heard related to 64bit / 32bit, is that Workflow development environment relies on 32-bit dlls, but that’s fine – we can have 32-bit guest for that purpose…

You can have 32bit VM guests on 64bit host, but you cannot do the other way around… so I would go for 64bit.

Bear in mind that SharePoint 2010 will work only on 64bit Windows 2008 and it will also require SQL Server 2005 / 2008 64bit. If possible plan ahead now.

Tags | sharepoint development, virtual machines, vm
 0
Share Now

Toni Frankola

Entrepreneur, IT consultant, speaker, blogger, and geek. Co-founder of syskit.com.

You Might Also Like

SharePoint

Team-Based Development in Microsoft Office SharePoint Server 2007 – Part 2 – Building a development lab

December 21, 2008
Previous Post SharePoint in plain English
Next Post Use case: PhoneBook Search – no code required

Archives

  • December 2021 (1)
  • June 2021 (1)
  • January 2021 (1)
  • July 2019 (1)
  • June 2019 (2)
  • March 2019 (1)
  • February 2019 (3)
  • October 2018 (2)
  • August 2018 (2)
  • June 2018 (1)
  • April 2018 (1)
  • February 2018 (1)
  • January 2018 (1)
  • June 2017 (1)
  • April 2017 (1)
  • February 2017 (1)
  • November 2016 (2)
  • August 2016 (1)
  • July 2016 (2)
  • March 2016 (1)
  • February 2016 (2)
  • January 2016 (1)
  • November 2015 (2)
  • December 2014 (1)
  • November 2014 (2)
  • July 2014 (2)
  • June 2014 (2)
  • May 2014 (1)
  • April 2014 (2)
  • March 2014 (1)
  • February 2014 (4)
  • January 2014 (2)
  • December 2013 (1)
  • September 2013 (1)
  • July 2013 (1)
  • June 2013 (1)
  • May 2013 (1)
  • April 2013 (3)
  • February 2013 (1)
  • December 2012 (1)
  • November 2012 (1)
  • September 2012 (1)
  • August 2012 (1)
  • July 2012 (2)
  • June 2012 (4)
  • April 2012 (1)
  • February 2012 (1)
  • January 2012 (1)
  • November 2011 (2)
  • October 2011 (2)
  • September 2011 (2)
  • July 2011 (3)
  • May 2011 (2)
  • April 2011 (1)
  • March 2011 (4)
  • February 2011 (3)
  • January 2011 (4)
  • December 2010 (4)
  • November 2010 (3)
  • October 2010 (3)
  • September 2010 (4)
  • August 2010 (1)
  • July 2010 (4)
  • May 2010 (2)
  • April 2010 (2)
  • March 2010 (3)
  • January 2010 (2)
  • December 2009 (3)
  • November 2009 (5)
  • October 2009 (2)
  • August 2009 (7)
  • July 2009 (3)
  • June 2009 (4)
  • May 2009 (3)
  • April 2009 (5)
  • March 2009 (8)
  • February 2009 (5)
  • January 2009 (8)
  • December 2008 (9)
  • November 2008 (8)
  • October 2008 (7)
  • September 2008 (4)
  • August 2008 (6)
  • July 2008 (5)
  • June 2008 (3)
  • May 2008 (4)
  • April 2008 (6)
  • March 2008 (4)
  • February 2008 (3)
  • January 2008 (6)
  • December 2007 (1)
  • November 2007 (3)
  • October 2007 (3)
  • September 2007 (2)
  • August 2007 (1)
  • July 2007 (12)
  • June 2007 (2)
  • May 2007 (3)

Connect Us

All postings on this blog are provided “AS IS” with no warranties, and confer no rights. All entries in this blog are my opinion and don’t necessarily reflect the opinion of my employer.

  • Home
  • About
  • Our Tools
  • Contact me

Copyright (c) Toni Frankola 2008. - 2019.