Comments on: The Known Type Provider http://davybrion.com/blog/2008/07/the-known-type-provider/ Trying to walk that thin line between intelligence and ignorance Thu, 11 Mar 2010 06:13:45 +0100 http://wordpress.org/?v=2.9.2 hourly 1 By: Davy Brion http://davybrion.com/blog/2008/07/the-known-type-provider/comment-page-1/#comment-1198 Davy Brion Sun, 17 Aug 2008 17:46:57 +0000 http://davybrion.com/blog/?p=193#comment-1198 I actually have the KnownTypeProvider in a library (Brion.Library) which is referenced by my application. In my application code, before i start hosting the service i do the following: <code> <div style="font-family: Consolas; font-size: 10pt; color: black; background: white;"> <p style="margin: 0px;">            <span style="color: #2b91af;">KnownTypeProvider</span>.RegisterDerivedTypesOf<<span style="color: #2b91af;">Request</span>>(sharedAssembly);</p> <p style="margin: 0px;">            <span style="color: #2b91af;">KnownTypeProvider</span>.RegisterDerivedTypesOf<<span style="color: #2b91af;">Response</span>>(sharedAssembly);</p> </div> <code> If i start hosting the service and i try to generate a proxy with SvcUtil, all of the known types in my application's library are present in the generated file i haven't tried using those proxies at runtime though, since i put my known types in a shared assembly and use it on both sides. The service's metadata properly returns the known types though, so i guess it should work Btw, you need to register the known types with the KnownTypeProvider client-side as well, at least if you're using the shared assembly approach. Not sure if you still have to do this when you're using generated proxies, but it's probably worth trying if you haven't done so already I actually have the KnownTypeProvider in a library (Brion.Library) which is referenced by my application.

In my application code, before i start hosting the service i do the following:

            KnownTypeProvider.RegisterDerivedTypesOf<Request>(sharedAssembly);

            KnownTypeProvider.RegisterDerivedTypesOf<Response>(sharedAssembly);

If i start hosting the service and i try to generate a proxy with SvcUtil, all of the known types in my application's library are present in the generated file

i haven't tried using those proxies at runtime though, since i put my known types in a shared assembly and use it on both sides. The service's metadata properly returns the known types though, so i guess it should work

Btw, you need to register the known types with the KnownTypeProvider client-side as well, at least if you're using the shared assembly approach. Not sure if you still have to do this when you're using generated proxies, but it's probably worth trying if you haven't done so already

]]> By: Daniel http://davybrion.com/blog/2008/07/the-known-type-provider/comment-page-1/#comment-1184 Daniel Sun, 17 Aug 2008 04:53:33 +0000 http://davybrion.com/blog/?p=193#comment-1184 This seems like it would provide a lot of flexibility since we wouldn't have to declare known types explicitly, but will this method work over layers? If I use the hard-coded attribute style for my service contract, I can access those known types as proxies on the client. Since the GetKnownTypes method is static, if I put this functionality up in the core library, I can't override it in the service layer and provide my known types there. I haven't had much success getting the proxies when updating my service reference in client code. Is it possible to use this in a Core library scenario or should I just suck it up and implement it in the services layer specifically? It'd be nice to package it up where my implementing layers would automatically add the known types for all messages, message handlers, DTOs, et al. for free just by using the base service contract in the core, and these would be available as proxies through the service reference. This seems like it would provide a lot of flexibility since we wouldn’t have to declare known types explicitly, but will this method work over layers? If I use the hard-coded attribute style for my service contract, I can access those known types as proxies on the client. Since the GetKnownTypes method is static, if I put this functionality up in the core library, I can’t override it in the service layer and provide my known types there. I haven’t had much success getting the proxies when updating my service reference in client code. Is it possible to use this in a Core library scenario or should I just suck it up and implement it in the services layer specifically? It’d be nice to package it up where my implementing layers would automatically add the known types for all messages, message handlers, DTOs, et al. for free just by using the base service contract in the core, and these would be available as proxies through the service reference.

]]> By: Daniel http://davybrion.com/blog/2008/07/the-known-type-provider/comment-page-1/#comment-963 Daniel Fri, 01 Aug 2008 00:58:32 +0000 http://davybrion.com/blog/?p=193#comment-963 I was running into the same annoying problem when I was trying to serialize POCOs in my <a href="http://csharpie.blogspot.com/2008/07/publisher-subscriber-pattern-using.html" title="Publisher-Subscriber Pattern using Duplex Channel " rel="nofollow">pub-sub</a> implementation. I was running into the same annoying problem when I was trying to serialize POCOs in my pub-sub implementation.

]]> By: The Inquisitive Coder - Davy Brion’s Blog » Blog Archive » The Request/Response Service Layer http://davybrion.com/blog/2008/07/the-known-type-provider/comment-page-1/#comment-899 The Inquisitive Coder - Davy Brion’s Blog » Blog Archive » The Request/Response Service Layer Sun, 27 Jul 2008 11:07:40 +0000 http://davybrion.com/blog/?p=193#comment-899 [...] The Known Type Provider [...] [...] The Known Type Provider [...]

]]> By: Dew Drop - July 22, 2008 | Alvin Ashcraft's Morning Dew http://davybrion.com/blog/2008/07/the-known-type-provider/comment-page-1/#comment-833 Dew Drop - July 22, 2008 | Alvin Ashcraft's Morning Dew Tue, 22 Jul 2008 11:59:57 +0000 http://davybrion.com/blog/?p=193#comment-833 [...] The Known Type Provider (Davy Brion) [...] [...] The Known Type Provider (Davy Brion) [...]

]]>