From: Arne Vajhøj on
On 01-07-2010 10:12, Jeff Johnson wrote:
> "Arne Vajh�j"<arne(a)vajhoej.dk> wrote in message
> news:4c2be245$0$282$14726298(a)news.sunsite.dk...
>>>> I'll have a look at what I can do via reflection.
>>>
>>> That's easy: anything.
>>
>> There are a few things it can't: make peace in the
>> middle east etc..
>
> That's because the attitudes on both sides are unmanaged....

Yep.

They need garbage collection.

:-)

Arne
From: Arne Vajhøj on
On 30-06-2010 22:57, Peter Duniho wrote:
> Arne Vajh�j wrote:
>> [...]
>>> I'm sure you can accomplish it using reflection. But as I mentioned
>>> before, it's usually not a good idea to do so. If you need this kind of
>>> functionality, it usually means your design is broken.
>>
>> My guess would be that >90% of all .NET apps uses reflection
>> for something, so ...
>
> I doubt that's true. In very large applications it may be difficult to
> avoid it completely, but even there the situations are generally rare.
> And in smaller desktop programs, utilities, command-line tools, etc.
> there's often no need for reflection at all.

Web app with lots of class names in web.config?

App using database via DbProviderFactory.

Serialization.

Web services.

O/R-mappers.

IoC/DI frameworks.

Etc.

> However, be that as it may, I wasn't talking about the reflection
> aspect. I was talking about the "inherit a class but don't use its
> functionality" aspect.

Ah - that I agree with.

Arne