Hi,

 when you set [assembly: System.CLSCompliant(true)] in the assemblyinfo.cs, you get a warning for every "_UpToTable1ByFieldx" identifier.

It is possible to avoid this by setting the attribute [CLSCompliant(false)] for every field starting with underscore but that means editing in the generated files. Is it possible to change the naming in MyGeneration? I don´t really like getting about 50 warnings everytime :)

 
Joris
 

I will take a look at this, thanx, we're cutting our July 9th release this weekend, I'll see if I can get rid of all these for you.

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

I'm now having the opposite problem:

[CLSCompliant(false)] is causing the following warning everywhere it appears in my classes (63 warnings):  Warning 4 'EntitySpaces.ClassName._UpToClassName2ById' does not need a CLSCompliant attribute because the assembly does not have a CLSCompliant attribute

I managed to work around this by adding: [assembly: CLSCompliant(false)] to my assembly.

There probably should be an option in MyGeneration to skip CLSCompliance entirely for those of us not writing CLSCompliant code.  I'm thinking that should probably be the default actually.

Yes, I didn't realize that until after release, that is the danger of doing a last minute enhancement, something we will be very careful of in the future, the next version will come with a checkbox for that. Sorry about that, adding the assembly attribute however does get rid of it, assuming of course you don't have other violations laying around in the code.

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

agree..

Ya, we are either going to make this a conditional or remove it, I agree, it caused more problems than it solved.

---

EntitySpaces | Twitter | BLOG | Please honor our Software License