Open GoogleCodeExporter opened 9 years ago
The actual fix is to modify the EntityInstanceBase.generated.cst file by
changing
the following:
<% if ( IncludeWCFDataAttributes ) { %>
[DataContract]
<% } else { %>
[Serializable]
<% } %>
to
<% if ( IncludeWCFDataAttributes ) { %>
[DataContract, Serializable]
<% } else { %>
[Serializable]
<% } %>
How does one get access to make coding modifications, I can implement this
change.
Original comment by vi...@daviworld.net
on 22 Jan 2009 at 4:26
Serializable attribute was applied like you show above until Rev 757. The fix
you
propose seems appropriate. Would like to confirm that this was an unintended
side
effect.
This issue is related to Rev 757
http://code.google.com/p/nettiers/issues/detail?id=87
Original comment by rhet...@gmail.com
on 23 Jan 2009 at 6:25
Also needs to make the similar change in EntityData template. After that the
sample
app seems to be working without issue. Generated using Northwind.
Original comment by rhet...@gmail.com
on 23 Jan 2009 at 6:50
Patch
Original comment by rhet...@gmail.com
on 23 Jan 2009 at 7:06
Attachments:
I had an application that tested this. Making this change worries me a little.
Please fully test entity serialization in order to see if this works. You
shouldn't
have to mark things serializable when using WCF.
Is the Admin Website running through the Web Services maybe. You shouldn't be
able
to use the WebServices with the DataContract attributes.
I don't know, the DataContract attributes were in bad shape when I fixed them.
I
will see if I still have all my tests I ran when I coded this.
jeff
Original comment by jmhin...@gmail.com
on 23 Jan 2009 at 1:32
I see now that the DataContract should be an acceptable substitute for the
serializable attribute. Maybe the issue is with the way the admin site is
setup. I'm
working on getting a sample running that uses the web services project...
Original comment by rhet...@gmail.com
on 24 Jan 2009 at 2:09
Original comment by rhet...@gmail.com
on 3 Feb 2009 at 5:45
Original comment by bniemyjski
on 25 May 2009 at 3:30
What is the status of this bug?
Original comment by bniemyjski
on 25 May 2009 at 4:20
Although the DataContract attribute is appropriate for WCF it is not
appropriate
when serializing elsewhere. Serialization is done directly when making a deep
copy
of the object, specifically in the EntityHelper Clone<T> method. The classes
mentioned should be marked as serializable for the DeepCopy to work. This
creates
an issue anywhere deepcopy is used.
As far as I can tell the suggested changes resolve the issue.
Original comment by jbai...@baileysc.com
on 19 Aug 2009 at 2:12
On the latest version of code that is downloadable from main google code page,
this
error still exists.
Original comment by depictur...@gmail.com
on 30 Sep 2009 at 2:02
Revision 821 does not include this patch and the exception
Type 'SomeNamespace.Web.Data.ProviderDataSourceDeepLoadList' in Assembly
'SomeNamespace.Web, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'
is not marked as serializable.
still occurs in the website admin pages as described above when selecting
IncludeWCFDataAttributes.
Original comment by peterrie...@bluewin.ch
on 2 Dec 2009 at 10:51
The current featured download still has this issue when
IncludeWCFDataAttributes is set to true.
Original comment by matrobic...@gmail.com
on 17 Feb 2011 at 9:02
Xkubr, could you please take a look into this.
Thanks
-Blake
Original comment by bniemyjski
on 4 Mar 2011 at 8:05
Original issue reported on code.google.com by
gmd...@gmail.com
on 7 Jan 2009 at 10:56