In the new SharePoint 2013 App model, there are essentially two ways to host apps – within SharePoint itself or from an external web site (also known as “provider hosted” or “autohosted”). One of the disadvantages of external apps is that they don’t look or feel like SharePoint. All the familiar navigation menus and shortcuts are missing, resulting in a stark contrast between the default SharePoint visual experience and whichever app is currently being used unless the app developer went the extra mile (or ten) to style their app.
The title talks about itself …
• Developing on the cloud. No need to install anything, you can write your code, build, deploy all on the cloud,
• No need for more RAMs as SharePoint 2013 and Visual Studio 2012 requires,
• You can start developing for Office and SharePoint without having to install Visual Studio 2012,
• You only need good Internet access
SharePoint 2013 applicaiton model is very strong approach for developer to leverage there skil and developer wornderful apps except using any sever side code. as we know Sandbox solution is deprecating in sharePoint 2013 because of so many ressones. but SharePoint 2013 open new door for developer to develop,market,earm Apps.
SharePoint 2013: Business Connectivity Services – Consuming OData in BCS using an App External Content TypeBlog Posts
As most if not all of you already know, SharePoint 2013 and Office 2013 has been released to preview/beta and is available for download from Microsoft’s download centers. In this article I will briefly introduce some exciting changes that has been made to the SharePoint 2013 Business Connectivity Services framework. I’ve written a bunch of articles on BCS for SharePoint 2010, and now it’s time to continue that track and introduce the new features available in SharePoint 2013.
A lot of new things are introduced with the SharePoint 2013 Preview, released by Microsoft just a few days ago. Many of these “things” are expected and seem as a natural continuation of existing functionality. SharePoint Apps feel a little different. It’s completely new! Or is it?
SharePoint 2013 introduces a new mechanism for custom code deployment known as “Apps”. Mostly targeted at online solutions, the purpose of the App model is to overcome the severe limitations of the 2010 isolated execution model (also known as the “Sandbox”) and provide developers with a way to run rich web applications in SharePoint without negatively impacting the underlying infrastructure. Much has already been made about this new model and a lot more will be written about it over the coming year as 2013 gets released and adoption spreads. Before we get too far off the beaten track into a debate about whether or not developers should or should not be using the new App model, it’s helpful to first understand why Microsoft chose this path and what it really means for both new application developers coming onto the platform and existing developers who need to support the next release.
Search Driven Applications with Office 365 / SharePoint Online Using the tagging feature in SharePoint 2010Blog Posts
Common stuff about Search Driven Applications and a solution proposal with Office 365 / SharePoint Online.
You can build Search Driven Applications in several different ways and based on different techniques. One of the easiest is using the Query Object Model from the SharePoint Search to create “Fixed Keyword Queries”. For example this query shows all SharePoint sites which you have access to:
Puzzlepart was founded on the bet of the concept of Apps arriving in the enterprise space, and that it will be a complete game changer. When we started our quest in 2008 the concept of apps was just arriving in the consumer space. Today we have app-store ready native SharePoint Apps that delivers immediate business value impact.