1. Choose the right data storage device
Do not use XML files as the sole data storage device, for XML files are not ideal for constant data operations (delete, insert, update).
Do not use Access database, because a. Access Database is not suitable for multiple concurrent users; b. Access database is not scalable.
SQL server is a preferred database choice for most .NET developers, for the powerful support provided by VS studio, high performance, scalability and a wide range of tools in database administration.
2. Dataset or custom data providers
DataSets is essentially a detached mini-database, it carries with it considerable overhead. With a typed dataset, every bit of change of the database schema means it has to be rebuilt.
On the other hand, custom data providers are more flexible and elegant. But it takes more time to design and code.
3. Stored procedures or ad-hoc text queries
Most literature I read prefer stored procedure for faster execution. Personally I like text queries, for its flexibility and nimblnes.
4. Do cache data for better performance
This has been stressed across all website building textbooks. ASP .NET 2.0 has also enhanced the Cache class.
5. Store connection strings and other settings in one single file, eg., web.config for .net applications.
...
All the above is culled from the book "ASP .NET 2.0 Website Programming: Problem - Design - Solution" by Marco Bellinaso, they may have been twisted unwittingly by me.
Have not blogged for a long long while. A busy crazy schedule and the flurry of holidays were among the things to blame.
Now back to work / blogging.
Now everyone goes to multimedia. My little company is not immune to the trend, so they charged me with the mighty task. The requirements are: a. within a reasonable budget; b. quality video/audio streaming, reasonably stable and fast; c. cannot have YouTube sticking its square fat brand on our proud web site (
http://www.mcic.org)
Sure. Sure. I agree.
After some quick googling, I found that there is an online battle of life-or-death-or-rebirth between Adobe Flash and the new-born Microsoft Silverlight. I also read that in the ever expanding varacious online world, Silverlight is soundly beat by Adobe Flash.
I agree. My experience with YouTube has been smooth and pleasant. I knew nothing about Silverlight. I agreed even more after the disastrous experience with Silverlight two days ago.
Two days ago, all news agency reported Bill Gates' keynote speech in CES and the comic video slip where he and a great celebrities stared. So I went to the Silverlight website and tried to watch the video.
What a disaster!
First they asked me to download Silverligt 1.0. But what? I have downloaded already. No, they said, not Silverlight 1.1, but 1.0. They threw me the error message (seen in the screenshot):
(I am suspicious of any downloading and installation request. Now they asked me to download, install then uninstall then download again. Outragious)
However, my desire to see the video was such so I followed the instructions.
I did this and that, uninstalled and reinstalled, clicked through. I thought I finally could have a laugh at Bill Gates. But no, the website had to load and buffer the videos. Gush, and for so long! Then when it finally played, it played badly. It started, then stopped, then started again ... Bill Gates' wrinkly face was so often frozen in place ...
In the end I had to watch the video using Windows Media Player locally.
...
However, being a staunch Microsoft user, tomorrow I still will shush my complaints and learn SilverLight. I hope I can write about my learning experience.