Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

It looks like the tools for developing SharePoint 2013 customizations are mostly in Visual Studio 2012 and "Napa for Office 365."

If you've tried developing solutions for SharePoint 2013 in Visual Studio 2010, what has worked for you?

share|improve this question

4 Answers 4

up vote 5 down vote accepted

To add to Hugh's answer, almost anything you can do in VS 2010 for SP10 works in SP13 (event receivers, web parts, etc.), but nothing new, or not much of the new features work in VS2010 because much of them are new templates and data techniques such as the app model, remote event receivers, etc.

The App model requires the ability to do remote development which is built into VS 2012, but not 2010 and the SharePoint add on for VS is for 2012, not 2010.

By the way, it is Visual Studio 2012, not 2013, confusing, I know.

A positive push for VS 2012 is that remote development and deployment is allow, which matches Microsoft's push towards SharePoint online (office 365).

share|improve this answer
    
Thanks for catching the 2013 typo. –  Tom Resing Oct 23 '12 at 0:27
    
Everything I've read regarding remote development has been geared towards apps. Can we deploy/debug solutions remotely is the only way to debug/deploy through VS is if you're doing it on the server? I can't seem to get that figured out -- especially when "app" refers to anything you can do to a SharePoint site. –  EHorodyski Feb 25 '13 at 21:45
    
From what I have seen, you can deploy anything remotely because you are allowed to log into remote servers from VS now. The server requirements for 2013 makes it harder to have it installed on individual developer VMs. –  Sam Sussman Feb 25 '13 at 23:53

You can actually do loads still with VS2010 in SharePoint 2013. We do exactly that for DocRead (no time to upgrade to 2012). Check my post on supporting multiple versions of SharePoint from 1 VS Solution.

I just made an update to this article as I forgot to compile against .Net 4.0

share|improve this answer
    
Thanks for the link to your great article, @Mark jones. In summary, would you say that everything you need to do for SharePoint 2013 Development is available in VS2010 then? –  Tom Resing Jan 8 '13 at 16:22

Some relevant article you can find here: http://faisalrafique.wordpress.com/2012/12/09/whats-new-for-sharepoint-development-in-visual-studio-2012/

share|improve this answer
    
Welcome to SharePoint.SE! While this may theoretically answer the question, we prefer inclusion of the essential parts of the answer here, and to provide the link for reference. See How to Answer for general guidelines. –  Kit Menke Jan 4 '13 at 15:08
    
I agree with Kit. If you update your question with a summary of the content relevant to Visual Studio 2010 I would give an up vote. –  Tom Resing Jan 4 '13 at 15:22

It seems to work for the most part, but I am not confident about things like workflows as I have had two not work now which work on 2010.

We are in the middle of upgrading visual studio now though, as a company we don't believe the risks of incompatibility outweigh the costs.

share|improve this answer
    
Thanks, Hugh. Workflow makes sense because the custom workflow model is different in 2013. Have you tried installing the App Model tools? I don't imagine those would work either. –  Tom Resing Oct 22 '12 at 12:25
1  
Yes we tried during our review before our license was updated, this was the point where we stopped testing however, we can't risk being incompatible even by 1%. –  Hugh Wood Oct 22 '12 at 12:27

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.