Load Drop Down List using Javascript
About LINQ TO SQL
LINQ TO SQL
Linq-To-SQL is the lightweight,
straightforward, MS-SQL Server only technology
Advantages:
- Reduction in work, Faster development
- Strongly typed code (Type Safety).
- A common syntax for all data.
- Compile check when database changes
- Auto-generated domain objects that are usable small projects
- Lazy loading feature can speed up performance & at least simplify the code a lot.
- Debugging support
Disadvantages:
- Support for SQL Server only
- No direct execution against database
- Not suitable for handling large amount of data, like filling dataset.
Performance:
- Insert operations are better in LINQ, the read operation is superior in ADO. (http://www.codeproject.com/KB/linq/performance_comparisons.aspx)
- In some Real world comparison, it shows LINQ is much slower than the SqlDataReader (http://devtoolshed.com/content/performance-benchmarks-linq-vs-sqldatareader-dataset-linq-compiled-queries-part-2)
- While handling large amount of data, It is advisable to swap some linq queries with stored procedures or ADO.NET
Tags: Advantages of linq to sql, limitations linq to sql, linq to sql performance, about linq to sql
Exception Handling in Global.asax, Application_Error
Some of the Limitations of Exception Handling in Global.asax
(Application_Error)
- An error handler that is defined in the Global.asax file will only catch errors that occur during processing of requests by the ASP.NET runtime. For example, it will catch the error if a user requests an .aspx file that does not occur in your application. However, it does not catch the error if a user requests a nonexistent .htm file. For non-ASP.NET errors, you can create a custom handler in Internet Information Services (IIS). The custom handler will also not be called for server-level errors.
- You cannot directly output error information for requests from the Global.asax file; you must transfer control to another page, typically a Web Forms page. When transferring control to another page, use Transfer method. This preserves the current context so that you can get error information from the GetLastError method.
- Application_Error never fires for a web service.
- Application_Error will catch parser, compilation, and run-time errors within pages. It will not catch configuration issues, nor will it catch errors that occur within inetinfo while aspnet_isapi processes the request.
One of the biggest advantages
of Exception Handling in Global.asax (Application_Error)
- Good in Performance