Developing software solutions that work across several devices and platforms is becoming increasingly important. With that in mind, Visual Studio 2015 attempts to streamline sharing code across platforms in a number of ways. This video provides an overview Visual Studio 2015's new shared project type and how you can use it to share code across platforms. The video also briefly covers portable code libraries (PCLs) and shares best practices for choosing a code sharing strategy.
To find out more information about cross device development with Visual Studio, check out this whitepaper on building mobile apps with Microsoft tools and resources, leveraging the Azure platform.
Testability is more important than ever. With short ship cycles and the desire for continuous delivery, it is critical to quickly know if a modification has destabilized your code base. This session will enable you to use a dependency injection container of your choice to create testable code. We will examine tightly coupled code and what problems it causes and how DI can be used to avoid these problems. The Unity DI container will be used as the medium to understand the concepts.
UCB is a patient-centric biopharma leader, focusing on severe diseases in Immunology and the Central Nervous System. The company employs in the region of 9000 employees and operates in approximately 40 countries. UCB achieved revenues of $3.46 billion in 2012.
The main driver to implement Lync in the early part of 2011 was first started by the need for a video conferencing solution. This was further accelerated by the "Smarter Ways" efficiency program – which included effective collaboration within the scope. The Lync conferencing services alone helped UCB realize savings of $1.2M compared to the legacy conferencing solutions that were previously in place. The choice of Lync has also allowed full integration of the Unified Contact Centre systems at UCB.
During this session, UCB will cover their drivers for unified communication, the Lync journey (strategy with scope expansion and timeline), communication & change management activities and finally some KPI's.