Wednesday, June 30, 2004
Wednesday, June 23, 2004
Online .NET books
Here is the List of some of the very useful Books which contains lot of useful study material for Free. (Updated Links)
Here is the List of some of the very useful Books which contains lot of useful study material for Free. (Updated Links)
Tuesday, June 22, 2004
Monday, June 21, 2004
Async-Up Your Objects
Encapsulate asynchronous functionality directly into your business objects. The .NET Framework facilitates calling object methods asynchronously through the use of delegates. You may already know how to do this using helper code, but there is a cleaner and much cooler way of packaging this kind of functionality right inside your business objects.
by Miguel A. Castro
Encapsulate asynchronous functionality directly into your business objects. The .NET Framework facilitates calling object methods asynchronously through the use of delegates. You may already know how to do this using helper code, but there is a cleaner and much cooler way of packaging this kind of functionality right inside your business objects.
by Miguel A. Castro
Friday, June 18, 2004
You should use stored procedures instead of embedded SQL statements for a number of reasons:
Stored procedures generally result in improved performance because the database can optimize the data access plan used by the procedure and cache it for subsequent reuse.
Stored procedures can be individually secured within the database. A client can be granted permissions to execute a stored procedure without having any permissions on the underlying tables.
Stored procedures result in easier maintenance because it is generally easier to modify a stored procedure than it is to change a hard-coded SQL statement within a deployed component.
Stored procedures add an extra level of abstraction from the underlying database schema. The client of the stored procedure is isolated from the implementation details of the stored procedure and from the underlying schema.
Stored procedures can reduce network traffic, because SQL statements can be executed in batches rather than sending multiple requests from the client.
Stored procedures generally result in improved performance because the database can optimize the data access plan used by the procedure and cache it for subsequent reuse.
Stored procedures can be individually secured within the database. A client can be granted permissions to execute a stored procedure without having any permissions on the underlying tables.
Stored procedures result in easier maintenance because it is generally easier to modify a stored procedure than it is to change a hard-coded SQL statement within a deployed component.
Stored procedures add an extra level of abstraction from the underlying database schema. The client of the stored procedure is isolated from the implementation details of the stored procedure and from the underlying schema.
Stored procedures can reduce network traffic, because SQL statements can be executed in batches rather than sending multiple requests from the client.
Thursday, June 17, 2004
Thursday, June 10, 2004
Understanding ASP.NET View State
Summary: Scott Mitchell looks at the benefits of and confusion around View State in Microsoft® ASP.NET. In addition, he shows you how you can interpret (and protect) the data stored in View State
Summary: Scott Mitchell looks at the benefits of and confusion around View State in Microsoft® ASP.NET. In addition, he shows you how you can interpret (and protect) the data stored in View State
Wednesday, June 02, 2004
Business Patterns for Software Engineering Use, Part 1
Philip Teale
Microsoft Corporation
Defines business patterns in a way that is useful for software developers, and develops a business patterns framework using the Strategic Architecture Model.
Philip Teale
Microsoft Corporation
Defines business patterns in a way that is useful for software developers, and develops a business patterns framework using the Strategic Architecture Model.
