archive-nl.com » NL » M » MAVENTION.NL

Total: 609

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Remote authentication in SharePoint Online for Windows Phone apps - Blog - Mavention
    I added a call to GetClaimsParams to my page initialization wired a navigation event to my webview to process the results and started the flow by directing the WebView to the portal login url How it works GetClaimsParams retrieves the login page url of the portal and the url of the page to which the browser will be redirected after authentication by making a HttpWebRequest to the portal url provided and parsing the request headers The WebView is then directed to this login page where the user can provide credentials directly to SharePoint Credentials are never passed to or stored in the Windows Phone app Finally the event handler firing after the WebView is navigates to a new page checks if the current page is the page displayed after login extracts the authentication cookies from it and navigates the app to MainPage of the app The extracted cookies can now simply be added to the REST calls fired at SharePoint as per usual Adds this to your page initializaton to set up cookie collection from WebView The actual collection and handling is handled in AuthenticationWebView NavigationCompleted await GetClaimParams StartUrl AuthenticationWebView Navigate new Uri LoginUrl AuthenticationWebView NavigationCompleted AuthenticationWebView NavigationCompleted private async Task GetClaimParams string targetUrl HttpWebRequest webRequest HttpWebRequest WebRequest Create targetUrl webRequest Method OPTIONS try WebResponse response await webRequest GetResponseAsync ExtraHeadersFromResponse response catch WebException webEx ExtraHeadersFromResponse webEx Response private bool ExtraHeadersFromResponse WebResponse response LoginUrl null EndUrl null try EndUrl new Uri response Headers X Forms Based Auth Return Url LoginUrl response Headers X FORMS BASED AUTH REQUIRED return true catch return false private CookieContainer ExtractAuthCookiesFromUrl string url Uri uriBase new Uri url Uri uri new Uri uriBase call WinInet dll to get cookie string stringCookie CookieReader GetCookie uri ToString if string IsNullOrEmpty stringCookie return null stringCookie stringCookie Replace Replace use CookieContainer

    Original URL path: http://www.mavention.nl/blog/remote-authentication-sharepoint-online-windows-phone-apps (2016-02-18)
    Open archived version from archive


  • Update for Mavention Last Modified Documents available - Blog - Mavention
    sure links break out of the iframe and open the page or document in the parent window This mechanism does not work for certain versions of the iPad causing the link to open inside the iframe We resolved this issue by adding the target parent attribute to the links in the app part in order to force links out of the iframe Since we were publishing a new version of the app we decided to add an optimalisation right away The app makes calls to SharePoint using the REST API The calls are made using accept header application json odata verbose While this is not wrong it includes a lot of meta data to the result which we don t need By changing the accept header to application json odata nometadata a lot of the data we don t need is left out by the server thus saving some bandwidth You can find the Mavention Latest Documents in the Office Store or checkout all Apps by Mavention If you already have a version of the Mavention Latest Documents installed all you need to do is update the app You can find a short description on updating an app on MSDN

    Original URL path: http://www.mavention.nl/blog/update-mavention-last-modified-documents-version-1020 (2016-02-18)
    Open archived version from archive

  • Building the Isala folders Windows Store app - Blog - Mavention
    of the search index Naturally we d like this metadata to be registered when people use the app as well Luckily the REST API supports by calling api events logevent as described in the blog post about building companion apps Invalid content Most of the html page content on the Isala site is pretty clean so we didn t have to worry much about stripping elements or patching inline styles copy pasted from Word However there was specific element which caused us problems embedded YouTube clips The html code YouTube provides to embedding clips into a page is simply an iframe Since iframes are not allowed in html content of Windows Store app pages these are automatically stripped from the content The solution was to parse the url of the clip from the html content and manually inject a webview element where the iframe should be and generating some script to navigate the webview to the clip The support for YouTube clips is also the main reason for targeting the app to the Windows 8 1 api since the webview was introduced in this version Offline content One of the key features of the app is the option to store folders offline This allows users to view selected folders at any time even when a connection the internet is not available This created two challenges First we needed to implemented a mechanism to make sure local folders are updated whenever the online version is Second the content consists of more than just html code On a website you can just add link to an image but in an offline scenario all the relevant related resources will need to stored locally as well In practice this meant downloading all the images and rewriting the html to use local paths YouTube clips

    Original URL path: http://www.mavention.nl/blog/building-isala-folders-windows-store-app (2016-02-18)
    Open archived version from archive

  • Confusing content type name updates using PowerShell, Part 2 - Blog - Mavention
    you need select an alternative language in the language settings And that s it With multilingual enabled you can use the NameResource attribute to rename content types in your site Keep in mind that changing the name of a content type does not rename inheriting list content types and that we re only changing the labels here and not the actual name of the content type so when retrieving the content type in code we ll need to use the original name or even better use its id Finally the alternative languages setting is not inherited in subsites so you need to manually set this on each subweb or use a script for this as well Wrapping it up here s the script I used to rename the my content type and update the inheriting list content types function RenameContentType web id newName ctId New Object Microsoft SharePoint SPContentTypeId id ct web ContentTypes ctId if ct ne null Write Host Got ct from web ct Name ForegroundColor Magenta ct NameResource SetValueForUICulture nl NL newName ct NameResource SetValueForUICulture en US newName ct Update Write Host Renamed ct in web web Url ForeGroundColor Magenta else Write Host ct not found in web

    Original URL path: http://www.mavention.nl/blog/confusing-content-type-name-updates-using-powershell-part-2 (2016-02-18)
    Open archived version from archive

  • Duet Enterprise features available on SharePoint Online - Blog - Mavention
    When I tried to activate the site collection features I got an error saying Reporting needs to be configured to activate this feature Please contact your Tenant admin Farm admin to configure it The most I could find on this is a preliminary article on TechNet titled Deploying Duet Enterprise Online for Microsoft SharePoint and SAP However the availability of this set of features could be a great step forward

    Original URL path: http://www.mavention.nl/blog/duet-enterprise-features-sharepoint-online (2016-02-18)
    Open archived version from archive

  • Confusing content type name updates using powershell - Blog - Mavention
    oldName if ct ne null ct Name newName ct Update true This works fine for sites created in the English language Unfortunately our customer s portal was created as a Dutch site collection Since updating a web title in such a scenario requires an additional step we figured this might be the case here as well and added ct NameResource SetValueForUICulture nl NL newName This turned to not be the solution The most interesting past is the update seemingly works fine Even fetching the content type in a new PowerShell window shows the update A clue to there being something wrong is in you having to retrieve the content type using the old name The value in the array operator does not match the value either in the Name or the NameResource propery When you check the UI you ll see the name was not actually updated Scanning the properties we noticed the SchemaXml was still listing the old value in the Name attribute SchemaXml is read only and can t be updated but SchemaXmlWithResourceTokens holds the same data and can be edited Changing the script to update this value solved our problem web Get SPWeb http intranet oldName SomeContentType ct web ContentTypes oldName if ct ne null ct SchemaXmlWithResourceTokens ct SchemaXmlWithResourceTokens Replace oldName newName ct Update true The name of a content type is not pushed to inheriting list content types not even when you pass the parameter to SPContentType Update bool So we altered the script to loop all the webs and lists to fix the content type The solution of updating SchemaXmlWithResourceTokens does not work on list content types however since the SchemaXmlWithResourceTokens is not actually used for list content types Updating the Name and NameResource properties still does not do anything so we are currently not

    Original URL path: http://www.mavention.nl/blog/updating-content-type-names-using-powershell (2016-02-18)
    Open archived version from archive

  • Blog - Mavention
    to use interface to access the information you require and is available in the store now Aangemaakt op 30 9 2014 door Frans van Rijn Update for Mavention Last Modified Documents available Version 1 0 2 0 of the Mavention Last Modified Document app for SharePoint is now available Aangemaakt op 8 9 2014 door Frans van Rijn Remote authentication in SharePoint Online for Windows Phone apps Remote authentication for SharePoint Online in native Windows apps is nothing new but support for the Windows Phone platform is lacking This blog explains how remote authentication can be achieved in a native Windows Phone app Aangemaakt op 21 8 2014 door Frans van Rijn Building the Isala folders Windows Store app Together with Isala Mavention developed a Windows Store app centered on these brochures to easily disclose the information available here to a broader audience This blog discusses a few of the technical challenges we encountered during this development Aangemaakt op 27 5 2014 door Frans van Rijn Building SharePoint apps with SignalR Inspired by a recent blog by Vesa Juvonen about connected SharePoint app parts with SignalR we decided to have a look at SignalR and how we can use to

    Original URL path: http://www.mavention.nl/blog?k=PublishingContactNameOWSTEXT%3a%22Frans+van+Rijn%22&start=5 (2016-02-18)
    Open archived version from archive

  • Demystifying Document ID's - Blog - Mavention
    prefix and thus generate one for us however this method will do some more for us Before actually activating it will determine the size of our site and based on that it will activate the Document ID Assignment or it will create a work item to do so if DocIdHelpers IsSiteTooBig site DocIdEnableWorkitem ScheduleWorkitem site prefix fEnable fScheduleAssignment fOverwriteExistingIds fDocsetCtUpdateOnly else DocIdEnableWorkItemJobDefinition EnableAssignment site prefix fEnable fScheduleAssignment fOverwriteExistingIds fDocsetCtUpdateOnly The site is defined as to big when one of the following requirements is met The site has a subweb if it has more then 1 web including the rootweb The site has more then 40 lists The site has more then 20 document libraries That means that if we enable the feature or assign an new prefix through code it will always check the sizing of the site before enabling Document ID s If a work item gets created both timerjobs should run before you will see the prefix as you expected However there is another pitfall the scheduling of the work item is done by the following code site AddWorkItem Guid Empty DateTime Now AddMinutes 30 0 ToUniversalTime DocIdEnableWorkItemJobDefinition DocIdEnableWIType site RootWeb ID site ID 1 false Guid Empty Guid Empty site RootWeb CurrentUser ID null strTextPayload Guid Empty The thing to notice there is that it will create a new work item as expected but it does so with a scheduled date that is 30 minutes from the moment you activate the feature That means that you can run the timerjobs as much as you like but it will take 30 minutes before your site will be processed Timerjobs There are two timerjobs that will need to be executed in the right order to have the prefix working on your farm The first on is the Document ID enable disable job this will process the work items on all sites and make sure that the prefix is pushed to all subwebs on the site collection And then there is the Document ID assignment job this job will push the required settings to all lists on the webs and make sure that documents that are created after the feature was turned on are updated with the correct ID and prefix If you would run the Document ID assignment job before running the enable disable job it will not process your web properly and you will not see the expected Document ID s Eventreceivers When running the Document ID assignment job one of the steps that will done in the web and its lists will be to update all the Content Types with the event receivers that are needed to update documents with an Document ID When those event receivers are not present you will see entries in the ULS that it will try to process the item but nothing else happens and the item itself will be not be stamped with a Document ID So if you are running into issues where your documents are not provided with a

    Original URL path: http://www.mavention.nl/blog/demystifying-document-id (2016-02-18)
    Open archived version from archive



  •