Have you considered keeping the legacy code in its own AppDomain? I have used this for many upgrade (not just nH) scenarios, and it works quite nicely.
From: [email protected] [mailto:[email protected]] On Behalf Of Chad Ruppert Sent: Saturday, July 21, 2012 10:10 AM To: [email protected] Subject: [nhusers] nh1.2 to 2.1 upgrade with old data and types mapped with type="serializable" throwing serialization exceptions I have been dealing with legacy code written in NHib 1.2, and have wanted to upgrade it to at least 2.1 running on .net 4.0. Everything has gone quite swimmingly, except for types mapped as type="serializable" with the sql type of image on Sql Server 2k. This has been a MAJOR issue, in that it throws serialization exceptions when trying to load entities that contain said mapping. The inner exception complains about not being able to find the 1.2 version of the NHib assembly. I have tried everything from assembly redirects to attempting to load both versions of the assembly. (redirects are ignored, and the dual loading caused type confusion). I am quite frankly losing hope here, and am beginning to believe that it just won't happen without doing some terrible, terrible things. Can you think of anything that might be done? -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/zXx7rLNM95UJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
