This post is article 29 from the 30 Articles App series for SharePoint
Future of Auto-hosted apps :
A few blogs from SPC14 say about AutoHosted Apps are being deprecated, This could be a rumor as Microsoft has not yet confirmed anything officially on this. If they are not being deprecated in near future, for how long they will be supported or when they may go from preview to fully supported is still not clear. As they are still in Preview, they should be avoided for Production design and recommended for only prototyping .
Some new Infographics for Apps:
These infographics can be downloaded from here . They give good and quick understanding on Why to build SharePoint apps?, App Concepts, App – hosting options, Data storage/access options etc.
New Office Web Widgets:
These experimental UI widgets were announced at SPC14 and are intended to help building apps for Office and SharePoint. The first release includes People Picker and the List View widgets. As per the Office dev team, these widgets are “experimental” and its primary goal is to collect feedback. They plan to release these controls for production use soon. Download it from NuGet Manager (search for Office Widgets) . Try it and send your feedback on UserVoice using the Office Web Widgets category.
New Office 365 SDK for Android Preview:
Finally Microsoft is thinking openly ;). this sdk is built by MS Open Tech and provides access to:
• Microsoft SharePoint Lists
• Microsoft SharePoint Files
• Microsoft Exchange Calendar
• Microsoft Exchange Contacts
• Microsoft Exchange Mail
The SDK is composed of three independent packages, so that you can import only the SDK that you need in your project.
- office365-files-sdk [depends on office365-base-sdk]
- office365-lists-sdk [depends on office365-base-sdk]
For more info on this refer to http://msopentech.com/blog/2014/03/03/new-open-source-sdk-for-android-brings-office-365-apps-to-life/
External links to SPC14 Summary articles from SharePoint Community folks:
Link to official Press Release at PRweb
ProSigma took home two prizes at app awards SharePoint Conference 2014 at Las Vegas with our app ProConnect winning 1st place in Most Business Value SharePoint category and awarded 2nd place in Most Interesting SharePoint Scenario category. The awards honour innovative and high-quality productivity apps dedicated to enhancing Microsoft Office 365 or SharePoint.
“We are thrilled to receive these awards and delighted to be recognized as a leader in this space. We are boosting innovation and adoption of cloud-based solutions. We are committed to bring out increasing business value and the best experience through ProConnect . ” said Analben Mehta, Founder and CEO at ProSigma.
ProConnect won first place for “Most Business Value”
The Most Business Value SharePoint category was selected by a panel of Microsoft judges, who based their decision on two criteria: 75 percent on Productivity and 25 percent on Relevance to Platform.
Proconnect also won 2nd place for “Most Interesting Scenario”
The Most Interesting SharePoint Scenario category was selected by a panel of Microsoft judges, who based their decision on two criteria: 75 percent on the app’s relevance to the platform and 25 percent on app performance.
ProConnect is a secured location based business networking application that helps you keep in touch with your colleagues anywhere! It is an interactive Microsoft SharePoint 2013 app that allows users to create and share location based contents within organizations. It also offers creating and maintaining places of user’s choice. This app also brings near-by location information and updates.
ProConnect also comes with supporting free smartphone mobile application for users to stay connected while on the move.
See the links below for more details:
Office store link for ProConnect
Windows phone store link for Mobile Client
Please visit http://prosigmaltd.com/ProConnect to know more about ProConnect.
Follow @Proconn3ct to get latest updates about ProConnect
This post is article 28 from the 30 Articles App series for SharePoint
Web components can also be deployed programmatically using a remote event receiver InstalledEventEndpoint or an UpgradedEventEndpoint. If you are adding components in other than the app web you should also implement an UninstallingEventEndpoint that uninstalls those same components.
Handling the app updated event :
Your sharepoint app should have valid UpgradedEventEndpoint refering to your remote service.
In web project , open AppEventReceiver.svc.cs file and add a conditional structure to the ProcessEvent to handle appUpdated event like following.
if (properties.EventType == SPRemoteEventType.AppUpgraded)
using (ClientContext cc = TokenHelper.CreateAppEventClientContext(properties, true))
// CSOM code that accesses the app web
using (ClientContext cc = TokenHelper.CreateAppEventClientContext(properties, false))
// CSOM code that accesses the host web
// Other update code as per your need
Provide conditional structure to handle the app updated event on subsequent updates
Version ver2OOO = new Version("22.214.171.124");
if (properties.AppEventProperties.PreviousVersion < ver2OOO)
// Code to update from 126.96.36.199 to 188.8.131.52 is here.
Version ver3OOO = new Version("184.108.40.206");
if (properties.AppEventProperties.PreviousVersion < ver3OOO)
// Code to update from 220.127.116.11 to 18.104.22.168 (previous update code) is here.
// Code to update from 22.214.171.124 to 126.96.36.199 is here.
catch (Exception e)
// Make sure you catch all exceptions while updating and rollback to undo if that is necessary.
result.ErrorMessage = "error message : " + e.Message;
result.Status = SPRemoteEventServiceStatus.CancelWithError;
In some cases, you might need to migrate data or upgrade schema. If your old data is somewhere that can be accessed by a remote event handler, you can implement migration logic in an InstalledEventEndpoint web service of the new app. Alternatively, if the new app has access to the old data, you can put the migration logic in code that runs the first time that a user starts the new app. If the old data cannot be accessed by either the remote handlers or the new app, you can create an update of the old app that adds a data export capability and a UI for the capability. Users would first update the old app, and then use it to export the data to a location where the new app can access it. You include the capability and UI to import data in the new app.