Link to home
Start Free TrialLog in
Avatar of Demosthenes
Demosthenes

asked on

How to code SharePoint 2013 online

I have been reading all over the internet trying to find out how to code SharePoint 2013 online.  I wanted to be able to make Visual Web Parts but after going down that road, I now read that Microsoft shut off Sandboxed Solutions ?  Can anyone give me a clear explanation of how to code C# in SharePoint 2013 online ?

With C# I can do anything, connect to azure databases, sharepoint lists, take over the DOM and make my own pages etc etc etc.  Is there still a way to do all the things I could do with C#.  If  C# is indeed no longer allowed, what do you use ?
ASKER CERTIFIED SOLUTION
Avatar of Jamie McAllister
Jamie McAllister
Flag of Switzerland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Demosthenes
Demosthenes

ASKER

So, you will never write and deploy compiled C# code to SharePoint Online. Ever!

Wow.  Ok, finally a clear answer !  Thank you much.
To be fair I mostly work with SharePoint on-premises, but even there I avoid deploying code to SharePoint itself whenever possible. (As soon as I saw what Microsoft were aiming at with SharePoint 2013 and the App Model I saw where future investment from MS was going to go)

I write solutions in C# and even powershell. These tend to use the Client Object Model to call into SharePoint to retrieve or manipulate data. They're deployed to other servers in my org, and often use least privileged service accounts to operate. (Quite often batch processing due to nature of the business).

I also write javascript that I deploy to SharePoint (store in libraries and on pages). This javascript often also uses the Client Object Model to retrieve or manipulate data.

Beyond this I also use K2 Blackpearl, which gives me powerful electronic form and workflow capabilities I couldn't get from native SharePoint. (Deployed to a K2 server, once again not touching the SharePoint servers themselves).

I partially documented my ethos in this blog post in 2013; http://the-north.com/sharepoint/post/Alternatives-to-SharePoint-Timer-Jobs
Great info Jamie, thanks...