Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

System.Transactions and Allow Inbound/Outbound DTC Settings

If you do distributed transactions across the network, you know about Allow Inbound and Allow Outbound security settings for DTC (available by running dcomcnfg or by opening Component Services). The help describes these settings as: Allow Inbound: Select

Intro for Microsoft Azure .Net Service Bus

Clemens Vasters gives a great introduction to Microsoft Azure .Net Service Bus and its 4 feature areas: Naming, Registry, Connectivity, and Eventing. Find it at http://vasters.com/clemensv/PermaLink,guid,92d78bee-2cfd-4a29-95ab-c5abb9b905e7.aspx
Posted by florinlazar | 1 Comments

Atbroker.exe application error - CTRL-ALT-END in a remote session

I use remote desktop daily. The Atbroker.exe application error followed by black screen seemed to be gone for a while. Now it is back. The only solution that I know of and which works most of the times is "CTRL-ALT-END" (the equivalent of “CTRL-ALT-DEL”
Posted by florinlazar | 1 Comments

When not to use transactions and where you can't use transactions

Transactions are great when everyone plays in. You group a set of activities together under a transaction and you start executing them. If anything bad happens along the way or something doesn't go as planned, invoke rollback and all is taking care of

MSDTC and COM+ Configuration Tool in Vista

To access the MSDTC and COM+ configuration tool in Windows Vista, also known as Component Services MMC, you have the following options: 1. Run “dcomcnfg” 2. Or run: %SystemRoot%\System32\comexp.msc 3. Or if you prefer, you can add a shortcut to %SystemRoot%\System32\comexp.msc
Posted by florinlazar | 0 Comments
Filed under:

Exception Handling without catch(Exception)

The design guidelines for exception handling are quite clear on avoiding “catch all” and/or avoiding catching exceptions you can’t handle. But there are cases when you really need to know if the try block completed successfully or not, and possibly take
Posted by florinlazar | 2 Comments
Filed under:

Working with CMD and Long Path Names

I like using the command prompt for a lot of things and working with long (or very long) path names is something that is common these days. Fortunately, you can customize cmd by using "prompt". Do a “prompt /?” in a command window to see all the options.
Posted by florinlazar | 0 Comments
Filed under:

How to Use System.Data with System.Transactions and Maintain Atomicity and Data Consistency

The Bug I call it a bug. Initially I was persuaded to believe it was a feature; later I was "convinced" that it is now a matter of app compat and it can't be changed anymore. Let’s look at the following code: SqlConnection connection1 = new SqlConnection(connectionString);
Posted by florinlazar | 4 Comments

Limitation of TransactionScope (and using)

If you read the documentation for TransactionScope , you will find: "If no exception occurs within the transaction scope […], then the transaction in which the scope participates is allowed to proceed. If an exception does occur within the transaction
Posted by florinlazar | 0 Comments
Filed under: ,

Avoiding Transaction Promotion with Multiple Connections - Improvements in System.Data and SQL Server 2008

Great news! The new updates added to System.Data and SQL Server 2008 finally allow multiple Open/Close connections to the same SQL Server without promoting the transaction to MSDTC. This was by far the most requested feature for the System.Transactions/System.Data/SQL

A Simpler TransactionScope

In .Net 3.5 I can write a transactional code block as follows: transacted(()=> { using (SqlConnection connection = new SqlConnection(connectionString)) { connection.Open(); SqlCommand command1 = new SqlCommand(commandString1, connection); command1.ExecuteNonQuery();
Posted by florinlazar | 3 Comments
Filed under:

Flowing or propagating transactions in .Net

System.Transactions transactions are bounded to the appdomain. Which means that if you make in-appdomain calls from inside a TransactionScope, those calls will share the transaction. This also means that if you need to make a call outside the current

TIP is now deprecated

TIP is getting deprecated - see the note at http://msdn2.microsoft.com/en-us/library/ms679484(VS.85).aspx If the native OleTx protocol used by MSDTC and System.Transactions is not friendly enough for your firewall, you should consider the WS-AtomicTransactions
Posted by florinlazar | 0 Comments
Filed under:

MSDN Magazine Article on Transactional File System

Jason Olson describes the Transactional NTFS and how you can take advantage of it in your applications: http://msdn.microsoft.com/msdnmag/issues/07/07/NTFS/default.aspx
Posted by florinlazar | 0 Comments
Filed under:

WCF in Romania

These days I'm in Romania with a tour at 3 universities (in Bucharest, Cluj and Iasi) talking about Windows Communication Foundation, distributed systems and web services. Adi Oltean is also talking about storage technologies in Windows. So far the seminars
Posted by florinlazar | 3 Comments
Filed under:
More Posts Next page »
 
Page view tracker