Jquery tab postback

Question!

I am using jquery remote tab with asp.net to load my .aspx pages.The problem is if suppose i have a main page called "Parent.aspx" which contains the jquery tab and child page "Page1.aspx" which is loaded via remote tab into the "Parent.aspx".When i click on a server side button on my Page1.aspx, the whole window redirects to the Page1.aspx.I want it to remain on the Paernt.aspx itself.

My Code:

$(function() {
      $('#divEmployee').tabs(1, { remote: true });
 });

should i add some thing to this, to acheive the above mentioned functionality

Please help.Thanks

By : dr. evil


Answers

Straight from the how to section of the jQuery Tabs documentation.

Open links in the current tab instead of leaving the page

$('#example').tabs({
    load: function(event, ui) {
        $('a', ui.panel).click(function() {
            $(ui.panel).load(this.href);
            return false;
        });
    }
});


The difference between:

using (var scope = new TransactionScope(TransactionScopeOption.RequiresNew))

and

using (var scope = new TransactionScope())

Is that the second one reuse the existing (ambient) transaction, whereas the first one creates a new transaction within an old one.

This transaction within a transaction requires the Distributed Transaction Coordinator.

There are then three probable reasons for your error:

  • The MSDTC is not running
  • Your database is on a different machine and windows is configured not to allow transactions from the network.
  • Your database is on a different machine and SQL server is configured not to allow transactions from the network


I believe what is happening when the error occurs is that the framework is trying to promote the original "lightweight" (i.e. DBMS) transaction to a "distributed" transaction. The MSDTC (Distributed Transaction Coordinator) service, which manages distributed transactions, is either not running or is otherwise not able to work.

This typically happens when one logical transaction spans two (or more) database connections. Of course, in your case there is (apparently) only one DBMS connection. I'm guessing by forcing a new, independent transaction scope you are also forcing the framework to use a distributed transaction.



This video can help you solving your question :)
By: admin