2
Answers

Resource file serialization error

Sam

Sam

13y
1.9k
1
Hello good fellows,

I have a resource file in which I save all my controls settings.
It was OK until I did something that somehow disturbed saving of the resources.

When trying to save the file, I get a serialization exception with the error message
"control .....is not marked as serializable".

I can not read the file, as it is probably does not exist (I get reading header error).

The same saving error message is true for any control.
I made the class [Seriizable], made all controls public, but for no avail.

Attached is my method that takes care of saving. It is quite simple.

Thanks

Sam

Attachment: paramssave.rar

Answers (2)
0
Vulpes

Vulpes

NA 98.3k 1.5m 12y
It depends to what extent the C# 3.0 application made use of features that were introduced in that version of the language. 

If the application made heavy use of these features (notably LINQ), then it will probably be impractical to translate it to C# 2.0 and the only sensible option would be to start again.

Apart from that, a translation should be feasible as C# 3.0 is backwards compatible with C# 2.0.

For a list of the stuff that was introduced in C# 3.0, see here:

http://msdn.microsoft.com/en-us/library/bb308966.aspx 





Accepted
0
Vulpes

Vulpes

NA 98.3k 1.5m 12y
You should be able to reuse a lot of it with some simple modifications.

For example:

Implicitly typed variables - just replace 'var' with the actual type.

Lambda expressions - replace with anonymous methods which were introduced in C# 2.0.

Object and collection initializers  - should be simple to rewrite.

However, anything to do with LINQ (to objects, XML or SQL) will need to be rewritten using 'traditional' code  - there's no other way.
0
sean li

sean li

NA 3 2.6k 12y
Hi Vulpes: Thanks for your info. The application (I believe it was coded in 3.0)made use of Implicitly local variables, Lambda expressions, delegate Type, et. It didn't work properly in .NET 2.0 run time. Should we modify or start the scrach in C#2.0?