Welcome to WebmasterWorld Guest from 220.127.116.11
Forum Moderators: ocean10000
I have plans to develop further applications in this website to make more use of databases (with multiple users, reading / writing frequently).
I am stuck up with following Qs?
1) I have heard that asp.net is better than asp for future. So, should i migrate now. Will it be worth the hard work of designing so many pages
2) Should i migrate from MS acess to Mysql or some other database , capable of handling more requests or having more speed (pages loading quickly)
3) Should i shift to PHP (i am a novice in it, but if the work is worth it, then i am willing to learn and do it all)
4) Should i go for some portal applications like dotnetnuke / phpnuke or stick to my individual page designing process [This because, i am concerned with data backup issue.]
5) Is it easy to backup mysql db? Should i split my db to several mini dbs?
Any advice is appreciated.
Your problem is the database. you can't use Access as a database/server. That is why your pages are slow. Pretty soon your website will just stop loading at all. That is something you need to migrate from. mySQL is a good choice and it is easy to back up.
I wouldn't bother with any of the templates if you already have thousands of pages.
if anything, I'd try to find a way to reduce the number of pages, and make it more dynamic.
Thousands of pages are there but the site is dynamic in the sense that -
1) under the main folder there are many subfolders.
2) for most of the subfolders, i have customized include header and footer files.
3) for sub subfolders, i have customized include header and footer files for many of the pages.
But i cannot update all the include header and footer templates together as for each folder they are different and usually are based on other include files, so changing one will result in improper working of one or more unknown folder.
However, i have taken up the task of making more generic includes , so that i have to do less of a redesign if i need it in future (But the hard fact is , by the time one learns something right/new, he/she has already created a lot of pages, and reduplication of effort is tiring.)
Thanks for the suggestion. Any more comments are welcome, and very much appreciated.
I am hooked on ASP.NET. I have mixed in some old style ASP pages on some of my newer .NET sites with no problem. I'll get around to updating all the pages to .NET someday.
Thanks for the reply And correctly pointing out that both asp and aspx pages can be run simultaneouly.
I am not going to update all old asp pages with aspx right now. Will do them gradually.
Right now the problem is - i have a new website project. Which language do i choose - PHP / PERL / ASP.NET (considering heavy site traffic, future support and updates in the language)
Every language has its champions who will testify that it is the best. Like I said, I'm hooked on .NET. I use VB and C#, I can also use C++ or any other language I want to for a particular project. The whole architecture and object structure suits me fine. Once I got used to it I just fell into the groove. So much better than the old ASP.
If you are a C++ or VB or even a Java programmer, then .NET will immediately make sense and be easy. It has some quirks and pitfalls, but it is my favorite.
Probably this is the security hole that you are talking about "The latest ASP.NET vulnerability is due to a canonicalization error within the .NET authentication schema" (got it from net).
I will keep it in mind. Thanks again.
... google will never (?) penalise/inflate a site based on the technology of the server.
but does the same apply to microsoft? whose websearch will be bigger in the future than it is now.
despite the claims of the linux guys, i think asp.net is fantastic, additionally imho ms-sqlserver is superior to mysql - the one drawback is that in a cheap hosting environment ms is more expensive, but if you get very busy the extra cost is trivial.
I've not heard the linux folks trashing .NET. I mostly just hear rants about Windows, and I can understand why.
I hear people saying that VB.NET and C# in are not true object oriented languages because they do not conform to strict definitions of inheritance and polymorphism. That's just academic bs in my opinion. I like .NET and plan to stay with it for a long time.