We have serveral options for error logging in ASP.NET MVC application:
– ELMAH for error logging
– log4net
– NLog
The most common complaint against NoSQL is that if you know how to write good SQL queries then SQL works fine. If SQL is slow you can always tune it and make it faster. A NoSQLite might counter that this is what key-value database is for. All that data could have been retrieved in one get, no tuning, problem solved. The counter is then you lose all the benefits of a relational database and it can be shown that the original was fast enough and could be made very fast through a simple turning process, so there is no reason to go NoSQL.
Read more about StackOverflow experience to make slow pages 100x faster by simple SQL tuning
Web Services are the key point of Integration for different applications belonging to different Platforms, Languages, systems.
Web services are set of platform independent exposed APIs(functions) which can be used used from remote server over the Internet. There are basically two parties involved in this, one which provides a set of exposed APIs and the another one ,commonly know as web services consumers,is the party which uses the functionality and services provided by web services providing party.
There are different method for providing web services but the most common are SOAP, XML-RPC and REST .
Stack Overflow opens sources of their ASP.NET MVC mini profiler. It is a simple but effective mini-profiler for ASP.NET MVC.
The sources can be found here – http://code.google.com/p/mvc-mini-profiler/.
Find W3C recommendations here – http://www.w3.org/TR/CSS2/
“Final Release to Web (RTW) of Microsoft ADO.NET Entity Framework 4.1 (EF 4.1). This is a fully supported, go-live release.” – said ADO.NET team on April, 2011.