<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><item><title>Comment on Get a visual parent of an element in Silverlight by gifts</title><link>/get-a-visual-parent-of-an-element-in-silverlight#comment-1797</link><description>Very informative and helpful post. You have good command on the topic and have explained in a very nice way. Thanks for sharing</description><pubDate>2012-01-31T11:33:13</pubDate><guid isPermaLink="false">urn:comment:1797</guid></item><item><title>Comment on Orchard custom field list by PAMP gold</title><link>/orchard-custom-field-list#comment-1795</link><description>Hi great article I really enjoy reading this blog,thanks, good topic I am pleased to say it is interesting that this blog has a great variety of viewpoints to better understand the situation and that is what most caught my attention and has a great variety of comments thanks
</description><pubDate>2012-01-25T21:59:42</pubDate><guid isPermaLink="false">urn:comment:1795</guid></item><item><title>Comment on Get a free App Hub membership by john</title><link>/get-a-free-app-hub-membership#comment-1793</link><description>Want an apphub account</description><pubDate>2012-01-23T08:39:28</pubDate><guid isPermaLink="false">urn:comment:1793</guid></item><item><title>Comment on Tasks in Visual Studio by Rick</title><link>/tasks-in-visual-studio#comment-1774</link><description>I don't find a menu choice for Task List in my View menu. However, there is an options/environment/task list page. 
Is the Task List view not available in VS 2010-express?</description><pubDate>2011-12-09T21:46:05</pubDate><guid isPermaLink="false">urn:comment:1774</guid></item><item><title>Comment on Great tool for SQL Server Compact Databases by Christian Helle</title><link>/great-tool-for-sql-server-compact-databases#comment-1771</link><description>I'm glad you like the tool :)</description><pubDate>2011-12-05T23:17:56</pubDate><guid isPermaLink="false">urn:comment:1771</guid></item><item><title>Comment on IcoFX - The Free Icon Editor by rudraksha</title><link>/archive/2007/02/28/2385.aspx#comment-1765</link><description>userful</description><pubDate>2011-11-25T10:05:26</pubDate><guid isPermaLink="false">urn:comment:1765</guid></item><item><title>Comment on Cool gradient effect in C# by Tanuj Kumar</title><link>/archive/2005/11/29/671.aspx#comment-1758</link><description>This is one of the best articles I read online. No crap, just useful information. Very well presented.
This link...
http://www.mindstick.com/Blog/161/Gradient%20background%20in%20c

also helped me to complete my task.

 </description><pubDate>2011-11-15T16:37:57</pubDate><guid isPermaLink="false">urn:comment:1758</guid></item><item><title>Comment on Tip: Do not dispose objects multiple times by porges</title><link>/tip-do-not-dispose-objects-multiple-times#comment-1729</link><description>Personally, I think the rule is just a bad one. The documentation for Dispose() states that it &lt;em&gt;must&lt;/em&gt; be okay for Dispose() to be called multiple times:

&lt;blockquote&gt;If an object's Dispose method is called more than once, the object must ignore all calls after the first one. The object must not throw an exception if its Dispose method is called multiple times. Instance methods other than Dispose can throw an ObjectDisposedException when resources are already disposed.&lt;/quote&gt;

</description><pubDate>2011-09-07T21:55:55</pubDate><guid isPermaLink="false">urn:comment:1729</guid></item><item><title>Comment on Tip: Do not dispose objects multiple times by atkulp</title><link>/tip-do-not-dispose-objects-multiple-times#comment-1724</link><description>Thomas, I was very surprised by this error, because I also wouldn't have made the assumption that one dispose operation would affect a disposable object that it referred to.  Maybe that's best practice, but it seems dangerous!  The fact that MS wrote an FxCop rule for it makes it seem more legit, but maybe it only applies to certain framework objects.

The relevant quote from the CA2202 rule is "If the IDisposable resource of the nested inner using statement contains the resource of the outer using statement, the Dispose method of the nested resource releases the contained resource. When this situation occurs, the Dispose method of the outer using statement attempts to dispose its resource for a second time."</description><pubDate>2011-08-22T16:28:06</pubDate><guid isPermaLink="false">urn:comment:1724</guid></item><item><title>Comment on Tip: Access to modified variable in closures by atkulp</title><link>/tip-access-to-modified-variable-in-closures#comment-1722</link><description>Thanks Peter-John.  Good points on lambdas vs closures vs anonymous methods.  Thanks also for the better example, although once you involve threading you also increase the inherent danger since you can't predict execution order, but the closure just makes it considerably worse!</description><pubDate>2011-08-22T16:04:41</pubDate><guid isPermaLink="false">urn:comment:1722</guid></item><item><title>Comment on LEGO Mindstorms and Windows 7 by atkulp</title><link>/archive/2009/08/18/2572.aspx#comment-1721</link><description>I don't know, but it's definitely frustrating.  Try setting compatibility mode to XP SP2 and see if it runs on Windows 7 better that way.  I can't remember all the steps that I followed, but the basic software itself works now anyway.</description><pubDate>2011-08-22T16:01:10</pubDate><guid isPermaLink="false">urn:comment:1721</guid></item><item><title>Comment on Tip: Access to modified variable in closures by Peter-John Lightfoot</title><link>/tip-access-to-modified-variable-in-closures#comment-1718</link><description>Couple of points: 

First, your introduction paragraph seems to suggest that closures and lambdas are the same thing. Your readers should note that closures are simply anonymous methods (including, therefore, lambdas) that ACCESS a variable in their ENCLOSING scope. In your example, your anonymous method references "x" from its enclosing scope, which gives the anonymous method a "pointer" to the memory location of x, and thereby creates a closure.

Second, an interesting example for seeing the danger of this, is as follows:

for( int x = 0; x &lt; 10; x++ ) {
   new System.Threading.Thread(
      () =&gt; System.Console.WriteLine(x)
   ).Start();
}

The above snippet will clearly print an erratic list of numbers every time, since the anonymous methods will execute at non-deterministic intervals, and will simply use whatever the value of "x" is at that time.

</description><pubDate>2011-08-19T14:43:26</pubDate><guid isPermaLink="false">urn:comment:1718</guid></item><item><title>Comment on Tip: Do not dispose objects multiple times by David Hogue</title><link>/tip-do-not-dispose-objects-multiple-times#comment-1713</link><description>You know, I think this depends completely on how the outer class implements IDisposable.

I've run into this same error before and I never thought to add a finally like this to dispose the inner object.  Probably a really good idea though.</description><pubDate>2011-08-15T18:23:27</pubDate><guid isPermaLink="false">urn:comment:1713</guid></item><item><title>Comment on Tip: Do not dispose objects multiple times by Thomas Eyde</title><link>/tip-do-not-dispose-objects-multiple-times#comment-1712</link><description>That's not entirely true. The case is that the nested using *can* cause this violation. This only happens when the inner class decides to dispose the contained object, something it shouldn't.

StreamWriter is one of the classes which doesn't behave, and it's not possible to cleanly rewrite away the warning.

If this were always the case, the following unit test should pass:

    [TestClass]
    public class UnitTest1
    {
        [TestMethod]
        public void TestMethod1()
        {
            using (var foo = new Foo())
            {
                using (var bar = new Bar(foo))
                {
                    bar.DoNothing();
                }

                Assert.IsTrue(foo.IsDisposed);
            }
        }
    }

    public class Bar : IDisposable
    {
        private readonly Foo _foo;

        public Bar(Foo foo)
        {
        }

        public void DoNothing()
        {
        }

        public void Dispose()
        {
        }
    }

    public class Foo : IDisposable
    {
        public void Dispose()
        {
            IsDisposed = true;
        }

        public bool IsDisposed { get; private set; }
    }
</description><pubDate>2011-08-15T07:44:28</pubDate><guid isPermaLink="false">urn:comment:1712</guid></item><item><title>Comment on LEGO Mindstorms and Windows 7 by &amp;lt;e</title><link>/archive/2009/08/18/2572.aspx#comment-1708</link><description>I have the exact same issue, blue screen during shutdown, everytime after installing a clean version. Thoughts???</description><pubDate>2011-08-09T18:18:16</pubDate><guid isPermaLink="false">urn:comment:1708</guid></item><item><title>Comment on A better way to check your Windows Phone app submissions by Robin</title><link>/a-better-way-to-check-your-windows-phone-app-submissions#comment-1682</link><description>I submitted a comment on this page last week and it still is not shown on the site. It gives me the impression that you are not open to criticism to your WP7 application Marketplace Dashboard... 
I've installed it and think it is quite a cool idea, but it is stuck on Loading Data and reading on the web shows me other users experience this as well. You think you will work on it or shall I just be honest to other WP7-users and review it with 0 stars? </description><pubDate>2011-07-04T13:33:55</pubDate><guid isPermaLink="false">urn:comment:1682</guid></item><item><title>Comment on A better way to check your Windows Phone app submissions by Robin Paardekam</title><link>/a-better-way-to-check-your-windows-phone-app-submissions#comment-1680</link><description>Nice plan Adrian. Just installed it but unfortunately browser control stays blank, loading data, but no luck so far. Using Samsung Omnia 7.5 Mango... Any ideas?</description><pubDate>2011-06-30T16:46:19</pubDate><guid isPermaLink="false">urn:comment:1680</guid></item><item><title>Comment on Get a free App Hub membership by Ryan Lambourn</title><link>/get-a-free-app-hub-membership#comment-1658</link><description>Me want app hub</description><pubDate>2011-06-22T00:00:03</pubDate><guid isPermaLink="false">urn:comment:1658</guid></item><item><title>Comment on Set as Startup Project in Visual Studio by Ulf</title><link>/archive/2009/02/23/2557.aspx#comment-1656</link><description>Or you could select the solution in the Solution Explorer and then click Project&gt;Set StartUp Projects... and set it from there. :-)</description><pubDate>2011-06-10T13:04:11</pubDate><guid isPermaLink="false">urn:comment:1656</guid></item><item><title>Comment on Get an ApplicationBarIconButton by name by atkulp</title><link>/get-an-applicationbariconbutton-by-name#comment-1642</link><description>Absolutely right.  I always forget about the Cast() method in LINQ.  I could have casted the list in the foreach loop for that matter too.  Thanks!</description><pubDate>2011-05-25T05:17:09</pubDate><guid isPermaLink="false">urn:comment:1642</guid></item></channel></rss>
