locked
SharePoint Development RRS feed

  • Question

  • We have SharePoint Server 2010 in a production environment installed on Windows Server 2008, but do not have a development environment for creating web parts, etc..  Is there a license cost for creating a development environment?  Also, if we create a development environment in Windows 7 on our desktops, should we also create a another test environment with the same operating system as Production.  Are there known compatibility problems with deploying a web part developed in Windows 7 onto a SharePoint site in Windows Server 2008?


    • Edited by TWOLFE1871 Thursday, January 3, 2013 8:55 PM
    • Moved by Hemendra Agrawal Friday, January 4, 2013 4:53 AM (From:SharePoint Legacy Versions - Setup, Upgrade, Administration and Operations)
    Thursday, January 3, 2013 8:06 PM

Answers

  • Development environments are covered under MSDN licensing.

    You can use Windows 7, it's supported. It's generally not a good method. If your development environment closely matches production you'll reduce the risk that what you develop won't work in production. In theory however a web part shouldn't care what OS is on the server.

    Microsoft has a good guide on setting up a SharePoint 2010 development environment.


    Jason Warren
    Infrastructure Architect

    • Proposed as answer by Bjoern H Rapp Friday, January 4, 2013 8:20 AM
    • Marked as answer by Bjoern H Rapp Monday, January 7, 2013 10:22 PM
    Thursday, January 3, 2013 10:38 PM
  • I belive you can use the trial version SP2010 VHD provided here http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=27417

    with trial version of visual studio


    Raghavendra Shanbhag | Blog: www.SharePointColumn.com
    Please click "Propose As Answer " if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
    Disclaimer: This posting is provided "AS IS" with no warranties.

    • Proposed as answer by Bjoern H Rapp Friday, January 4, 2013 8:20 AM
    • Marked as answer by Bjoern H Rapp Monday, January 7, 2013 10:22 PM
    Friday, January 4, 2013 7:37 AM
  • hi

    in most cases it is not a good idea to have both development and production environments on the same server. Better option is to virtual environment with single-server Sharepoint installation (i.e. when all roles will be in single virtual image: WFE, app server, db server) and then copy it to your developers when they will need it. For virtual environment you may use VMWare or HyperV (I prefer VMWare, but you can use any). Such method have many advantages: you need to invest to setup environment only once and you may do snapshots and revert machine to the stable state if something will go wrong, which is not so simple with real physical environment (although it is also possible).

    About OS: Sharepoint is server technology and it is better to use Windows Server OS for installation. With Windows 7 you will have problems even with developing regular ASP.Net applications, because many components are missing from default installation. And for sure you will have unnecessary problems with Sharepoint development in this case. It is possible to solve them, but if you will work with Sharepoint you will have enough things to investigate even if you will do everything as recommended, so it is better to avoid problems which can be avoided and concentrate on the actual tasks. And of course if you need test env, it is better to use similiar configuration to production env (same OS, same Sharepoint patch level, same customizations).


    Blog - http://sadomovalex.blogspot.com
    CAML via C# - http://camlex.codeplex.com

    • Proposed as answer by Bjoern H Rapp Friday, January 4, 2013 8:21 AM
    • Marked as answer by Bjoern H Rapp Monday, January 7, 2013 10:22 PM
    Friday, January 4, 2013 8:11 AM

All replies

  • Development environments are covered under MSDN licensing.

    You can use Windows 7, it's supported. It's generally not a good method. If your development environment closely matches production you'll reduce the risk that what you develop won't work in production. In theory however a web part shouldn't care what OS is on the server.

    Microsoft has a good guide on setting up a SharePoint 2010 development environment.


    Jason Warren
    Infrastructure Architect

    • Proposed as answer by Bjoern H Rapp Friday, January 4, 2013 8:20 AM
    • Marked as answer by Bjoern H Rapp Monday, January 7, 2013 10:22 PM
    Thursday, January 3, 2013 10:38 PM
  • I belive you can use the trial version SP2010 VHD provided here http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=27417

    with trial version of visual studio


    Raghavendra Shanbhag | Blog: www.SharePointColumn.com
    Please click "Propose As Answer " if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
    Disclaimer: This posting is provided "AS IS" with no warranties.

    • Proposed as answer by Bjoern H Rapp Friday, January 4, 2013 8:20 AM
    • Marked as answer by Bjoern H Rapp Monday, January 7, 2013 10:22 PM
    Friday, January 4, 2013 7:37 AM
  • hi

    in most cases it is not a good idea to have both development and production environments on the same server. Better option is to virtual environment with single-server Sharepoint installation (i.e. when all roles will be in single virtual image: WFE, app server, db server) and then copy it to your developers when they will need it. For virtual environment you may use VMWare or HyperV (I prefer VMWare, but you can use any). Such method have many advantages: you need to invest to setup environment only once and you may do snapshots and revert machine to the stable state if something will go wrong, which is not so simple with real physical environment (although it is also possible).

    About OS: Sharepoint is server technology and it is better to use Windows Server OS for installation. With Windows 7 you will have problems even with developing regular ASP.Net applications, because many components are missing from default installation. And for sure you will have unnecessary problems with Sharepoint development in this case. It is possible to solve them, but if you will work with Sharepoint you will have enough things to investigate even if you will do everything as recommended, so it is better to avoid problems which can be avoided and concentrate on the actual tasks. And of course if you need test env, it is better to use similiar configuration to production env (same OS, same Sharepoint patch level, same customizations).


    Blog - http://sadomovalex.blogspot.com
    CAML via C# - http://camlex.codeplex.com

    • Proposed as answer by Bjoern H Rapp Friday, January 4, 2013 8:21 AM
    • Marked as answer by Bjoern H Rapp Monday, January 7, 2013 10:22 PM
    Friday, January 4, 2013 8:11 AM