search
Japanese Chinese Nederlands Espanol Italiano Deutsch Francais Twitter Rss Feeds
.NET Framework GroupsView
Deployment Server
.NET Distributed_Apps
.NET
.NET ADO.NET
.NET ASP.NET
.NET ASP.NET Security
.NET ASP.NET Webcontrols
.NET ASP.NET Web Services
.NET Clr
.NET Compact Framework
.NET Drawing
.NET Interop
.NET Micro Porting
.NET Performance
.NET Web Services
.NET Windows Forms
.NET Windows Forms Controls
.NET General
.NET Csharp
.NET Visual Basic
.NET Vc
.NET Security
.NET Xml
Scripting Jscript
Scripting Visual Basicscript
Scripting Wsh
Smartphone Developer
Visual Basic Com
Visual Basic Controls
Visual Basic Crystal
Visual Basic Database Ado
Visual Basic Syntax
Visual Basic Vista Compatibility
Visual Basic Winapi
Vc Atl
Vc Debugger
Vc Language
Vc Mfc
Vc Stl
Visio Developer Visual Basica
Vsnet Debugging
Windows Powershell
Windowsce Embedded Vc
Xml
Xsl

Group SummariesView
.NET Framework
Access
BizTalk
Certifications
CRM
DDK
Exchange Server
FoxPro
French
French .NET
Games
German
German .NET
Graphic Design
IIS
Internet
ISA Server
Italian
Italian .NET
Maps
MCIS
Miscellaneous
Mobile Application Development
Money
MSN
Networking
Office
Ops Mgr
Publisher
Security
SharePoint
Small Business
Spanish
Spanish .NET
SQL Server
Systems Management Server
Transaction Server
Virtual PC / Virtual Server
Visual Studio
Win32
Windows 2000
Windows 2003 Server
Windows 7
Windows Live
Windows Media
Windows Update
Windows Vista
Windows XP
 

View All Microsoft NET ASP NET Web Services Posts  Ask A New Question 

WCF 3.5 and Problem with KnownTypeAttribute - coconet

Friday, February 29, 2008 11:34 AM

I have an Interface and an implementing class (receiver) and calling
class (sender) in a single DLL. The DLL is referenced in a web site
that received WCF calls and also in a seperate web site that makes
calls to the WCF site .svc. Why would I get an Exception about
KnownTypeAttribute?


InnerException thrown is:

System.Runtime.Serialization.SerializationException: Type
'nstestSecurity.TestPrincipal' with data contract name
'TestPrincipal:http://schemas.datacontract.org/2004/07/nstest.Security'
is not expected. Add any types not known statically to the list of
known types - for example, by using the KnownTypeAttribute attribute
or by adding them to the list of known types passed to
DataContractSerializer..

But my stuff looks like this:

[KnownType(typeof(IPrincipal))]
[DataContract(Name="DashboardPrincipal")]
public class TestPrincipal : IPrincipal
{
....
}

An instance of TestPrincipal is one of two parameters for a class that
uses this interface:

[ServiceContract(Name="IWcfReceiver",Namespace="http://nstest/200804/IWcfReceiver")]
public interface IWcfReceiver
{
[OperationContract]
List<ITestStuff> Do( IPrincipal inputPrincipal , List<ITestStuff>
testList );
}
reply
 

Hi coconet,Regarding on the "Type not serializable" exception you encountered, - stchen

Sunday, March 02, 2008 10:42 PM

Hi coconet,

Regarding on the "Type not serializable" exception you encountered, it is a
typical error in WCF service when you use base class/interface with derived
classes actually send in WCF service method.

For your case, the problem here is that you only declare the Interface type
in your WCF method( the IPrincipal type which is not a DataContract).
However, WCF service will only expose metadata for types that is decorated
with "DataContract" attribute or any type that is declared as "KnowType".
I saw the you've add "KnowTypeAttribute" in the "TestPrincipal" class, this
is not the correct means of using "KnownTypeAttribute".
interface) or on a DataContract type which has member of the base
type/interface. See the following reference:

http://msdn2.microsoft.com/en-us/library/ms730167.aspx

To address the problem in your case, since you haven't use a base class,
you can add the known type declaration at service contract level. e.g.

=========
[ServiceContract]
[ServiceKnownType(typeof(TestPrincipal ))]
public interface IYourServiceInterface
....
==============

the following article include all the three means that can be used for
apply "KnownType" info for WCF service's  custom data contract:

http://footheory.com/blogs/bennie/archive/2007/07/28/handling-data-contract-
object-hierarchies-in-wcf.aspx

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------

ceiver")]
reply

Hi,Found a solution to your problem? - Marc

Thursday, March 06, 2008 3:21 AM

Hi,

Found a solution to your problem? I'm having a simular issue where I get the knowType exception

/Marc

BizTalk Utilities - Frustration free BizTalk Adapters
http://www.topxml.com/biztalkutilities
reply

I got into something else and don't remember what the fix should be,after some - coconet

Tuesday, April 08, 2008 11:14 PM

I got into something else and don't remember what the fix should be,
after some more research I think I got it but did not actually
implement a solution.

I think the problem has to do with my using a List<T> of an Interface
for a return type and for a parameter. Whent he List<T> is serialized,
the receiver expects an array of a concrete type that it can convert
to the list of a type. When passing a list of Interface, the class
that implements it could be "anything" so it doesn't rehydrate
properly.

I think I was being too lazy in hoping I could just pass things around
this way, I am pretty sure that changing the method signature to
take/receive an array of each concrete type (instead of a single
method that gives/expects a List of Interface) would work.
reply

Previous Microsoft NET ASP NET Web Services conversation.