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


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)

EF6.1.2 Beta 2 Available

AddThis Social Bookmark Button
Today we are making Beta 2 of the EF6.1.2 release available. This patch release contains bug fixes and some contributions from our community.   When will EF6.1.2 RTM? We were originally planning to go straight to RTM from Beta 1. However, we ended up taking a number of important bug fixes after Beta 1 shipped and we decided that the churn in the code base warranted another pre-release before we RTM. The pre-releases are important because they allow our customers and provider/extension writers to report any issues before we ship the RTM release. Our plan
is to ship RTM sometime next month. This may change if we have additional high priority bugs reported on Beta 2.   What’s in Beta 2? EF6.1.2 is mostly about bug fixes, you can see a list of the fixes included in EF6.1.2 on our CodePlex site. We also accepted a couple of noteworthy changes from members of the community: Query cache parameters can be configured from the app/web.configuration file   
...(Read whole news on source site)

Live playground for RavenDB 3.0

AddThis Social Bookmark Button
We are getting to the part where we are out of things to do, so we setup a live instance of RavenDB 3.0 and opened it up for the world to play with. It is available here: Disclaimer - It may go down at any moment, data will routinely be wiped but is public and can be copied and used for other users. This is strictly for playing around with it, nothing more. Give it a shot, see all the new cool stuff.