Which is best Asp.net, Php, Sharepoint?
Hey guys, yesterday I talked with one web programmer on web development he suggested me three unique programs for my website, 1. Asp.net 2. Php 3. Sharepoint
Well I am new and I don’t have any ideas, I just asked him what will be the best platform to use for my properties site, as I told him that I need to handle lots more database, he suggested me to opt for asp.net, he feels mysql is not much safe and not efficient to handle such huge database
I wana know from this community which in these three will be best, or is there anything new? I need your valuable suggestion..
Share: 
| df3728 wrote: |
| Hey guys, yesterday I talked with one web programmer on web development he suggested me three unique programs for my website, 1. Asp.net 2. Php 3. Sharepoint |
I don't know enough about sharepoint to give you a proper idea on that, but as I understand it, sharepoint is a specific product whereas the other two are development platforms where you would need to code up the website yourself.
PHP usually goes with MySQL but doesn't have to; similarly, you can presumably run asp.net with mysql if you wanted to. I'd therefore suggest that you decide which development platform and which database platform you want to use can be chosen (almost) independently.
It really rather depends on your skill set with PHP and/or .NET. Either can do the job for you...
Jack Pickard The Pickards Information Services| Blog | Twit
Share:
PHP + MySQL is what most are likely to say. I've been using .NET + MySQL (most folk would normally use MS SQL SERVER with .NET), as I needed some of the MS goodness (MS SAPI to be specific).
.NET really is a very good framework. You can code in C# or VB or if you're really adventurous unmanaged C++ which the links through COMs or other reference methods, but thats a pain.
Sharepoint has some issues re out the box accessibility (IMO). All of which (that I've seen) can be worked around.
Share:
Let's not forget that Perl 5 is still a valid choice 
Works well for me anyway!
And Perl 6 is on the way soon.
Accessify Forum Administrator ~ Nigel Peck / MIS Web Design
"Everything I say is not meant to be set in stone" - Van Morrison
Share:
I prefer Php as it is very easy to get started with it.
Share:
I prefer Java than any of these mentioned 
Remember however that PHP+MySQL is the system which is supported probably by the most of hosting vendors. Read about CMS using these tools: Drupal, Joomla and many other...
Share:
Until recently, I have worked with php and MySQL - and had little difficulty. More recently I have had to work with asp.net - and have been surprisingly impressed. It can produce clunky code, but there are techniques for improving that. The menu tool produces a rather dire table formatted menu - which looks fine, but compiles to awful coding. There are community produced CSS adapters, but they are rather clunky. I believe that problem will be solved when asp.net 4 comes out.
asp.net is a highly productive way of producing web sites - but does take quite a lot of learning. I have chosen to get going in Visual Basic - with hindsight I might have gone for C# - which seems a little more php like in its structure; rather more has to be defined in VB - and it seems to be a little less used, so fewer examples are produced in it - as far as I can see.
Microsoft Web Developer is surprisingly powerful, free, and well supported.
Share:
I have used all 3. Go with what the programmer feels most comfirtable with. PHP will be cheapest long term.Johan De Silva / Portfolio
Share:
i'm using php with mysql it is the best and the best part it is free and there are many opensource scripts that you can use
Share:
| kiwibrit wrote: |
| Microsoft Web Developer is surprisingly powerful, free, and well supported. |
The website for it uses tables for layout, some presentational markup and a Transitional doctype. But that might just be from the microsoft.com infrastructure.
What was your experience with it like? Does it take the model of Dreamweaver, or is more like a CMS?
Share:
Wow. It's a little hard to answer your questions, but here goes:
I am using Visual Web Developer 2008. It is a little like Dreamweaver, but I found I had to get into a completely different mindset, really. You call up what you want, using a wide variety of tools, and the system compiles your pages. And whilst the design page does sort of show you a layout - you definitely need to view the page in a browser - which is very easy to do. Right at the moment, my company has diverted me on to CAD chores, and development work on a couple of sites is just that - development, awaiting further work.
Here's one of the sites that is on a back burner
It uses xhtml transitional 1.0 because that is what the reference book I am learning from uses - but I think once I get to grips with it there should not be much problem switching to strict. I think html should also be possible. The biggest thing that concerns me is the menu coding. It is possible to get round that using CSS code adapters, but that is a bit of a dog's dinner - and anyway I gather the problem will disappear when asp.net 4 becomes available.
Share:
I have tried all 3. And i think Asp.net is best. It is working for me.
Share:
Taking the Microsoft route is incomprehensibly expensive, from the projects and estimates I've seen. Especially because you must spend so much time unpicking the trash it outputs by default.
If you start from scratch or with a standards-based, open-source platform, it's much more feasible and affordable to deliver great websites. The only problem is under-quoting the total project - you start to think every part is for free, but time is still money!
Share:
I have utilized all 3. Go with what the programmer feelings most comfortable with. PHP will be cheapest long condition.
Share:
I have developed a community application/site with asp.net and since the projects inception, I have learnt an awful lot regarding accessibility standars (an area i was largely ignoreant of before - unfortunatrly all to common in the developer world) - and though I love this technology (use of c#) there are certain accessibility problems built into the .net 2.0 environment.
Watch out for server controls that wire in javascript postback calls and be aware that some design properties are also hardcoded into the resultant htm page (content and presentation should always be seperated with diligent use of css - not doing so is bad for seo and a pain for screen readers).
Check out the css friendly adapters, but note that they are not provided for all controls (calander The control does not render a header in columns). I haven't had time to check out .net 4.
Share: