The extra time you put into your resume to find the errors is really what I'm looking for and what I'm calling to question here. If someone doesn't care to take the time to review their resume thoroughly prior to submitting it for employment, why should I think they would do any different when they complete a development task? Thanks for your reply.

Yea, I have seen this too. Seems like many of the agencies like to put their 'branding' into the CV. Pretty lame when they modify experience with the intent exaggerate a candidates abilities.

I couldn't agree with you more. If I see SQL Management Enterprise when someone claims to be an expert in SQL Server 2000 I have to question the integrity of their statement.

These are my thoughts as well. Thanks for confirming.

With so many candidates on the market looking for work, it seems like first impressions would be of the utmost importance. Yet, I still am receiving resumes with numerous typos. I take these typos very seriously when considering a potential employee/contractor given the fact I may either have to maintain, modify, fix code they have written at some point. Am I over reacting?

We use XXCopy to replicate data across WAN with relatively good perf as well as some nice features like directory synchronization, etc... Good luck

Sorry, I misread the first time.... Since those fields are readonly in addition to your list, you need to set them in the a constructor of the frog struct. You might try adding something like the following to your frog struct. public frog(int legs, int eyes) { this.legs = legs; this.eyes = eyes; } so your entire program would look like.... public struct foo { public readonly List<frog> al; public struct frog { public frog(int eyes, int legs) { this.eyes = eyes; this.legs = legs; } public readonly int legs; public readonly int eyes; } public foo(int unususedInt) { al = new List<frog>(); al.Add(new frog(2, 2)); } } Hope that solves your prob. Sorry it took me twice to get the problem. :)

JoeRip wrote:

public foo(int unususedInt) { al = new List{{frog}}(); frog myFrog = new frog(); myFrog.legs = 2; myFrog.eyes = 2; al.Add(myFrog); }

It looks like you have the legs and eyes fields on your struct set as readonly. I doubt the error you're encountering is being generated from writing to the list, but instead setting the properties on the frog instance. Hope this helps.