Error "Cannot find the assembly..." when Deserializing

Hello,


Few days I'm trying to solve this strange problem. It's giving me a headake. :(

I have created class library and console aplication. When I serialize this class in console app and then desiarelize everything is fine. (console app was designed only for testing purpose)

Then I copied all classes from class library to my other solution. When I try to desiarelize I get message:

"Cannot find the assembly MyLibrary, Version=1.0.2140.18983, Culture=neutral, PublicKeyToken=null."

I tryied to move these classes to new class library project and use reference to it, but I got same problem.


Regards in advance,
Andrius

I dont know exactly what your problem is but you can try this:

Check your Assembly Folder! Located at

C:\WINNT\assembly

Your Solution is always checking your assembly cache first. Delete all versions of your assembly there and deploy your freshly build assembly version to the cache.

BTW: I prefer to version my assembly myself and not have Vs do it. So I change the 1.0.*.* always to a fix number and do the versioning myself. Like 1.0.0.0

HTH,

Stephan

In C:\WINNT\assembly there is no such DLL and when I tried to copy there it says that name itn's strongly typed.

Quote:

---

Originally Posted by Sgt-Peppa

I dont know exactly what your problem is but you can try this:

Check your Assembly Folder! Located at

C:\WINNT\assembly

Your Solution is always checking your assembly cache first. Delete all versions of your assembly there and deploy your freshly build assembly version to the cache.

BTW: I prefer to version my assembly myself and not have Vs do it. So I change the 1.0.*.* always to a fix number and do the versioning myself. Like 1.0.0.0

HTH,

Stephan

---

Oh Ok I see.
Well than that should not be your problem.
Sorry for not being more of a help. I dont have any other ideas.

You could try to sign your assembly with a strong name key and then use the gacutil to deploy it to the Assembly cache but actually I doubt that it will solve your problem.

Sorry again,

Stephan

RESOLVED. Hard one...