Some ideas * Designer designer - illustrator, photoshop etc idea --> image / pdf * Web designer - html, css; idea --> markup OR image / pdf --> markup (a .NET webdesigner could use the right controls directly, --> skins, themes asp:controls) - Use MS cssadapters - Use MS Css Properties addin (more like expression web and "orcas") both can be found at www.asp.net (downloads) * web developer - html, css --> skins, themes and asp:net-controls With good co-development and the right controls for the job, there are plenty of possibilites to work in paralell. some notes: - use markup when no need for dynamic server behavior meaning stop useing

Heard of Refactor from devexpress? http://www.devexpress.com/Products/NET/IDETools/Refactor/ [Free versions] Refactor!™ for Visual Basic® .NET 2005 http://www.devexpress.com/Products/NET/IDETools/VBRefactor/ Refactor!™ for ASP.NET http://www.devexpress.com/Products/NET/IDETools/RefactorASP/ Refactor!™ for C++ http://www.devexpress.com/Products/NET/IDETools/RefactorCPP/

If it works for you then it's not wrong for you (but perhaps for the wider audience). Personally as stated before I think the m adds nothing. consider mAge _age with how reading letter work. The human mind skims quickly through text not reading character by character but rather ses the "image" of the word; therefore the m also disturbs the quick skimming and readability of the code. For more info on the subject see: http://www.microsoft.com/typography/ctfonts/WordRecognition.aspx#m1 Finally A good source (with comments, arguments) for naming convention: http://www.irritatedvowel.com/Programming/Standards.aspx

I Like them! :rose: Why? I'm a VB.NET developer... to write none language dependent code is like coding to interfaces instead of implementations ;P What do I mean? Well to easily convert / write / use code from BOTH c# and VB.Net "_" simplifies a great bit... Mainly because vb.net is not case sensitive. I find the "_" char the least disturbing in reading / skimming through code. The m_ prefix i dislike the m_ prefix as I consider it outdated; as far as I know the m stands for member, and if I want to now a class member I take a look in the Object browser, or use the "Me" (this in c#) ex: Me._myFieldName therefore in my opinion -> m_ adds "nothing". As the previous post states, the _ is used for private members and therefore encapsulated by the class and you work with the public properties / methods instead i.o.w not that big of a problem (in my humble opinion) in contrast to language independence.