Generated code does not follow c# naming standards

[Manuel de la Peña]

The generated code does not follow naming standards. I'm sure there is no need to explain why this is bad.

[Manish Sinha (मनीष सिन्हा) (manishsinha)]

Manuel, You now have access to the trunk. Go ahead and merge the code. I am not sure if I have time now to review and merge it.

[Manuel de la Peña (mandel)]

Sweet, thanks A LOT. I suppose I should tell you what I suddenly started working on you project. I'm currently the person porting Ubuntu One to Windows. As you may know Canonical rolled out Ubuntu SSO that replaces Launchpad login and we require this to work on Windows.

So far you project has the best code I've seen so far on the WADL + C# real so I have started finding "bugs" (I think of them more as to do things) and trying to fix a long the way ;)

I really appreciate your help and the fact that you allow me to get to commit in trunk, thx!

[Manish Sinha (मनीष सिन्हा) (manishsinha)]

Yeah. From your LP page and your blog, I could make out that you are porting U1 on Windows.
Well, looking at a code/project from a critical angle can actually help a lot. I believe that constructive criticisms help a lot.

BTW there is one more project of mind called WadlAv [ https://launchpad.net/wadlav ] which actually takes the WADL and generates the assembly instead of code. It uses Reflection.Emit , but due to time constraints, I had to shelve it. It is halfway through. This means that every 2 weeks when LP API can change, the application can update itself if it can generate the new assembly from the fresh WADL.

You have access to WadlAv too (through the team cil-advancers)