Otherwise, the class maps listing is going to contain a number of classes that you might not want... For instance, there is a class map for System.Object. Hence, you'd somehow need to provide a filter to limit it to valid types. Once you get there, you might as well just keep a list of all the support types or do some assembly level reflection for all types in a given namespace or implementing a particular interface.
> Otherwise, the class maps listing is going to contain a number of classes
> that you might not want... For instance, there is a class map for
> System.Object. Hence, you'd somehow need to provide a filter to limit it
> to valid types. Once you get there, you might as well just keep a list of
> all the support types or do some assembly level reflection for all types in
> a given namespace or implementing a particular interface.
> On Thursday, September 13, 2012 9:08:01 AM UTC-5, Alex Brown wrote:
>> Didn't think so. At least i wasn't going mad.
>> Easiest way to describe it is creating a kind of web api
>> request comes in as /customer/find-all
>> Rather than strong typing each of my services, i want a "base" service to
>> handle them
>> so, "customer" is the type
>> We then look in our AllClassMaps collection, for a type, where name is
>> "customer"
>> Can then instantiate the according repository, based on the retrieved
>> Type from AllClassMaps
>> Hope that makes sense....
>> On 13 September 2012 15:03, craiggwilson <craigg...@gmail.com> wrote:
>>> No, there is not a way to do this. May I ask why you need this
>>> functionality?
>>> On Thursday, September 13, 2012 8:57:24 AM UTC-5, Alex Brown wrote:
>>>> Is there a way of getting back a collection of all currently mapped
>>>> types?
