Generated Struct Members Should be Marked "readonly"

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Accidently assign a value to Namespace.Columns.member
 ie. Query.WHERE(Namespace.Columns.Member = value)
    vs the proper Query.WHERE(Namespace.Columns.Member, value)

2. Run the project on IIS

3. It will blow up and continue to blow up until IIS is restarted.

What is the expected output? What do you see instead?

If the members were readonly then the compiler would stop it from 
continuing.  Instead the value was cached on IIS (I assume), had to 
restart the service.  Stopping/Starting the website didn't help, neither 
did restarting VS2005.

What version of the product are you using? On what operating system?

2.1 on XP.

Please provide any additional information below.

This is by no means a bug, just something that I can see a user friendly 
feature, as I assume most users won't be changing the struct member values 
at runtime.
(Sorry I posted this on codeplex as well...)

Original issue reported on code.google.com by hateonet...@gmail.com on 17 Jul 2008 at 8:35

[GoogleCodeExporter]

Original comment by canof...@gmail.com on 18 Jul 2008 at 9:58

• Changed title: Generated Struct Members Should be Marked "readonly"

[GoogleCodeExporter]

Original comment by canof...@gmail.com on 18 Jul 2008 at 9:59

• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by canof...@gmail.com on 18 Jul 2008 at 9:59

• Changed state: Started

[GoogleCodeExporter]

Fixed in Revision 474.

Original comment by canof...@gmail.com on 18 Jul 2008 at 10:07

• Changed state: Fixed

[GoogleCodeExporter]

thanks for getting this fixed.

Original comment by hateonet...@gmail.com on 21 Jul 2008 at 2:34