C#

Abyss wrote:

What is the preferred approach?

Abyss wrote:

However I expected that such kind of versioning is already implemented by the streaming framework. I tried to obtain the Assembly version from the SerializationInfo but it is always set to current version not to the version which was used when the object was saved.

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]

Tridip Bhattacharjee wrote:

i have very small programming experience

int i = 5; // the value 5 is on stack.
MyObject myObject = new MyObject();
// as discussed, the myObject reference is on stack, but the MyObject content is on the heap.
// now, imagine that the MyObject has an int field.
myObject.intField = 10; // as the contents of myObject are on the heap, the intField is on the heap.

Tridip Bhattacharjee wrote:

in this case why do i need to create static class rather we can create static function inside in any non-static class and my purpose will be solved.

Tridip Bhattacharjee wrote:

i firmly believe that there must be some solid reason when user has to create static class.

Tridip Bhattacharjee wrote:

it will be more help full for me if u come with sample code for static class which show me the importance of creating it instead of create a static method inside in any non-static class. thanks

//Suppose a Class car with properties color and speed and methods accelerate and turn.
// you can do this:
Car red_car = new Car();
Car blue_car = new Car();
red_car.Speed = 100;
red_car.Color = Red;
blue_car.Speed = 65;
blue_car.Color = Blue;

// Now you have 2 instances of the class Car.  blue_car and red_car, each with its own properties.
// next lets execute an algorithm
red_car.Accelerate(-25);
blue_car.Accelerate(10);

//You'll notice that at this point:
//1) red_car and blue_car are different entities.
//2) I NEVER used the class Car as a reference to access properties or methods.

//Suppose a static class MathConstants with properties Pi and e and a method CalculateCircleCircumfence.
// You can NOT do this:
//MathConstants mc = new MathConstants(); 

//You can do this:
double radius = 3.6;
double circumfence = MathConstants.CalculateCircleCircumfence(radius);
double americanpie = 3.141599999;
MathConstants.PI = americanpie;
//know our MathConstants.PI has changed for every usage from this point on.

//You'll notice that at this point:
//1) There are no different entities, because you cannot create them
//2) I ALWAYS used MathConstants to access properties and methods.