Mark Levison

Musings on No Touch Deployment, .NET development and photography

<October 2008>
SuMoTuWeThFrSa
2829301234
567891011
12131415161718
19202122232425
2627282930311
2345678


Navigation

Other

Blogroll

Subscriptions

Post Categories



Monday, March 08, 2004 - Posts

VS.NET 2003 Find in Files suddenly stopped working
One minute it works, the next it doesn't. A few minutes ago I was successfully search files with "Find in Files...". Now I get "Find all "xxx.xxx", Match case, Subfolders, Find Results 2, "C:\darwin\insight.net\test", "*.cs *.java *.jsl"" results in the message
"No files were found to look in.".

Arrrggggghhhhhhhh. Has anyone seen this before?
Google doesn't have much useful to say in the first 100 hits. <br>
Update: a search of Google Groups shows that many people have had this problem with no solution found. BTW Rebooting seems to solve the problem for the moment

posted Monday, March 08, 2004 2:43 PM by mlevison with 1 Comments

IDisposable Pattern best practices question
I've spent the morning working on series of resource leak problems. After ensuring that our production code and the unit tests call dispose, I'm left with an interesting question. How far should I propogate IDisposable through my containment heirarchy? Suppose I have class Foo that contains an image:

class Foo : IDisposable {
 private Image image
...
pubic void Dispose(bool disposing) {
...
image.Dispose()
}

Should the class Foobar that contains Foo also implement Dispose? So that Foo.Dispose() has chance of being called, without waiting for the GC? How far should IDisposable ripple through the code?

Time for a nice cup of tea - maybe that will help clarify my thinking.

posted Monday, March 08, 2004 12:01 PM by mlevison with 0 Comments




Powered by Dot Net Junkies, by Telligent Systems