Peter Duniho
7/22/2008 12:19:00 AM
On Mon, 21 Jul 2008 16:40:59 -0700, John W. <no_spam@_nospam.com> wrote:
> Thanks for the feedback ...
>
>> Define ".NET Framework". Do you mean just the CLR? Or do you mean to
>> include any assembly provided by Microsoft as part of .NET?
>
> Yes, the CLR - anything that's installed with the framework installer.
All due respect, that's an inconsistent answer. The CLR is just the
run-time (mscorlib.dll). The .NET Framework includes more than that.
Different parts of .NET are found in different assemblies.
I take your answer to mean _all_ of .NET, not just the CLR (the latter
would be easier...just look for the one DLL).
> [...]
> I was also hoping to avoid this route if possible. My app will be
> processing
> arbitrary types on 2.0 or later and I need to distinguish between
> user-defined types and native .NET types.
I'm curious as to why, if you don't mind sharing. It seems to me to be a
somewhat arbitrary requirement, since the types would otherwise behave
exactly the same. What is it about .NET types versus third-party types
that makes them so different that you need to track them independently?
I don't know. Maybe someone else will have better advice as to how to
identify all of the types that come from .NET, or alternatively how to
automatically determine a complete list of the assemblies that make up
..NET (I figure that would be a reasonable alternative). But on the face
of it, if it were me, I'd be working to redefine the problem so that it's
easier. :)
Pete