Remote dataportal business object dependecy

Remote dataportal business object dependecy

Old forum URL: forums.lhotka.net/forums/t/12017.aspx


btardif posted on Tuesday, June 11, 2013

Good day to all,

I can't seem to find an answer to this question so I decided to ask it here.

We currently are happily using CSLA with a couple of our web sites and are using a couple of data portals to fit our different needs.

The main problem (well, inconvenient might be a better word) is that every time we change the version of our web site, we change the version of everything in the solution (so the version of the data portal as well) meaning that we have to redeploy the web site but every data portal as well even if the code that is being serviced by the data portal has not change.

Is there a way of circumventing this? Aside from the obvious solution which would be to stop managing the version numbers at the solution level and manage them on a project by project basis.

Thank you in advance.

Ben

JonnyBee replied on Tuesday, June 11, 2013

Hmm, 

In terms of serialization the version number is part of the contract. 

So the options that I know of would involve either:

Both options may introduce new bugs/problems so my recommendation would be to redeploy everything!

Copyright (c) Marimer LLC