Search

Transaction behavior regarding WF by Leandro Faria

Resolved
as By Design Help for as By Design

4
0
Sign in
to vote
Type: Bug
ID: 778730
Opened: 2/7/2013 4:44:42 AM
Access Restriction: Public
1
Workaround(s)
0
User(s) can reproduce this bug
If i open a transaction outside of the workflow and flow it into the workflow no matter what the transaction always come out aborted
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Example already implemented supplied

Product Language

English

Operating System

Windows Server 2008 R2 SP1

Operating System Language

English

Actual results

Transaction always come out of the workflow aborted

Expected results

Transaction come out as it went in (alive)
File Attachments
File Name Submitted By Submitted On File Size  
TransactedReceiveTest.rar 2/7/2013 77 KB
Sign in to post a comment.
Posted by Microsoft on 5/15/2013 at 2:27 PM
Thank you for passing along this issue to us. We evaluate all the feedback our customers submit, but unfortunately we cannot fix every item that comes in. We have evaluated the issue you submitted, and at this point, we do not anticipate releasing an update for it. If the issue is blocking you from using the product, please contact our support via the Visual Studio Help and Support (http://msdn.microsoft.com/en-us/vstudio/cc136615.aspx) page on MSDN. Also, make sure to take a look at the Workaround supplied by Rafael.
Posted by Microsoft on 2/7/2013 at 8:50 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 2/7/2013 at 4:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Posted by Leonardo A L Ferreira on 2/7/2013 at 4:49 AM
Having the same issue here...
Sign in to post a workaround.
Posted by Rafael Bertholdo on 2/7/2013 at 5:29 AM
I was having the same issue then i removed the "Persist Before Send" from the send reply you provided and it worked