By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,735 Members | 1,462 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,735 IT Pros & Developers. It's quick & easy.

Problems after de-serializing...

P: n/a
Good day group!

I have created a nice filtering plugin system, where all filters derive
from a Filter class, and they pass a PictureData object between them.

I have a problem though. I am able to save the filter setup by
serializing the filter chain to a file, and there seems to be no
problems when de-serializing, as the filter chain will seem to
re-generate properly.

But problems arise when I add a new filter to the de-serialized chain -
it will not recognize the de-serialized PictureData object as being of
the same type of the PictureData object passed to it.

Does anybody have any experience with this kind of problem?

Thanks in advance.

Jan 23 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
By the way (I forgot to add some information): I'm using VS2005 / .NET
2.0.

The classes Filter and PictureData have their own project, and are
compiled into a DLL which is shared with some other projects.

And the problem does NOT arise because I rebuilt the DLL between doing
the serializing and the de-serializing.

And I should add that there are NO problems when I use "builtin" types,
like e.g. System.Drawing.Bitmap.

Jan 23 '06 #2

P: n/a
I have solved the problem (not knowing exactly what caused it, which is
frustrating):

Just moved the PictureData class definition to its own project/DLL...

If someone can explain this, explanations are welcome!

Jan 23 '06 #3

P: n/a
I would think that it has something to do with the fact that the filters
and the picture data are not loaded before serialization. I'm just guessing
here.

If you could post an example, it would help in figuring it out.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

<mo********@gmail.com> wrote in message
news:11**********************@g49g2000cwa.googlegr oups.com...
I have solved the problem (not knowing exactly what caused it, which is
frustrating):

Just moved the PictureData class definition to its own project/DLL...

If someone can explain this, explanations are welcome!

Jan 23 '06 #4

P: n/a
Are you using the XML serializer provided by the .NET?

Jan 23 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.