C#

Ennis Ray Lynch, Jr. wrote:

I often refactor many of my lambda expressions into real code

Member 4487083 wrote:

the old fashioned way will almost always be more readable

PIEBALDconsult wrote:

B<layer>ut I suppose it's similar to using a Regular Expression rather than writing a custom parser. Or even like including SQL in your code rather than calling an API of some sort.

Member 4487083 wrote:

When (if ever) should we use Lambdas?

Member 4487083 wrote:

and performs MUCH better, so why use LINQ to SQL?

List<string> claData = new List<string>();

claData.Add("Test1");
claData.Add("Test2");
claData.Add("etc.");

specs.cla = claData.ToArray();

specs.clas[0] = "some text"

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
namespace Computer_Specs
{
    class Computer
    {
        private string _Brand;
        private int _RAM;
        private string _cpuBrand;
        private float _cpuSpeed;
        private string _operatingSystem;
        //Array
        private string[] _clArray;
        public string brand
        {
            get { return this._Brand; }
            set { this._Brand = value; }
        }
        public int ram
        {
            get { return this._RAM; }
            set { this._RAM = value; }
        }
        public string cpuBrand
        {
            get { return this._cpuBrand; }
            set { this._cpuBrand = value; }
        }
        public float cpuSpeed
        {
            get { return this._cpuSpeed; }
            set { this._cpuSpeed = value; }
        }
        public string os
        {
            get { return this._operatingSystem; }
            set { this._operatingSystem = value; }
        }
        //Array
        public string[] cla
        {
            get { return this._clArray; }
            set { this._clArray = value; }
        }
    }
}

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
namespace Computer_Specs
{
    public partial class Form1 : Form
    {
        public Form1()
        {
            InitializeComponent();
        }
        private void button1_Click(object sender, EventArgs e)
        {
            string nl = Environment.NewLine;
            Computer specs = new Computer();
            
            tbLog.Text = specs.brand = tbBrand.Text + nl;
            tbLog.Text = tbLog.Text + (specs.ram = int.Parse(tbRAM.Text)) + nl;
            tbLog.Text = tbLog.Text + (specs.cpuBrand = tbcpuBrand.Text) + nl;
            tbLog.Text = tbLog.Text + (specs.cpuSpeed = float.Parse(tbCPUSpeed.Text)) + nl;
            tbLog.Text = tbLog.Text + (specs.os = tbOS.Text) + nl + nl;
            List<string> claData = new List<string>();
            int loopY = 0;
            while (loopY < 5)
            {
                claData.Add(loopY.ToString());
                loopY++;
            } specs.cla = claData.ToArray();
            int loopX = 0;
            while (loopX < 5)
            {
                tbLog.Text = tbLog.Text + specs.cla[loopX] + nl;
                loopX++;
            }
            
        }
    }
}

Dell
2
AMD
2.61
Windows XP
0
1
2
3
4

string[] _clArray;

public string[] Cla
{
    get { return this._clArray; }
    private set { this._clArray = value; }
}

lukeer wrote:

Is there a way to load the "old" assembly into memory

jschell wrote:

Yes. Use an app domain.

jschell wrote:

But what happens in 2 years when you now have 5 versions?

jschell wrote:

have a migration tool that runs independently

jschell wrote:

determine what version the data is

lukeer wrote:

The problem here is that if Formatter.Deserialize() fails, the
serialized version number is as inaccessible as all the other saved data.