Web Best Practice - HTML rendering from c#, vb.net into ASPx or php?
Hi Experts,
I am interested in some resources and ideas on what is the best method in web 2.0 and 3.0 coming up for building tight well organised, css based sites of the future.
Facebook is written in PHP with a MySql backed.
Traditionally I am a Microsoft programmer knowing c#, vb.net and asp/ asp.net.
However the controls and asp ajax tend to be clunky, heavy on HTML encoding and slow in general. I have been using DotNetNuke as a CMS, but I am loving Wordpress at the moment.
Should I learn PHP and MySQL and go the Open Source way, or should I learn how to program using C#, without using ASP (just rendering HTML)
What methods are used for PHP rendering - from what I can tell in the Wordpress world it is pretty much writing the HTML as needed like in classic asp days.
What is the best practices for HTML rendering these days?
What is the best most efficient language to use to build a database driven content managed system?
Is LINQ better than SP and MySQL? Faster?
I am interested in some resources and ideas on what is the best method in web 2.0 and 3.0 coming up for building tight well organised, css based sites of the future.
Facebook is written in PHP with a MySql backed.
Traditionally I am a Microsoft programmer knowing c#, vb.net and asp/ asp.net.
However the controls and asp ajax tend to be clunky, heavy on HTML encoding and slow in general. I have been using DotNetNuke as a CMS, but I am loving Wordpress at the moment.
Should I learn PHP and MySQL and go the Open Source way, or should I learn how to program using C#, without using ASP (just rendering HTML)
What methods are used for PHP rendering - from what I can tell in the Wordpress world it is pretty much writing the HTML as needed like in classic asp days.
What is the best practices for HTML rendering these days?
What is the best most efficient language to use to build a database driven content managed system?
Is LINQ better than SP and MySQL? Faster?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
> Asp.Net does dump some fairly heafty HTML, but that's part of the nature of how it handles its state information.
Actually it is "webforms" that does that, and it is easy to avoid webforms with asp.net. Just don't use the <form runat=server> thing. That of course cancels also many other things that come with webforms, but it keeps the HTML code clean and keeps the sever-side part understandable.
Actually it is "webforms" that does that, and it is easy to avoid webforms with asp.net. Just don't use the <form runat=server> thing. That of course cancels also many other things that come with webforms, but it keeps the HTML code clean and keeps the sever-side part understandable.
ASKER
Thanks for all the info!
I think I am going to use c# and MSSQL or MySQL as the backend and only XHTML/Ajax/Javascript as the front end, no aspx controls at all.
I have used DotNetNuke as a CMS in the past, but I think it is to cumbersome for something as simple as this, so I will be looking for another one so I don't have to reinvent the wheel.
I think I am going to use c# and MSSQL or MySQL as the backend and only XHTML/Ajax/Javascript as the front end, no aspx controls at all.
I have used DotNetNuke as a CMS in the past, but I think it is to cumbersome for something as simple as this, so I will be looking for another one so I don't have to reinvent the wheel.
ASKER
Thanks for the reply.
I haven't looked at MVC at all yet - bit behind on the MS coding front I guess as worked in Corporate mostly - so generally a few years behind the 8 ball... haha
I will investigate - any articles you recommend reading to start?
Does MVC3 output a stack of rubbish HTML to the client as @wwwdeveloper2 suggests these programs do.
I have felt a little limited by ASP.net as at the end of the day HTML is output, and Javascript is still by far the best client side scripting language - especially with the libraries that are available now.
As for comparing LINQ with the others - it was more the fact that you are writing the queries directly in the code, so how does the speed of querying compare to PHP methods I guess at the end of the day... I have found that LINQ is definitely faster than SP/MSSQL combinations - I haven't used LINQ to connect to anything but SQL Server mind.
wwwdeveloper2:
I have found PHP to be fairly easy to learn yes - as a programmer it is pretty simple to pick up another language and start to work with it, and there are stacks of examples out there too, which makes life lots easier. As to methodology - the first method you mentioned is the one I used in classic ASP and PHP - I just wonder if that is considered the best method considering the massive amounts of options out there.... And I often wonder about the article I read once that if Facebook was written in c# it would be 40% more efficient.
I wonder what the likes of the below best of web2.0 sites are written in.
http://basecamphq.com/
http://www.stumbleupon.com/
http://www.ning.com/
http://www.netvibes.com/en