Contents tagged with ASP.NET
-
Building Functions vs. Building Expressions: Performance Comparison
Yesterday I posted an entry describing a method for building functions as opposed to building expressions to get a more succinct syntax, and in general a more functional approach. There was a touch of reflection in there though, so I wasn’t too sure what the performance would be like.
-
C# Dynamic Function Factory
Building functions instead of expression trees.
-
Silverlight Adaptive Streaming: How it works
Recently an announcement was made by Akamai that it was partnering with Microsoft to provide an Adaptive Streaming solution for Silverlight and IIS 7.0. Since I work in the online video industry I found the announcement very interesting, especially considering Move Network's previous announcement that it had formed a "Strategic Releationship" with Microsoft to provide this exact functionality.
-
LINQ to Concurrency Problems
LINQ to SQL is fascinating - the more I work with it, the more I hate it, and then love it again all at the same time. Recently we had an issue while using it in a slightly older version of our N-Tier WCF application which uses LINQ to SQL as it's primary ORM solution (yes, I know).
-
Troubleshooting ASP.NET MVC Routing
One thing I absolutely love about the ASP.NET MVC framework is that there isn't too much "magic". Magic can be nice if you are able to adhere to a framework's "Golden Path", but as soon as some customization becomes necessary you find that the magic can get in the way (DataContractSerializer anyone?).
-
Thinking In Rest - Part 2
So last time I covered the concept of resources (if you haven't read it yet, you should check that out here first) and the idea that when browsing the web you aren't looking at "pages" but instead you are looking at resources that happen to be formatted as pages. As it turns out, an HTML page is a pretty convenient format for a resource when a human is accessing it. Unfortunately, HTML is pretty poor for machine consumption - so how do we provide resources to client programs?
-
Thinking in REST
I've been reading blogs around the .NET community lately and there seems to be some serious confusion about what exactly REST is. Is it a SOAP replacement? Is it a definition of how to prepare data for consumption by AJAX clients? And what does it have to do with all this new MVC stuff we've been hearing about? What is it exactly?