<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.csharpfeeds.com/~d/styles/itemcontent.css"?><rss version="2.0">
			<channel>
				<title>CSharp Feeds</title>
				<link>http://csharpfeeds.com</link>
				<description>CSharpFeeds - All your C# feeds in one place.</description>
	
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.csharpfeeds.com/Csharpfeeds" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="csharpfeeds" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
				<title>Style follows semantics</title>
				<description>Which is better style?
bool abc;if (Foo())&amp;nbsp; abc = Bar();else&amp;nbsp; abc = false;
vs
bool abc = Foo() &amp;amp;&amp;amp; Bar();
?
To me, this comes down to the question “is Bar useful solely for obtaining its value, or also for its side effects?” The stylistic choices should typically be driven by a desire to clearly communicate the semantics of the program fragment.
The metasyntatic names are therefore making this harder to answer, not easier. Suppose the choice were in fact between:
bool loginSucc
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/1dNny_UtHoUeGIXO3o33FNQXReg/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/1dNny_UtHoUeGIXO3o33FNQXReg/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/1dNny_UtHoUeGIXO3o33FNQXReg/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/1dNny_UtHoUeGIXO3o33FNQXReg/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</description>
				<link>http://blogs.msdn.com/ericlippert/archive/2010/02/01/style-follows-semantics.aspx</link>
				<author>Eric Lippert</author>
				<pubDate>Mon, 01 Feb 2010 16:29:00 GMT</pubDate>
			</item>
	
			<item>
				<title>Acer 1420P Leaky Handle Driver Fix</title>
				<description>Download: SDTabletPCFix_1.0.0.0.zip  I wasn’t lucky enough to receive the Acer 1420P laptop given out at PDC this year since I was “staff”, however I wound up picking one up on eBay for a very reasonable price.&amp;#160; I received it last week, added an additional 2GB of RAM, used my Windows Home Server to save off the original hard drive image, and then repaved the machine, installing Windows 7 Ultimate x64, drivers, and applications from scratch.&amp;#160; Earlier this week I noticed the machine was
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/57G5BbOmQzrkYyAspcGaqW71CrU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/57G5BbOmQzrkYyAspcGaqW71CrU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/57G5BbOmQzrkYyAspcGaqW71CrU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/57G5BbOmQzrkYyAspcGaqW71CrU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</description>
				<link>http://feedproxy.google.com/~r/BrianPeek/~3/xGCkCnNYPqo/acer-1420p-leaky-handle-driver-fix.aspx</link>
				<author>Brian Peek</author>
				<pubDate>Sun, 31 Jan 2010 22:07:00 GMT</pubDate>
			</item>
	
			<item>
				<title>Calling constructors in arbitrary places</title>
				<description>C# lets you call another constructor from a given constructor, but only before the body of the calling constructor runs: 
public C(int x) : this(x, null){&amp;nbsp; // …}public C(int x, string y){&amp;nbsp; // …} 
Why can you call another constructor at the beginning of a constructor block, but not at the end of the block, or in the middle of the block? 
Well, let's break it down into two cases. (1) You're calling a "base" constructor, and (2) you're calling a "this" constructor. 
For the "base" scenar
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/2VUScxrXOgddGGVsS-2ubYXsq8w/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/2VUScxrXOgddGGVsS-2ubYXsq8w/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/2VUScxrXOgddGGVsS-2ubYXsq8w/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/2VUScxrXOgddGGVsS-2ubYXsq8w/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</description>
				<link>http://blogs.msdn.com/ericlippert/archive/2010/01/28/calling-constructors-in-arbitrary-places.aspx</link>
				<author>Eric Lippert</author>
				<pubDate>Thu, 28 Jan 2010 15:10:00 GMT</pubDate>
			</item>
	
			<item>
				<title>Extensible Output Caching with ASP.NET 4 (VS 2010 and .NET 4.0 Series)</title>
				<description>[In addition to blogging, I am also now using Twitter for quick updates and to share links. Follow me at: twitter.com/scottgu]    This is the fourteenth in a series of blog posts I’m doing on the upcoming VS 2010 and .NET 4 release.&amp;#160; Today’s post covers some of the output caching extensibility improvements being made to ASP.NET 4.&amp;#160; These can be used by all ASP.NET 4 applications – including those built using both ASP.NET Web Forms and ASP.NET MVC.    Output Caching Today    ASP.NET
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/GDAL3DDQHPy4hJLc4qkQ_gITjQo/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/GDAL3DDQHPy4hJLc4qkQ_gITjQo/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/GDAL3DDQHPy4hJLc4qkQ_gITjQo/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/GDAL3DDQHPy4hJLc4qkQ_gITjQo/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</description>
				<link>http://weblogs.asp.net/scottgu/archive/2010/01/27/extensible-output-caching-with-asp-net-4-vs-2010-and-net-4-0-series.aspx</link>
				<author>ScottGu</author>
				<pubDate>Thu, 28 Jan 2010 07:27:22 GMT</pubDate>
			</item>
	
			<item>
				<title>Creating attached properties</title>
				<description>Now that you understand what attached properties are, we’re in the position to look at what is needed for creating attached properties. Since we’re building custom code, we do really need to rely in the RegisterAttached method (of the DependencyProperty class). Creating a new attached properties means doing the following:     adding a static DependencyProperty field to the class;     using the RegisterAttached method for creating the field which is used as a store for the dependency property;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ahDTQ4Cet7gPtSUiNBbfHylZ-fg/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ahDTQ4Cet7gPtSUiNBbfHylZ-fg/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ahDTQ4Cet7gPtSUiNBbfHylZ-fg/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ahDTQ4Cet7gPtSUiNBbfHylZ-fg/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</description>
				<link>http://feedproxy.google.com/~r/Laneten/~3/MZcNjaF_U3s/creating-attached-properties.aspx</link>
				<author>luisabreu</author>
				<pubDate>Wed, 27 Jan 2010 10:20:27 GMT</pubDate>
			</item>
	
			<item>
				<title>Playing With LINQ: Getting Interface Property Implementations</title>
				<description>Today, my friend Nuno was writing some code to get the PropertyInfos of a class implementation of an interface.
Given this interface:public interface ISomeInterface
{
    int IntProperty { get; set; }
    string StringProperty { get; }
    void Method();
}
and this class:public class SomeClass : ISomeInterface
{
    int ISomeInterface.IntProperty { get; set; }
    public int IntProperty { get; private set; }
    public string StringProperty { get; private set; }
    public void Method() { }
}
Nu
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/0Uk-ZyvB3Djbwgj0_RDZNf5qK7E/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/0Uk-ZyvB3Djbwgj0_RDZNf5qK7E/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/0Uk-ZyvB3Djbwgj0_RDZNf5qK7E/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/0Uk-ZyvB3Djbwgj0_RDZNf5qK7E/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</description>
				<link>http://msmvps.com/blogs/paulomorgado/archive/2010/01/27/playing-with-linq-getting-interface-property-implementations.aspx</link>
				<author>Paulo Morgado</author>
				<pubDate>Wed, 27 Jan 2010 02:22:00 GMT</pubDate>
			</item>
	
			<item>
				<title>Type initialization changes in .NET 4.0</title>
				<description>This morning, while checking out an email I&amp;#39;d received about my brain-teasers page, I discovered an interesting change to the CLR in .NET 4.0. At least, I think it&amp;#39;s interesting. It&amp;#39;s possible that different builds of the CLR have exhibited different behaviour for a while - I only have 32-bit versions of Windows installed, so that&amp;#39;s what I&amp;#39;m looking at for this whole post. (Oh, and all testing was done under .NET 4.0b2 - it could still change before release.)
Note: to try any
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/8cVezPy-Bd4DJcCm4JKvli0oCRA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/8cVezPy-Bd4DJcCm4JKvli0oCRA/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/8cVezPy-Bd4DJcCm4JKvli0oCRA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/8cVezPy-Bd4DJcCm4JKvli0oCRA/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</description>
				<link>http://feedproxy.google.com/~r/JonSkeetCodingBlog/~3/D1o3VuErqVA/type-initialization-changes-in-net-4-0.aspx</link>
				<author>skeet</author>
				<pubDate>Tue, 26 Jan 2010 17:48:00 GMT</pubDate>
			</item>
	
			<item>
				<title>Magellan is on CodePlex</title>
				<description>I have migrated the Magellan source code and releases to CodePlex.

http://magellan.codeplex.com 

A few benefits to using CodePlex are:


I use TeamCity to publish releases for each check in (thanks to the MSBuild Deployment Tools project). The releases are hidden at first (in case they have problems) and once I have tested them they become public. 
You can use the RSS feed to stay up to date.
You can use the Issue Tracker to report bugs.
You can use the online source code b
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/8YqlvOjlhqjkHpynRoTbdYEoBII/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/8YqlvOjlhqjkHpynRoTbdYEoBII/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/8YqlvOjlhqjkHpynRoTbdYEoBII/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/8YqlvOjlhqjkHpynRoTbdYEoBII/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</description>
				<link>http://www.paulstovell.com/magellan-codeplex</link>
				<author>Paul Stovell</author>
				<pubDate>Tue, 26 Jan 2010 07:04:16 GMT</pubDate>
			</item>
	
			<item>
				<title>My ASP.NET MVC in Action talk from Houston TechFest (webcast)</title>
				<description>Here is a talk I gave on 26 September 2009 at the Houston TechFest.&amp;#160; Thanks to Shawn Weisfeld for recording it!
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/pJEjIy5w5SP_KaZEpGWpX0K4Syk/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/pJEjIy5w5SP_KaZEpGWpX0K4Syk/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/pJEjIy5w5SP_KaZEpGWpX0K4Syk/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/pJEjIy5w5SP_KaZEpGWpX0K4Syk/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</description>
				<link>http://feedproxy.google.com/~r/jeffreypalermo/~3/cgZ0_g1X3e8/</link>
				<author>Jeffrey Palermo</author>
				<pubDate>Mon, 25 Jan 2010 22:02:00 GMT</pubDate>
			</item>
	
			<item>
				<title>Why are unused using directives not a warning?</title>
				<description>As I’ve discussed before, we try to reserve warnings for only those situations where we can say with almost certainty that the code is broken, misleading or useless. One reason for trying to ensure that warnings are not “false positives” is that we don’t ever want to encourage someone to take working, correct code and break it so as to remove the warning. Another is that since many people compile with “warnings are errors” turned on, we do not want to introduce a whole lot of unnecessary build
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/TNcEKZMMGSuJq__cJggiOSENc5U/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/TNcEKZMMGSuJq__cJggiOSENc5U/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/TNcEKZMMGSuJq__cJggiOSENc5U/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/TNcEKZMMGSuJq__cJggiOSENc5U/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</description>
				<link>http://blogs.msdn.com/ericlippert/archive/2010/01/25/why-are-unused-using-directives-not-a-warning.aspx</link>
				<author>Eric Lippert</author>
				<pubDate>Mon, 25 Jan 2010 15:00:00 GMT</pubDate>
			</item>
	
			</channel>
		</rss>
