Kim Hamilton - All Comments

Click & Solve » Advanced resource debugging with Resview

Click & Solve » Advanced resource debugging with Resview — Fri, 06 Mar 2009 22:25:11 GMT

PingBack from http://www.clickandsolve.com/?p=19014

Advanced resource debugging with Resview

Kim Hamilton — Fri, 06 Mar 2009 22:12:51 GMT

In an earlier blog about resource fallback essentials , I said that the resource diagnostic tool resview

Working with the ResourceManager [Kim Hamilton]

BCL Team Blog — Tue, 17 Feb 2009 00:30:43 GMT

The essentials of resource fallback and how to debug failures Resource loading failures can be tricky

Cleaning up after yourself (Dispose(void) doesn’t get called for you) | Tmao Coders

Tue, 18 Nov 2008 09:43:41 GMT

PingBack from http://www.tmao.info/cleaning-up-after-yourself-disposevoid-doesnt-get-called-for-you/

re: When to call Dispose

Jérémie Chassaing — Mon, 17 Nov 2008 12:24:08 GMT

A typical ambiguous case can be found with readers and writers (StreamReader, StreamWriter, BinaryReader, BinaryWriter...).

They implement IDisposable just in case the have ownership on the underlying stream, but the documentation is not clear about it.

When you need to keep the stream open (to use several differents writers, or when using a memory stream), you must use Flush and not Close (= Dispose).

My opinion is that you should always call Flush, and then call Dispose only if you need to get rid of the underlying stream.

A bit confusing...

No need to throw out the baby with the streamwriter; they probably could have just put in a replacement

Sorting it all Out — Thu, 13 Nov 2008 15:13:16 GMT

So anyway, Kim 's other recent blog, entitled Making a StreamWriter usable even after given garbage characters

re: When to call Dispose

Mike Dimmick — Thu, 13 Nov 2008 13:31:21 GMT

In WinForms, controls that are owned by another control (in that control's Controls collection, either by calling .Add or by setting the control's Parent property) are disposed automatically when that control is itself disposed. Top-level forms are disposed when the window is destroyed. This largely means that the programmer doesn't have to do anything. However, there is no Destroy method - you destroy a window by calling Dispose.

In addition, any non-graphical components added to a form in Visual Studio's designer cause VS to generate code that adds them to a System.ComponentModel.Container named 'components', and an override of Dispose which disposes the container, which in turn disposes all of the contained components. This works for desktop apps but is BROKEN for smart device development (Compact Framework). I added a bug on this - Connect feedback ID 305534 - which has STILL had no reply after more than a year.

On Compact Framework you don't have space for VM overflows, particularly on Windows Mobile 5.0 devices where there is often a tiny amount of VM actually available, due to the DLL loading model and vast number of eXecute In Place DLLs. Calling Dispose everywhere is absolutely required. Leaving it to Finalize is too late.

re: What does the NeutralResourcesLanguageAttribute do?

MSDNArchive — Wed, 12 Nov 2008 04:11:04 GMT

Thanks David, that's good news! Can you re-post the link though? (It links to my post.)

re: What does the NeutralResourcesLanguageAttribute do?

David Kean — Wed, 12 Nov 2008 03:50:27 GMT

We added a warning to FxCop that fires on assemblies that contain ResourceManager-managed resources, but do not have the NeutralResourcesLanguageAttribute specified.

For more information, see: http://blogs.msdn.com/kimhamil/archive/2008/11/11/what-does-the-neutralresourceslanguageattribute-do.aspx

What does the NeutralResourcesLanguageAttribute do? | Tmao Coders

What does the NeutralResourcesLanguageAttribute do? | Tmao Coders — Wed, 12 Nov 2008 03:11:59 GMT

PingBack from http://www.tmao.info/what-does-the-neutralresourceslanguageattribute-do/