- Visual Studio 2013
- MS-LPL
- jQuery Mobile
- windows azure active directory
- Windows Phone 8
- CORS
- .NET Framework 4.5.1
- OWIN self-hosting
- Entity Framework 6
- Windows 8.1 HTML/WinJS
- ASP.NET Web API 2
- Devices and Services development
- 11/19/2013
At the Visual Studio 2013 Launch Event (Nov. 13th 2013), Microsoft used a set of demo applications to explain the new features in .NET 4.5.1 and Visual Studio 2013. Here we are publishing those demo applications.
MyCompany is a set of sample applications comprised of typical enterprise/business modules: Travel, Staff, Vacation, Visitors and Expenses.Each of these business applications are autonomous and
could have been developed by different teams. They use different technologies and solutions to fulfill the different requirements from different user profiles and desired scenarios. All web and services solutions can be deployed to Windows Azure, and
all of them are using Windows Azure Active Directory to support Single-Sign-On between all the applications in the suite.The companies can also federate the directory service with their on-premises directories (corporate Active Directory) to support SSO using
the on-premises corporate AD credentials.A few of the web apps can also be integrated as apps for SharePoint within Office 365.
In summary, different technologies are used depending on the business application scenarios: Web Apps, Windows Store, Windows Phone, WPF desktop, etc.
This concrete business application is called EXPENSES and it is described below.
Requirements
Description
EXPENSES Windows Phone native app (C#/XAML)
EXPENSES Web Mobile app (ASP.NET MVC)
Services technologies
ASP.NET Web API 2 |
Attribute Routes |
CORS |
OWIN-Katana |
OWIN self-hosting |
Entity Framework 6 |
Windows Azure Service Bus |
Web Application technologies
JQuery Mobile |
Security technologies
Windows Azure Active Directory |
Windows Apps technologies
Windows 8.1 Store HTML/JS |
Windows 8.1 Push notifications |
Windows Phone C#/XAML |
Windows Phone Push notifications |
These applications are not production systems and are not intended as a guidance for mission-critical applications, as it mostly covers CRUD and Data-Driven scenarios, only. If you need guidance for complex scenarios, we recommend to check guidance material from the Microsoft Patterns & Practices group like the ‘CQRS Journey guidance’, which shows a reference application with a related functional domain & scope (Events/Conferences platform) but from a different point of view based on design-patterns and best architectural practices for complex scenarios, covering approaches like CQRS (Command & Query Responsibility Segregation) & DDD (Domain Driven Design).