Visual studio feeds

All Visual Studio blogs in one place


Enter your email address:

Delivered by FeedBurner

Increase your website traffic with



Anti-spam: How many eyes has a typical person?

Follow us on FB


APress Deal of the Day 19/November/2014 - Beginning PowerShell for SharePoint 2013

AddThis Social Bookmark Button
Originally posted on:'s $10 Deal of the Day from APress at is Beginning PowerShell for SharePoint 2013. "Beginning PowerShell for SharePoint 2013 is a book for the SharePoint administrator looking to expand his or her toolkit and skills by learning PowerShell, Microsoft's vastly flexible and versatile object oriented scripting language"

How to integrate “Ad Mediator” in your apps?

AddThis Social Bookmark Button
Microsoft Ad Mediator”, recently released by Microsoft to maximize your ad monetization – we already talked about it last day. If you don’t know about it, read the said post, download the Visual Studio 2013 extension before continuing with this post. Today, we will discuss how to integrate “Ad Mediator” in your Windows Store and Windows Phone applications. As it currently supports only Windows Phone apps, so we will continue with that.  Once you install the “Ad Mediator” plugin extension for Visual Studio 2013, you
will see a new context menu item in your Windows Phone app project named “Connected Service”. This opens the Services Manager window where you can find the Ad Mediator section to add/configure your ad networks. To do this, right click on your Windows Phone application project, navigate to “Add” – “Connected Service…” as shown in the below screenshot:  At the first, it will search for all the ad network instances installed in your project and load them in this screen. By default, it loads the “Microsoft Advertising” network.  Once it loads the ad network instances, it shows the name of the ad network,...(Read whole news on source site)

Improving the Visual Studio Account Management Experience

AddThis Social Bookmark Button
Anyone who has built an application in Visual Studio that uses several services (e.g. roaming Visual Studio settings, accessing Azure services in Server Explorer, or using Windows Store) has probably experienced what we’ve come to call “sign-in Whack-A-Mole,” with prompts popping up when you least expect them to. In Visual Studio 2015 we introduced an account manager to reduce how often Visual Studio needs to prompt for credentials and to make it easier for you to switch among different user accounts within the IDE. You’ll see the account manager utilized in various places inside the Visual Studio 2015
user interface, but the central place of account management resides In File -> Account Settings. Let’s take a deeper look at how the account manager works. Many Services, Many User Accounts There were two general types of authentication workflows we saw in Visual Studio 2013 and earlier: Multiple Services. Online services such as Azure, Office 365, and Visual Studio Online managed their users’ authentication tokens separately. Additionally, re-entering your credentials only refreshed the token for that one feature, leaving other features unauthenticated. This meant...(Read whole news on source site)

Katana, ASP.NET 5, and bridging the gap - .NET Web Development and Tools Blog - Site Home - MSDN Blogs

AddThis Social Bookmark Button
Katana, ASP.NET 5, and bridging the gap - .NET Web Development and Tools Blog - Site Home - MSDN Blogs


renaming the packages and namespaces from Microsoft.Owin.* to
Microsoft.AspNet.* to conform to the rest of ASP.NET. Due to the rename
the package versions have been reset to v1.0.0.

ASP.NET 5 has built in support for the new OWIN pipeline builder model. See the extensions and samples. Middleware may use any OWIN helpers they wish internally, including the IOwinContext if that’s what they’re already

Formatters in ASP.NET MVC 6 - StrathWeb

AddThis Social Bookmark Button
Formatters in ASP.NET MVC 6 - StrathWeb

key concepts in HTTP API development is the notion of content
negotiation (conneg). ASP.NET Web API provided first class support for
content negotiation through the use of MediaTypeFormatters.

MVC 6 ships with a bunch of formatters defined already.

Three input formatters:

– JsonInputFormatter – based on JSON.NET – XmlSerializerInputFormatter – based on XmlSerializer (in the box, but not registered by default) – XmlDataContractSerializerInputFormatter – based on DataContractSerializerSix output formatters:

– JsonOutputFormatter – based on JSON.NET –
XmlSerializerOutputFormatter – based on XmlSerializer (in the box, but not registered by default) – XmlDataContractSerializerOutputFormatter – based on DataContractSerializer – TextPlainFormatter – used to force a string into a text/plain content type – HttpNoContentOutputFormatter – used to force 204 status code for null action return – HttpNotAcceptableOutputFormatter – used to force 406
status code if no appropriate formatter can be selected to handle the
request (in the box, but not registered by default)This is a slight change from Web API which itself defined four
formatters – JSON, XML and two formatter specialized in handling form

ASP.NET Web Forms Extensibility: Output Encoders

AddThis Social Bookmark Button
Since version 4, ASP.NET offers an extensible mechanism for encoding the output. This is the content that will be returned to the browser.A base class exists, HttpEncoder, for which it used to be the default implementation. It has the responsibility to encode all contents sent to the server, in a differentiated manner – JavaScript is encoded in a way, HTML in another, URLs in another, and so on. Since ASP.NET 4.5, the default implementation is AntiXssEncoder. Those familiar with Anti-Cross Site Scripting Library (now Web Protection Library) will recognize this class, which offers better
protection against cross site scripting attacks.This class offers a number of virtual methods that you can override to change the default behavior: HeaderNameValueEncode (for encoding headers sent in the response), HtmlAttributeEncode (for tag attributes), HtmlEncode (for generic text content), JavaScriptStringEncode (for JavaScript), UrlEncode (URLs) and UrlPathEncode (URL parts). Do create a dummy encoder and debug through these methods to see what they are called with.The actual implementation to use can be configured by code or XML configuration (the Web.config file).For using code configuration, one has to change the HttpEncoder.Current in...(Read whole news on source site)