Sign in
Microsoft.com
 
Microsoft
 
 
 
Microsoft > Forums Home > SharePoint - General Question and Answers and Discussion (pre-SharePoint 2010) > Visual Studio 2005 / 2008 to develop in SharePoint.

Answered Visual Studio 2005 / 2008 to develop in SharePoint.

    •  
      Tuesday, November 25, 2008 12:10 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hello again friends,

      What is the best environment to develop MOSS based application?. I have read that 2008 offers more benefits but also some drawbacks...

      Regards
      Computer Engineering
       

    Answers

    • Tuesday, November 25, 2008 2:25 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      Recommendation: Have both on your environment? It should be fine to have both 2005 and 2008 installed on your dev's. We did this for SharePoint 2003 development where we had 2003 and 2005 on our dev boxes, gives you the best of both worlds.

      It really depends on what/how you develop. Technically you can do anything in 2008 you can do in 2005 it just gets alot 'harder' sometimes. As an example the extensions for 2005 (for wss) don't necessarily work with 2008. (Personally I don't really use these that much though, so again it depends on how you develop.)

      Workflow's can be annoying as well because some SPD ones and some built in 2005 will have issues moving to the 2008 platform, theres some deployment things that people miss (related to infopath, etc)....

      That said I love some of the new features of 2008 and when it comes to writing some powerful UI aspects, webparts, features, site defs, list defs etc I normally use 2008. I still use 2005 for my workflow development only because we have lots of older projects that we use for reference or tie into regularly and these are all built in 2005 (don't want to take on the hassle of upgrading and doing the time consuming testing). 2005 has just been around for awhile and it's use and community have resulted in lots of powerful extensions and features for SharePoint that 2008 just hasn't caught up with quite yet.

      Anyways that's my two cents on it, hope it helps and doesn't hinder,
      Richard Harbridge
       
    • Tuesday, November 25, 2008 5:37 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      It's only a problem if you are on a 64Bit system.  The extensions won't install on 64bit, however there is a workaround.

      http://marclenferna.com/blog/archive/2008/11/22/installing-visual-studio-extensions-for-wss-on-x64-server.aspx
      Robert Stark MCTS - MOSS 2007 MCTS - WSS 3.0 ---www.thesharepointranch.com --- cas.excell.com
       

    All Replies

    • Tuesday, November 25, 2008 2:25 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      Recommendation: Have both on your environment? It should be fine to have both 2005 and 2008 installed on your dev's. We did this for SharePoint 2003 development where we had 2003 and 2005 on our dev boxes, gives you the best of both worlds.

      It really depends on what/how you develop. Technically you can do anything in 2008 you can do in 2005 it just gets alot 'harder' sometimes. As an example the extensions for 2005 (for wss) don't necessarily work with 2008. (Personally I don't really use these that much though, so again it depends on how you develop.)

      Workflow's can be annoying as well because some SPD ones and some built in 2005 will have issues moving to the 2008 platform, theres some deployment things that people miss (related to infopath, etc)....

      That said I love some of the new features of 2008 and when it comes to writing some powerful UI aspects, webparts, features, site defs, list defs etc I normally use 2008. I still use 2005 for my workflow development only because we have lots of older projects that we use for reference or tie into regularly and these are all built in 2005 (don't want to take on the hassle of upgrading and doing the time consuming testing). 2005 has just been around for awhile and it's use and community have resulted in lots of powerful extensions and features for SharePoint that 2008 just hasn't caught up with quite yet.

      Anyways that's my two cents on it, hope it helps and doesn't hinder,
      Richard Harbridge
       
    • Tuesday, November 25, 2008 3:18 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hello Richard,

      Thanks for your answer.

      I think this is the best solution, but i thought to use 2008 to develop sharepoint workflows, using 1.2 sharepoint extensions...is there any problem with this?, i don't know if this is a great idea.
      Computer Engineering
       
    • Tuesday, November 25, 2008 5:37 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      It's only a problem if you are on a 64Bit system.  The extensions won't install on 64bit, however there is a workaround.

      http://marclenferna.com/blog/archive/2008/11/22/installing-visual-studio-extensions-for-wss-on-x64-server.aspx
      Robert Stark MCTS - MOSS 2007 MCTS - WSS 3.0 ---www.thesharepointranch.com --- cas.excell.com
       
    • Wednesday, November 26, 2008 4:53 AM
      Moderator
       
       
      Sign In to Vote
      0
      Sign In to Vote
      If you are starting a fresh development, i'd recommend you to go with VS 2008
      Sundar Narasiman
       
    • Wednesday, November 26, 2008 2:18 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Also of note, there are 2 versions of extentions.  V1.1 is for VS05.  V1.2 is for VS08.

      - M
      - Michael Mukalian - MCTS: MOSS 2007 Configuration - http://moss2007stuff.blogspot.com