Member Avatar for Rach68

Hi,

I'm putting together a social networking site. One web developer is recommending going with them and using ASP.NET 3.0 and another is wanting to use PHP. I'm trying to find out which is better and what the difference is.

For example, will one affect the ease of use by us and the users, a hosting platform and adding on additional features at a later date versus the other.

Any feedback comparing the two, would be extremely helpful.

Thanks

  • 4 Contributors
  • 4 Replies
  • 209 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by Fungus1487

Dani AI

Generated

Quick clarification for : the phrase "ASP.NET 3.0" is ambiguous. Microsoft shipped .NET Framework 3.0 (WPF/WCF/WF) in 2006; ASP.NET is the web layer that runs on the .NET Framework, and the classic (pre‑Core) ASP.NET was tied to Windows/IIS. That Windows tie affected hosting and tooling choices at the time. (learn.microsoft.com)

Practical ecosystem differences (then and now): PHP commonly runs on the LAMP stack and is available on very low‑cost shared or VPS hosts, which makes spinning up an MVP quick. There are turnkey social engines and plugins (Elgg, WordPress + BuddyPress) that cut development time for community sites. Classic ASP.NET offered tight Visual Studio tooling and Windows integration but historically needed Windows hosting. (digitalocean.com)

Performance and long‑term direction: well‑written applications in either stack scale. Modern ASP.NET Core is cross‑platform and cloud‑optimized, and independent benchmarks show it among the high‑performance platforms—so raw speed is more about architecture than language choice. For maintainability and ecosystem, prefer actively supported, modern frameworks (ASP.NET Core for C# teams; Laravel or similar for PHP). (dotnet.microsoft.com)

Quick decision checklist (practical, short): match the stack to existing developer skills; if rapid, low‑cost launch is the goal, leverage PHP + off‑the‑shelf social packages; if the project needs deep Windows/enterprise integration or the team prefers C#, use ASP.NET Core today rather than legacy .NET; always budget for security, backups and horizontal scaling. The points raised by , and (community modules, coding/optimization, and personal preference) are all valid inputs into that checklist.

Recommended Answers

All 4 Replies

Member Avatar for peter_budo

I would go with PHP as it is community driven development and as it goes most of things will be free and coming numerous varieties where in ASP you more likely to end up paying for this or that. Secondly I find ASP slower in comparison to PHP or JSP.

Member Avatar for Fungus1487

Secondly I find ASP slower in comparison to PHP or JSP.

Alot of people throw this quote about but there is no reason ASP.net websites shouldn't be as fast (or faster) than php sites. It simply comes down to coding practices and optomizing performance.

I would consider what level of interaction/features your users will require. As persoannyl i find it easier to build a "Richer" interfcae using .Net rather than PHP. But again there is no reason why this should be the case. But i do agree with peter_budo...

I would go with PHP as it is community driven

that a social networking site would more than likely work best in a community driven environment

Member Avatar for omol

At the moment i would go with php purley because of the huge scale asprox botnet.

Also, call me crazy but i prefer to code in php.

Member Avatar for Fungus1487

Also, call me crazy but i prefer to code in php.

your crazy :P

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.