jmf

Members
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jmf

  • Rank
    Newbie

Profile Information

  • Gender
    Not Telling
  1. That's exactly what I did. Thanks a lot!
  2. Thanks for the answer. So, as far as I understand, as long as 1 is true (classes have a default constructor) and we don't care about a performance hit necessarily, we could live with using the constructor instantiation also on the full .net framework. For us the main reason is that we share the codebase between some Silverlight and WPF apps. Since in Silverlight the constructor is called, we have logic there. If we were to move it to OnLoad() then in case we instantiate the objects ourselves, we'd have to additionally call OnLoad() which is not really feasible. Do you think that this makes sense?
  3. Hi, I've noticed that when using the full .Net version of Perst it creates objects without invoking their constructor. Could you please let me know what the reason for this is? As we have some logic in the constructors, we would need them invoked. For the time being I've changed the code to actually call the constructor instead of using formatterservices.getuninitializedobject and it seems to work. Was the only reason for using this better performance? Thanks!