You don't have to use query expressions to use LINQ

submitted by johnsheehan 6 hours, 7 minutes ago

msmvps.com — LINQ is clearly gaining a fair amount of traction, given the number of posts I see about it on Stack Overflow. However, I've noticed an interesting piece of coding style: a lot of developers are using query expressions for every bit of LINQ they write, however trivial. read more...

add a comment | category: Linq | Views: 12

ContentGator - runtime content aggregation

submitted by DanielSchaffer 1 day, 10 hours ago

codeplex.com — ContentGator allows web developers to automatically serve aggregated content (css, js, etc) from their web pages. By simply listing relative paths, files are grouped by content type and aggregated into a single file, which is automatically served with GZip or Deflate compression. read more...

add a comment | category: Open Source | Views: 7

Activator.CreateInstance Performance

published 1 day, 4 hours ago, submitted by justin_etheredge 1 day, 10 hours ago

codethinked.com — A look at the different forms of Activator.CreateInstance and the performance implications of each. read more...

add a comment | category: C# | Views: 226

Verifying code and testing with Pex

blog.maartenballiauw.be — Earlier this week, Katrien posted an update on the list of Belgian TechDays 2009 speakers. This post featured a summary on all sessions, of which one was titled “Pex – Automated White Box Testing for .NET”. Here’s the abstract: “Pex is an automated white box testing tool for .NET. Pex systematically tries to cover every reachable branch in a program by monitoring execution traces, and using a constraint solver to produce new test cases with different behavior. Pex can be applied to any existing .NET assembly without any pre-existing test suite. Pex will try to find counterexamples for all assertion statements in the code. Pex can be guided by hand-written parameterized unit tests, which are API usage scenarios with assertions. The result of the analysis is a test suite which can be persisted as unit tests in source code. The generated unit tests integrate with Visual Studio Team Test as well as other test frameworks. By construction, Pex produces small unit test suites with high code and assertion coverage, and reported failures always come with a test case that reproduces the issue. At Microsoft, this technique has proven highly effective in testing even an extremely well-tested component.” After reading the second sentence in this abstract, I was thinking: “SWEET! Let’s try!”. So here goes… read more...

add a comment | category: Unit Testing | Views: 175

Filtering List Items - The Yield Return Solution

dev102.com — Here we are talking about filtering list items again :). read more...

add a comment | category: C# | Views: 285

Hidden Features of C#

published 5 days, 14 hours ago, submitted by ethilik 6 days, 3 hours ago

blog.sb2.fr — In this article, I’ll just link to a pretty great StackOverFlow Question about Hidden Features of C#. Most of C# Features are obscure for us and need some explanations, the following list and explain how to use it. read more...

add a comment | category: C# | Views: 1040

http://codeclimber.net.nz/archive/2008/12/30/looking-at-oxite-the-ldqu

published 8 days, 12 hours ago, submitted by keyvan 8 days, 14 hours ago

codeclimber.net.nz — Simone Chiaretta shares his opinions about Oxite, the CMS built by MIX team as a showcase for ASP.NET MVC, and talks how the downsides of the software can help you apply your knowldege in ASP.NET WebForms in ASP.NET MVC. read more...

2 comments | category: MVC | Views: 185

What is Microsoft waiting for providing a decent path API?

published 9 days, 7 hours ago, submitted by johnsheehan 9 days, 9 hours ago

codebetter.com — I was recently browsing the code source of Managed Extensibility Framework and realized that this future part of .NET 4, full of tricky and advanced ideas, was naively relying on strings to describe files and directories paths. It seems that the version 4 of .NET will miss the need for a descent path API. There is the class System.IO.Path but it is feature limited, full of flaws and pitfalls (to not say bugs) and it fosters users to encode their paths into raw strings. It seems to me that using strings to encode paths is as primitive as using String.IndexOf("<tag>") to parse some XML. read more...

1 comment | category: CLR | Views: 245