Your opinion: Are CSS friendly Adapters dead in 2010?

Question

User-2115395994 posted

What do you think? Is it wise to start to use CSS Friendly adapters at this point (2010) with these observations in mind:

• VS2010 and .Net4 are coming and may offer something new
• MVC is an option if you really want to manage your page layout
• Microsoft is not involved with CSSFA
• The codeplex project seems to be sleeping along
• It's been 4 years since it started

 

Is there a better way to get control of the HTML emitted by ASP.Net controls? I for one  am fed up with wrestling with the failures of browsers to handle the table code properly (e.g. applying classes) yet I am fearful of going down the CSS road when it seems so stale. What do you think? Your recommendation?

Answer 1

User2130758966 posted

If you are going to convert your project to asp.net 4 then you wont need the css friendly adapters.

All asp.net webforms controls have been fully revised for 4 and support proper standards compliant tableless markup.

If your project is going to stay with an older version then you should still use the CSS adapters.

Answer 2

User-2115395994 posted

Thanks, that's fairly clear. Will there be an option to continue to use the old table style output? I ask because it would seem that projects would be difficult to upgrade (detailed examination of every page required, especially with regard to CSS?)

Answer 3

User2130758966 posted

Yes its an attribute that you add to turn on the css friendly formatting.

You can see some pretty detailed info on this at:

• http://www.asp.net/LEARN/whitepapers/aspnet4/default.aspx#_TOC3_11
  

Answer 4

User1988710134 posted

Can I have css friendly controls only with the 4.0 framework and visual studio 2008 or I must also use visual studio 2010?

Answer 5

User-142784633 posted

All asp.net webforms controls have been fully revised for 4 and support proper standards compliant tableless markup.

I fired up a .NET 4 web application with VS2010 and it seems to me (unless I did something wrong) that the Calendar control hasn't been touched at all (probably since it was written for 2.0 or even older versions). It still has hard-coded inline CSS calls and auto-postback Javascript that cannot be overwritten (in a few places). 

Am I missing something? Thanks.