Le Post de MCNEXT

Les articles des consultants de MCNEXT

Microsoft Ignite 2015 – SharePoint 2013 & Azure Iaas : Better together – Mardi 5 mai

SharePoint 2013 & Azure Iaas : Better together
Code : BRK3124

Par Adrien,
Pôle SharePoint MCNEXT

• Niveau : 300
• Cible : IT Influencers and Implementers
• Présentateur : Brian Alderman


Get an overview of the options that Microsoft Azure provides for SharePoint. This session explains and demos how you can utilize Azure to host SharePoint farms for hot and warm standby, segregated farms for your developers, farms for integration testing or productive farms. We explain how you can create your own template for SharePoint servers that enables you to add a server to your farm in Azure or on-premises in 15 minutes. We also help you to develop a backup strategy for SharePoint that uses Azure as the storage for long-term backups.

Lire la suite

Microsoft Ignite 2015 – Microsoft Office 365 Video End-to-End Portal Setup for Admins – Mardi 5 mai

Microsoft Office 365 Video End-to-End Portal Setup for Admins
Code : ILL3101

Par Adrien,
Pôle SharePoint MCNEXT

• Niveau : 300
• Audience : IT Influencers and Implementers
• FORMAT : Lab
Join Mikael as he takes you step-by-step from not having a video portal within your Office 365 environment to establishing your ready-to-go Office 365 Video destination with channels and permissions intact. This instructor-led lab walks you through how to enable the portal so it shows up in the main Office 365 app launcher, shows you how to create new channels and properly assign both ownership to each channel and apply desired permissions, and finally how to upload and curate video content for the broadest outreach within your company. This is a very hands-on approach to learning and controlling Office 365 Video.

Lire la suite

Microsoft Ignite 2015 – Pré migration best practice – Mardi 5 mai

Pré migration best practice 
Code : BRK3153

Par Adrien,
Pôle SharePoint MCNEXT

Make new annoncement about migration API

Lire la suite

Microsoft Ignite 2015 – Office 365 Groups – Overview & Roadmap – Mardi 5 mai

Office 365 Groups – Overview & Roadmap
Code : BRK2114

Par Adrien,
Pôle SharePoint MCNEXT

Niveau : 200
Cible : IT Decision Makers
Présentateurs : Amit Gupta, Christophe Fiessinger

Office 365 Groups helps you collaborate by easily bringing together your colleagues and the applications you need to get work done. Office 365 Groups leverages a standard definition for team membership and permissions across Microsoft Exchange, SharePoint, and later Skype for Business, Yammer and the rest of Office 365, managed through Microsoft Azure Active Directory. This session provides an overview of Office 365 Groups, demonstrates its capabilities today, and provides a roadmap for future investments.

Objectif :
How to work together in Office 365

Lire la suite

Microsoft Ignite 2015 – Evolution of SharePoint – Overview and Roadmap – Lundi 4 mai

Evolution of SharePoint – Overview and Roadmap
Code : FND2203

Par Adrien,
Pôle SharePoint MCNEXT

Lire la suite

Microsoft Ignite 2015 – Integrating Custom File Types in Office 365 with File Handler Add-Ins – Jeudi 7 mai

Integrating Custom File Types in Office 365 with File Handler Add-Ins
Code : BRK4114

Par Stéphane,
Pôle SharePoint MCNEXT

Niveau : 400
Présentateur : Dorrenne Brown

Comment apprendre à Office 365 à gérer des types de fichiers non connus : icône, prévisualisation en recherche…

Lire la suite

Microsoft Ignite 2015 – The Social Intranet : Integrate Yammer into Your Microsoft SharePoint Experience – Jeudi 7 mai

The Social Intranet : Integrate Yammer into Your Microsoft SharePoint Experience
Code : BRK3201

Par Stéphane,
Pôle SharePoint MCNEXT

Niveau : 300
Présentateurs : Eric Overfield et Naomi Moneypenny

Présentation des possibilités d’intégration de Yammer aux intranets pour les rendre plus sociaux.

Lire la suite

Microsoft Ignite 2015 – Dealing With Application Lifecycle Management in Office 365 App Development – Jeudi 7 mai

Par Stéphane,
Pôle SharePoint MCNEXT

Dealing With Application Lifecycle Management in Office 365 App Development
Code : BRK4126

Niveau : 400
Cible : Développeurs
Présentateur : Chris O’Brien

Travail sur le processus de développements d’apps SharePoint ou Office 365. Approche pragmatique et beaucoup de bonnes idées, à voir à tout prix !

Lire la suite

Your first Windows web application

Since Windows 8, you could make native Windows applications using HTML and JavaScript. With Windows 8.1, this kind of application also include Windows Phone.

With Windows 10, this kind of application is now officialy called « Windows web applications » or « Windows web apps » and is part of the Universal app platform. It means you will be able to make Windows web apps for all Windows devices : phone, PC, tablet, Xbox, Hololens, etc.

But it’s not just about the name. Windows 8 was really strict about security in those apps, and has restrictions on referencing scripts outside of the applications sandbox, or using things like innerHTML to prevent script injection.Those restrictions prevent using some libraries, tools and workflow from a web developper perspective.

With the Windows web apps in Windows 10, the goal is to put you a lot more in control, and even allow some brand new kind of scenarios. Windows web apps use a security model based on the W3C standard « Content Security Policy », or CSP, to define the security for your application. It means you are in control of where your scripts or iframe code can resides. It also means that using most libraries, like AngularJS, should come without friction.

Another great improvement is that Windows web apps use the rendering and JavaScript engines of Microsoft Edge, and not Internet Explorer. It means that you could use all new HTML, CSS, and Javascript goodness coming from Edge like ECMAScript 6 features, @support, interaction media queries, … When new feature will come to Edge, you will also be able to use them in your applications (as the time of this writing ASM.js, css filter and more are in but with an experimental flag).

But that’s not all. The sandbox have been expanded to allow an application to run pages, iframes or webviews from outside your application. You could now make applications running partially, or entirely from web content.

Windows web hosted applications

This new capability is called hosted applications, because your app can be entirely or partially hosted in the web. Lets see together how you could make such applications. To run this, you will need Visual Studio 2015 and Windows 10.

First create a new Windows web application by clicking file / new / project. In the templates, expand JavaScript / Windows / Windows Universal and pick the « Blank App (Windows Universal) » template.

new project

To use hosted content, we must allow the http domains we want to access within our app. We must declare those domains in the manifest of our application.

In Visual Studio, open your « package.appxmanifest » file. Within your manifest, you should have something like this.

<Applications>
    <Application Id="App" StartPage="default.html">
        <uap:VisualElements
            DisplayName="App1"
            Description="App1"
            BackgroundColor="#464646"
            Square150x150Logo="images\Logo.png"
            Square44x44Logo="images\SmallLogo.png">
            <uap:SplashScreen Image="images\splashscreen.png" />
        </uap:VisualElements>
    </Application>
</Applications>

Inside the application, just after the « uap:VisualElements » node, add a node called « uap:ApplicationContentUriRules ». If you start typing, you will see that Visual Studio provide intellisense. In that node, add a « uap:Rule ». To that rule, the « Match » attribute indicate the http domain, and the « Type » attribute indicate if you want to include or exclude the http domain.

You should have something like this

<Application Id="App" StartPage="default.html">
    <uap:VisualElements>
    ...
    </uap:VisualElements>
    
    <uap:ApplicationContentUriRules>
        <uap:Rule Match="http://www.mcnext.com" Type="include" />
    </uap:ApplicationContentUriRules>
</Application>

Lets make a full hosted app. For that, we will change our starting page to point to our http domain. Change the « StartPage » attribute on the Application node to reflect that change.

<Application Id="App" StartPage="http://www.mcnext.com">
    <uap:VisualElements>
    ...
    </uap:VisualElements>
    
    <uap:ApplicationContentUriRules>
        <uap:Rule Match="http://www.mcnext.com" Type="include" />
    </uap:ApplicationContentUriRules>
</Application>

Now just run your application by hitting F5. A brand new application will run with your web content.

As configured here our web site can not use Windows Runtime API (WinRT). To enable this kind of scenarios, you must explicitely enable this http domain to access WinRT. Update the « uap:Rule » you set with the WindowsRuntimeAccess attribute to « all ».

<Application Id="App" StartPage="http://www.mcnext.com">
    <uap:VisualElements>
    ...
    </uap:VisualElements>
    
    <uap:ApplicationContentUriRules>
        <uap:Rule Match="http://www.mcnext.com" Type="include" WindowsRuntimeAccess="all"/>
    </uap:ApplicationContentUriRules>
</Application>

Congratulations, your website can now access WinRT features like Cortana, native share, and all other APIs available in WinRT (just look at MSDN documentation to see them all). Your application can also be deployed in the Windows Store, and add visibility to your site and services.

Obviously, just wrapping a website like we did is not the most valuable story. You will probably want to add a few files to bootstrap your application and show a decent (and branded) error page in case the user access your application without network. You may also mix packaged and hosted content by opening an iframe on that same uri, or whatever scenario respond to your needs.

This new hosted applications and new security model is really interesting because it unlocks many scenarios, for both public store applications, and line of business applications. We will try to expand on such scenarios in future posts.

Microsoft Ignite 2015 – Du lundi 4 mai au Mercredi 6 mai par Stéphane

Par Stéphane,
Pôle SharePoint MCNEXT

LUNDI 4 MAI 2015
1 – DevOps as a strategy for business agility
2 – Deep Div into Safe Sharepoint Branding in Office 365 Using Repeatable Patterns and Practices
3 – Building solutions with Office 365

MARDI 5 MAI 2015
4 – Get Your Hands Dirty with the Office 365 APIs, Authentication, and SDKs
5 – Designing and Applying Information Architecture for Microsoft SharePoint and Office 365
6 – Building business apps like they do in the valley with Angular, Node.js, and more..

MERCREDI 6 MAI 2015
7 – Understanding the IT Pro’s dynamic operations role within DevOps
8 – What’s new for build automation in Team Foundation Server and Visual Studio Online
9 – Bose Turns Up the Volume with Microsoft Office 365
10 – Visual Studio 2015 for Web Developers
11 – Implementing Next Generation SharePoint Hybrid Search with the Cloud Search Service Application

Lire la suite

Suivre

Recevez les nouvelles publications par mail.

Rejoignez 37 autres abonnés