Asp.net C#
Posted February 12th, 2008 at 12:10 PM by alexgeek
I've been using PHP for ages and then slightly after that I started learning C# for desktop applications.
Recently I've tried ASP.NET (C#) and I happy to say that I quite like it!
With PHP I'd put all my code into objects for easy access etc., but accessing these classes would mean putting an include at the top of every page or specifying the magic __autoload() function... it was okay but it was.. time consuming.
In ASP.NET I just put my classes in the App_Data folder and I can access them from all pages, simpler than a bunch of includes.
With PHP to put some configurations in I'd have to put them in an include file also, but I can even say a connection string in web.config that can be accessed by all pages. Likewise web.config has many more options to control than htaccess.
And I can use all the .NET stuff, so XML parsing and reading is a blast.
PHP is better in many ways though because it's easier! That may not be a valid excuse but it is.
If you get something wrong with PHP, you can configure your page to not display any errors and carry on. In ASP.NET you have to try{}..catch{} everything otherwise... big ugly red and white page telling you of an error. But still, despite you being more prone to errors you will rarely mispell or mistakedly capitalize a class or variable name as while you type a list of all classes and variables will appear in a box in Visual Web Developer.
And as always the problem with .NET is that arrays have to be a fixed length, you can't just keep adding to them like you can in PHP.
ASP.NET also provides many more features like web services which are brilliant if you want to add a desktop application to your sites features.
PHP also offers this but you it's a lot harder.
I could go on but you get the picture.
Recently I've tried ASP.NET (C#) and I happy to say that I quite like it!
With PHP I'd put all my code into objects for easy access etc., but accessing these classes would mean putting an include at the top of every page or specifying the magic __autoload() function... it was okay but it was.. time consuming.
In ASP.NET I just put my classes in the App_Data folder and I can access them from all pages, simpler than a bunch of includes.
With PHP to put some configurations in I'd have to put them in an include file also, but I can even say a connection string in web.config that can be accessed by all pages. Likewise web.config has many more options to control than htaccess.
And I can use all the .NET stuff, so XML parsing and reading is a blast.
PHP is better in many ways though because it's easier! That may not be a valid excuse but it is.
If you get something wrong with PHP, you can configure your page to not display any errors and carry on. In ASP.NET you have to try{}..catch{} everything otherwise... big ugly red and white page telling you of an error. But still, despite you being more prone to errors you will rarely mispell or mistakedly capitalize a class or variable name as while you type a list of all classes and variables will appear in a box in Visual Web Developer.
And as always the problem with .NET is that arrays have to be a fixed length, you can't just keep adding to them like you can in PHP.
ASP.NET also provides many more features like web services which are brilliant if you want to add a desktop application to your sites features.
PHP also offers this but you it's a lot harder.
I could go on but you get the picture.
Total Comments 1
Comments
|
|
I find php includes easy
|
Posted February 12th, 2008 at 01:17 PM by simonb
|
Recent Blog Entries by alexgeek
- 3D Chess in your browser! (March 14th, 2008)
- Asp.net C# (February 12th, 2008)
- Social Networking & Dating sites (February 7th, 2008)
- Why shouldn't I use PHP short tags? (January 30th, 2008)
- Ajax (January 12th, 2008)
iEntry 10th Anniversary
Announcements










