SharePoint extensions
- Is there plan to host user extensions to sharepoint (like VisualStudio workflows, webparts)? May i develop my own workfow, timer jobs, handlers etc in visual studio and deploy it to the SharePoint Online?
Answers
In our initial release, you will not be able to deploy code to the service. This means no Web Parts, timer jobs, custom workflows, or forms with managed code. You will be able to extend SharePoint Online in many other ways.
Because we're still in Beta, we haven't fully tested all the extensibility mechanisms yet, but our intent is for you to be able to:
· Use SharePoint designer to create and deploy no-code workflows, customize content types, taxonomy and branding via master pages and layouts, and create and deploy site templates.
· Use the Data Form Web Part to create applications that mashup, filter, roll-up and render SharePoint data or data consumed from a Web Service (e.g. RSS feeds) in new ways.
· Use InfoPath to design forms for workflows, provided these forms are user-deployable (i.e. contain no custom code).
· Use the SharePoint Web Services to access and manipulate SharePoint data remotely.
If you're in a position to test out any of these extensibility points (e.g. write code that calls our Web Services, or customize the Data Form Web Part to consume (for e.g.) an RSS feed, I'd love to hear how well it works for you.
Examples of things you will not be able to do:
· Use inline code, build coded workflows, or develop InfoPath forms with coded business logic.
· Deploy features, solutions, pluggable auth providers, Web Parts, site definitions, or anything else that has to be deployed and configured on the server.
· Modify any SharePoint files, Web.config settings, security policy, etc.
· Make any farm-wide configuration changes (i.e. changes that must be made in Central Admin).
Going forward, we will endeavor to enable more and more developer functionality in the service.
All Replies
In our initial release, you will not be able to deploy code to the service. This means no Web Parts, timer jobs, custom workflows, or forms with managed code. You will be able to extend SharePoint Online in many other ways.
Because we're still in Beta, we haven't fully tested all the extensibility mechanisms yet, but our intent is for you to be able to:
· Use SharePoint designer to create and deploy no-code workflows, customize content types, taxonomy and branding via master pages and layouts, and create and deploy site templates.
· Use the Data Form Web Part to create applications that mashup, filter, roll-up and render SharePoint data or data consumed from a Web Service (e.g. RSS feeds) in new ways.
· Use InfoPath to design forms for workflows, provided these forms are user-deployable (i.e. contain no custom code).
· Use the SharePoint Web Services to access and manipulate SharePoint data remotely.
If you're in a position to test out any of these extensibility points (e.g. write code that calls our Web Services, or customize the Data Form Web Part to consume (for e.g.) an RSS feed, I'd love to hear how well it works for you.
Examples of things you will not be able to do:
· Use inline code, build coded workflows, or develop InfoPath forms with coded business logic.
· Deploy features, solutions, pluggable auth providers, Web Parts, site definitions, or anything else that has to be deployed and configured on the server.
· Modify any SharePoint files, Web.config settings, security policy, etc.
· Make any farm-wide configuration changes (i.e. changes that must be made in Central Admin).
Going forward, we will endeavor to enable more and more developer functionality in the service.
David Gorbet [MSFT] wrote: - Use the Data Form Web Part to create applications that mashup, filter, roll-up and render SharePoint data or data consumed from a Web Service (e.g. RSS feeds) in new ways.
David,
Do you have any links to screencasts and/or demos that show how to go about doing this? I will have customers that need this type of functionality, however I don't really know where to begin. Any help would be much appreciated. Thanks.
Wow, sorry so far behind... You can start here: http://blogs.msdn.com/sharepointdesigner/archive/2007/04/24/spdatasource-and-rollups-with-the-data-view.aspx
- Hey ,
I need to do branding in one of the site created in sharepoint online services using sharepoint designer.
Could you please share some links or post where i can go and refer ?
Do we have options of using an alternate URL for the CSS in sharepoint online services ?
Do we have the option of overriding core.css in sharepoint online services ?
Can we create a custom theme in sharepoint online services ?
" Use SharePoint designer to create and deploy no-code workflows, customize content types, taxonomy and branding via master pages and layouts, and create and deploy site templates. " - You can start here: http://msdn.microsoft.com/en-us/library/aa830818.aspx. We also recently published a guide to customization and extensibility here: http://www.microsoft.com/downloads/details.aspx?FamilyID=d007f35e-375c-4b11-bc40-bc9082bb224a&displaylang=en
David Gorbet, Principal Program Manager, SharePoint Online - Hello,
I recently read SharePoint Online Standard Service Description, at the bottom of the document there is multiple tables which compare Dedicated to Standard solutions and especially Table 11. Within it, I see:
Server-side custom code
Yes
No
Pre-production environment
Yes
No
As I was seeking about Custom code I discovered this post : http://www.wictorwilen.se/Post/Custom-code-with-SharePoint-Online-and-Windows-Azure.aspx
Is it possible to create my own solution package (.wsp) in order to deliver into pre-production and then into production my customs Features?
Can my custom feature be just CAML (fields, content type, list definition,...)?
Can my custom feature be more than CAML (.dll, .aspx)?
Is their a case study which describes how to work with online services appart from UI manual customization which will not be accepted by my company?
Regards- Edited byWoZoI Wednesday, October 28, 2009 8:11 AMmore information
