.NET/C# Incompatibles with clients

[Logician]

I am developing a large website (million pages) and I decided to drop
most of the HTML I have been using and implementing mostly a .NET
solution supported by C# as the language.

Coding is about 90 times easier than using CSS and HTML and a real
relief after struggling style sheets, but I am a little worried that
not all clients will read the pages OK.

Does anyone have any experience of writing systems which use little
HTML, eg instead of using <li> just use a ListBox which is much
easier?

The trend seemed to be for a while using large client scripts to
handle screen functions, but I have always found server side code much
easier.

 

[Jon Skeet [C# MVP]]

I am developing a large website (million pages) and I decided to drop
most of the HTML I have been using and implementing mostly a .NET
solution supported by C# as the language.

Coding is about 90 times easier than using CSS and HTML and a real
relief after struggling style sheets, but I am a little worried that
not all clients will read the pages OK.

Why? Look at the HTML which is generated by your code. It's not like
the clients will see your ASPX - they'll only see the result. You're
still using HTML really, and you *should* still be using CSS too.

You don't *have* to use AJAX, although the client experience will be
better (for the vast majority of clients) if you do so - sensibly!

 

[Arne Vajhøj]

I am developing a large website (million pages) and I decided to drop
most of the HTML I have been using and implementing mostly a .NET
solution supported by C# as the language.

Coding is about 90 times easier than using CSS and HTML and a real
relief after struggling style sheets, but I am a little worried that
not all clients will read the pages OK.

Does anyone have any experience of writing systems which use little
HTML, eg instead of using <li> just use a ListBox which is much
easier?

The trend seemed to be for a while using large client scripts to
handle screen functions, but I have always found server side code much
easier.

I don't understand your post.

Are you changing a web app to a desktop app ?

Because an ASP.NET web app are still generating HTML, CSS and
JavaScript.

Arne

 

[Family Tree Mike]

One million pages at one per minute of coding gives you eight years of work
(assuming 40 hour work weeks).

I suspect there will be a few more technologies come out in that time
period...