15,794,202 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Python questions
View PHP questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by RWey (Top 1 by date)
RWey
2-Sep-10 21:15pm
View
First, I fixed a typo in the call to DeepClone() ... sorry. I think, nevertheless, you get the gist.
And yes ... selectedMembers, while a list of MyBaseObject, does contain derivatives of MyBaseObject.
Again, tho, I'm puzzled as to why the run-time thinks the serialization has anything to do with the TabPage from which I'm calling the DeepClone() method. I would think that all it should care about is the type of class specified in the DeepClone( ... ) call. Even if the serialization is having problems when it encounters derived types of MyBaseObject, I would certainly think the thrown exception would state something a little more germain ... not complain that the TabPage making the call isn't marked as serializable.
One suspicion I had regarding the strange error was that selectedMembers was declared as a field within my TabPage derivative. To test this, I moved selectedMembers into the "superGroup" ( which is derived from MyBaseObject ), and basically moved the foreach iterator into the superGroup as well. Thus, all serializing was contained within a MyBaseObject derivative, with the only link to the TabPage being a simple method call to "Copy those items now". That threw the same exception ... again complaining about the TabPage not being marked serializable.
It makes no sense. Obviously I'm missing something.
BTW, I'm using VS2005.