Paulo Morgado
.NET Development & Architecture
-
C# vNext language design - private protected - FamilyAndAssembly
C# vNext will have a new accessibility modifier. The C# team had first proposed to use "private protected", but maybe someone can find a better syntax for it.
-
Building a Release Pipeline with Team Foundation Server + Hands On Lab
The Practices & Patterns team has released another guidance.
-
Prism For Windows Runtime Is Out
Prism for the Windows Runtime and the associated AdventureWorks Shopper reference implementation is now available on the Windows Dev Center.
-
Red Gate Is Looking For Feedback On Its ASP.NET MVC Web Development Education Website
Red Gate is looking for feedback on its ASP.NET Web Development Education website.
-
Developing an End-to-End Windows Store app using C++ and XAML: Hilo
Patterns & Practices has released Hilo guidance: Developing a Windows Store app using C++ and XAML which is part of the Windows SDK.
-
Using The GeoCoordinateReactiveService
Having created an Rx wrapper over the GeoCoordinateWatcher on a previous post, in this post I’ll demonstrate how it can be used in a simple application.
-
Would you like to have roaming settings in Visual Studio?
The C++ Team (blog) has been researching roaming Visual Studio settings and they have a few questions that will help gain insights into what the best experience would be. They have created a survey (http://aka.ms/vsroaming) aimed at understanding Visual Studio settings usage patterns and gathering feedback. The survey should take less than 10 minutes, maybe more if you want to provide a ton of details.
-
Implementing The GeoCoordinateWatcher As A Reactive Service
With Rx, events are first class citizens that can be passed around and composed as needed in a very simple way.
-
Developing Multi-tenant Applications for the Cloud, 3rd Edition
Microsoft Patterns & Practices has recently released Developing Multi-tenant Applications for the Cloud, 3rd Edition.
-
A Synchronization Context Based On The TPL Dataflow Library
The purpose of the synchronization model implemented by the SynchronizationContext class is to allow the asynchronous/synchronization operations of the common language runtime to behave properly with different synchronization models. This model also simplifies some of the requirements that managed applications have to follow in order to work correctly under different synchronization environments. Examples of such synchronization environments are user interface infrastructures like Windows Forms, Windows Presentation Foundation and ASP.NET.