Comments for Thomas Levesque's .NET blog

Comment on [WPF] Binding to an asynchronous collection by Sumanth

Sumanth — Thu, 20 Jun 2013 09:28:46 +0000

Awesome.. It worked like a charm.. Solved my issue. I was looking all around and this one was simple and solved my problem! Thanks for posting this Thomas!

Comment on [WPF] Display an animated GIF image by Thomas Levesque

Thomas Levesque — Mon, 10 Jun 2013 08:45:38 +0000

Hi Jackie, the code in this article is obsolete; you should use the code from Codeplex instead (http://wpfanimatedgif.codeplex.com), where this fix has already been made.

Comment on [WPF] Display an animated GIF image by Jackie

Jackie — Mon, 10 Jun 2013 08:28:15 +0000

Thanks for your work. Just one small improvement to handle some GIF files that has Delay set to 0 in metadata, change the following line in method GetFrameInfo from

if (delay.HasValue)

if (delay.HasValue && delay.Value > 0)

Comment on [WPF] Display an animated GIF image by Dominik P

Dominik P — Fri, 31 May 2013 08:06:43 +0000

It gets jump if you are doing something on the UI thread that blocks the dispatcher from updating the animation. Refactor those calls into BackgroundWorker.DoWork/Completed structure and it runs smoothly.

Comment on An easy and secure way to store a password using Data Protection API by Kent Boogaart

Kent Boogaart — Tue, 28 May 2013 12:23:02 +0000

Great post, Thomas. I had completely forgotten about the DPAPI. I don''t have any user secrets to store just now, but this is a great reminder for when I do. It''s worth pointing out that the optional entropy is used to ensure application A1 running as user U cannot gain access to protected data written by application A2 running as the same user. Without the optional entropy, you''re leaving yourself more open to such an attack. On the assumption that your extension methods are only used within your application, you could hard-code your optional entropy right there instead of taking as a parameter. It''s not fool-proof of course, but it''s not really supposed to be - it''s just supposed to make it "more difficult" to compromise the data. Good stuff.

Comment on Using C# 5 caller info attributes when targeting earlier versions of the .NET framework by Akku

Akku — Thu, 23 May 2013 15:00:46 +0000

@Manish: I had the same problem, won”t fix for me, used the workaround posted above.

Comment on Using C# 5 caller info attributes when targeting earlier versions of the .NET framework by Thomas Levesque

Thomas Levesque — Thu, 23 May 2013 14:26:08 +0000

Yes, I tried it, and it works fine. I don”t usually post something on my blog without testing it first

Are you sure you declared the attributes in the correct namespace?

Comment on Using C# 5 caller info attributes when targeting earlier versions of the .NET framework by Manish

Manish — Thu, 23 May 2013 12:23:53 +0000

Do you tried it Frank coz its not working here mate.

Comment on Using C# 5 caller info attributes when targeting earlier versions of the .NET framework by Manish

Manish — Thu, 23 May 2013 12:20:33 +0000

I tried it in VS2012 targeting framework 4.0 but all I get is empty file path,line as well as member Name.
Do I missing something?

Comment on [WPF] How to bind to data when the DataContext is not inherited by Arena

Arena — Wed, 22 May 2013 08:54:57 +0000

Ok…thank you Thomas…:)