I was a little late to the session, so only a screenshot from the slides:
Approach: look at the key workloads in regards to SharePoint and bring them to the mobile apps on all platforms.
Things they learned: Sign-in issues (a lot), analysis of top requests and implementing them
Android: feature parity with iOS but with respect to the material design. PowerApps integration comes first to Android
Windows 10 mobile: feature parity with iOS but with windows design. You have to be an Insider to get the app here: https://aka.ms/spappwindows
Quickly author news with status updates or mention a document. News are available on mobile phones, too. Its planned to add mobile news authoring so you can craft news while on the go.
Intranet in your pocket, the changes that are coming are promising for that:
Notifications, News and list improvements will drive the adoption.
To be honest, I expected this session to discuss about SharePoint Apps – no, I mean Addins! – and not about the mobile apps. But on the plus side, it was really good session that showed me whats possible in the apps – I am more a browser guy, but I will give it a try!
Watch out, I am attending a developer session! Mainly because Scott Hanselman is the speaker and I totally love his style. Developers!
This session will give us a broad overview of all the new things for devs – so we start with the current options of Visual Studio:
12.7 Mio downloads of Visual Studio
2 Mio Visual Studio Code
4 Mio users of Visual Studio Team Services
Developers are important! Developers, Developers, Developers!
Cloud is connecting everything!
Demo 1: Modernization
Porting sounds boring, modernization is a cooler word for it.
Transition from .NET Framework 2, 3, 4 to .NET Core – Visual Studio support all of them.
First demo on a Mac, running the CLI to create projects, restore packages – awesome.
Demo 2: Visual Studio 2015 and future improvements
Run with multiple browser. Browser link now syncs scrolling and user inputs across browsers – that is cool.
Demo 3: Containers
Docker is confusing for most enterprises, but with the windows version it is much easier to run. Even integrated in Visual Studio into the “run with” dialog. The solution is then built and put into a docker image – even with debugging support.
Demo 4: Azure Integration
Staging slots – run copies of your website in parallel and switch them back and forth into production aka. hot swaps. Then he shows “testing in production” where you can load balance e.g. 25% of all the traffic will be directed to staging instead of production. You can even automate that with powershell, eg. send them to staging, check for errors and in that case send them back to production. What could go wrong?!
Because so many viewers accessed Scott’s public website, he did a live scale out with the push of a button. Awesome.
Demo 5: Portable Code and native apps
Scott shows another demo were 90% of his code is in a portable class library. The rest of the code is device specific and stored in separate projects for IOS, Androws, Windows Phone or UWP. Live debug run on an iPhone simulator running iOS 10.
Demo 6: Xamarin Test Cloud
Testing your app on multiple devices is effortless with Xamarin test cloud, you get memory consumption, error logs, videos of your tests – crazy stuff.
The explosion is a test run on a Galaxy Note 7
Demo 7: SharePoint Online
Scott show a document stored on SharePoint (!!!). Once the document is saved it will trigger an Azure Function app (server-less code) to notify clients that the document has changed. Automate the processes here is the main point.
Recently my colleagues and I created a lot of SharePoint provider-hosted addins – in our case that is just a MVC Website hosted on Azure that talks balk to SharePoint. And I have to say it is good fun because we could actually debug a production site/business application in case something unforeseeable happens (aka. bugs). And the integration in Visual Studio via the Cloud Explorer could not be simpler. Right click on the website, attach debugger and see the problem.
Attach debugger on your remote azure website – cant be easier!
That worked a long time perfectly for us – but something changed and Visual Studio 2015 dropped the connection once a breakpoint is hit (sometimes even earlier). Strangely debugging still worked with Visual Studio 2013.
Attaching with a Visual Studio 2015 Debugger either from Cloud Explorer, Server Explorer or directly via “attach to process” attaches the debugger briefly (if at all) and then results in two errors:
The web browser shows: 502 – Web server received an invalid response while acting as a gateway or proxy
502 – Web server received an invalid response while acting as a gateway or proxy
In Visual Studio 2015 an error box shows: The network connection to <>.azurewebsite.net:4020 has been lost. Debugging will be aborted.
Debugging will be aborted.
The fix is rather simple. In Visual Studio open Debug menu from the top and click on Options:
Then click on Debugging > General and find the option “Enable UI Debugging Tools for XAML” and uncheck it.
After that, Debugging worked like a charm again.
I did not find that one out myself – the awesome Microsoft Support (I am looking at you Akash Khandelwal!) spent hours troubleshooting my problem. He early noticed that there is a something with WPF in the logs but we initially ruled that one out. After a while his team suggested to disable this option – and it worked!
During the debugging session I learned a lot about Azure Website troubleshooting – great stuff!