Saturday, July 3, 2010

Sharepoint 2010 problems for old MOSS developers?

My biggest problem with Sharepoint 2010 right now is it killed the standalone developer support that does not have a killer machine.

On MOSS 2007 I was used to running a VM network on my laptop (or dekstop server) with Moss 2007 on one VM, Domain server on another VM and my dev environment on a 3rd VM (sometimes this is reserved for an ISA server or Biztalk depending on the requirements).

This makes sure I could develop and debug my applications without being connected to a dev server, as well as making sure that if i ever screwed up my VM I could just plug in another one from my backups.

Sharepoint 2k10 now killed this concept with the requirements of having SQL Server 64bit and Windows 2008 Server r2 64bit.

since most mid range laptops are running on 32bit OS and VMWare / Virtual PC doesn't support CPU virtualization, I'll be stuck with SPS2k10 running on my dekstop and my dev environment running on my laptop for now.

you could also use this tool to check if your laptop could support 64 bit VM

for now... I'll postpone migrating my environments until I could properly backup my laptop and change it from Windows 7 32 bit to 64 bit (and download all the requirements which with the problems I'm getting from my ISP could probably take me 3 years to finish.)

I also wonder...how painful would it be to migrate my web parts, custom controls and Portal. Hope it's not as painful as migrating from 2003 to Moss :P

No comments:

Post a Comment