Answered by:
Develop. NET in sharepoint online

Question
-
Hello,
I'm Developer Sharepoint 2010 and am migrating to 2013 ..
And I have some doubts about development. NET + SharePoint 2013!
- I wonder if with the online sharepoint I can develop web parts and application page with Visual Studio and deploy to?
- Apply the "Install-SPSolution" command in power shell?
- Upload wsp in site settings-> Solutions ?
- How do I develop. NET in Sharepoint Online?
Can anyone help me?
Thank you!- Edited by jorfla Monday, June 2, 2014 8:57 PM
Monday, June 2, 2014 8:37 PM
Answers
-
as Paul mentioned , you can use Sandbox solutions for user code it's deprecated but for the provisioning code it's still supported.
The other option is to build a .NET based provider hosted app that uses the client object model to access SharePoint and instead of having webpart you can create app parts which is simply aspx pages rendered in an iframe in the host (sharePoint) site
http://msdn.microsoft.com/en-us/library/office/fp142381(v=office.15).aspx
Hope that helps|Amr Fouad|MCTS,MCPD sharePoint 2010
- Marked as answer by jorfla Tuesday, June 10, 2014 8:05 PM
Monday, June 2, 2014 8:58 PM -
The provider hosted app parts are the better choice going forward. But they will take some extra work for SharePoint ONline since you need to have a server to run the .Net code on somewhere. The most common solution tends to be a web site in Azure.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.- Marked as answer by jorfla Tuesday, June 10, 2014 8:05 PM
Tuesday, June 3, 2014 12:48 PM
All replies
-
Server side code written in .Net can only be used in Sandbox solutions in SharePoint ONline, and those are deprecated and will be going away eventually. Here's a video on getting started developing Sandbox solution based web parts in SharePoint 2010. Its the same process.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.- Proposed as answer by Amr FouadMVP Monday, June 2, 2014 9:43 PM
Monday, June 2, 2014 8:52 PM -
as Paul mentioned , you can use Sandbox solutions for user code it's deprecated but for the provisioning code it's still supported.
The other option is to build a .NET based provider hosted app that uses the client object model to access SharePoint and instead of having webpart you can create app parts which is simply aspx pages rendered in an iframe in the host (sharePoint) site
http://msdn.microsoft.com/en-us/library/office/fp142381(v=office.15).aspx
Hope that helps|Amr Fouad|MCTS,MCPD sharePoint 2010
- Marked as answer by jorfla Tuesday, June 10, 2014 8:05 PM
Monday, June 2, 2014 8:58 PM -
The provider hosted app parts are the better choice going forward. But they will take some extra work for SharePoint ONline since you need to have a server to run the .Net code on somewhere. The most common solution tends to be a web site in Azure.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.- Marked as answer by jorfla Tuesday, June 10, 2014 8:05 PM
Tuesday, June 3, 2014 12:48 PM