Skip to main content

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest



Serializable allows one transaction to complete before the other start.

SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server.

Using TransactionScope Object:

A transaction can’t span multiple connections.
 



Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +.

In 2.X and later use TransactionScope object.




Serializable allows one transaction to complete before the other start.

SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server.

Using TransactionScope Object:



Dispoase of the transaction must be called to complete the transaction.

Distributed Transaction:
 


All object can be enlisted within transaction which implement ITransaction interface.

Storing and retrieving CLR types:
 






Using SqlNotificationRequest:


Enable Notification System on Sql Server 2005.
ALTER DATABASE AdventureWorks SET ENABLE_BROKER;
Setup Database:
CREATE QUEUE ContactChangeMessages;

CREATE SERVICE ContactChangeNotifications
 ON QUEUE ContactChangeMessages
([http://schemas.microsoft.com/SQL/Notifications/PostQueryNotification]);
private void Listen()
{
    using (SqlCommand command =
        new SqlCommand("WAITFOR (RECEIVE * FROM ContactChangeMessages);", connection))
    {
     // Make sure we don't time out before the
    // notification request times out.
       if (connection.State != ConnectionState.Open)
        {
            connection.Open();
        }

        command.CommandTimeout = NotificationTimeout + 120;

        AsyncCallback callBack = new AsyncCallback(
            this.OnReaderComplete);
        IAsyncResult asynResult = command.BeginExecuteReader(
            callBack, command);
        if (asynResult.IsCompleted == true)
        {
            waitInProgress = true;
        }
    }
}
private void OnReaderComplete(IAsyncResult asynResult)
{
                SqlDataReader reader = ((SqlCommand)asynResult.AsyncState)
                .EndExecuteReader(asynResult);
            while (reader.Read())
            // Empty queue of messages.
            // Application logic could partse
            // the queue data to determine why things.
            {
                for (int i = 0; i <= reader.FieldCount - 1; i++)
                    Debug.WriteLine(reader[i].ToString());
            }

            reader.Close();
}



Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...

Concept of App Domain in .Net

Creating Application Domains: Application domain is just like process, provides separate memory space, and isolates from other code. But it’s quite light weight. It also provides the following advantages: 1-       Reliability : If a domain crashes, it can be unloaded. Hence doesn’t affect the other assemblies. 2-       Efficiency : Loading all assemblies in one domain can be cumbersome and can make the process heavy but Appdomains are efficient in this manner. Important properties of AppDomain: ApplicationIdentity , ApplicationTrust , BaseDirectory , CurrentDomain , DomainManager , DomainDirectory , Evidence , FriendlyName , ID , RelativeSearchPath , SetupInformation , ShadowCopyFiles . Important methods of AppDomain: ApplyPolicy , CreateCOMInstanceFrom , CreateDomain , CreateInstance (Assembly). To create an AppDomain: AppDomain adomain = AppDomain.CreateDomain(“D”); To execute an assembly:...

ASP.NET Working With Data-Bound Web Server Controls

Suppose we have: List<Car> vCars = new List<Car>(); There are three types of databound controls: Simple databound controls(List, AdRotater), Composite data bound controls(GridView, DetailsView, FormView that inherit from CompositeDataBoundControl), and Hierarchal data bound controls (TreeView, Menu).   DataBoundControl has a DataBind method that can be used when data is ready. It calls DataBind for child controls as well. Page.DataBind() will call DataBind for all child controls. Using DataSource Objects:                                       BaseDataBound control exposes DataSource property that accepts objects that implement IEnumerable , IListSource , IDataSource , or IHierarchalDataSource . DataSourceID accepts ID of SqlDataSource . If both specified Data...