DataModel doesn't work with Transfer

[jberkovitch]

I found out that DataModel doesn't work, when I use the transfer mode for my pages. In this case the data has not been saved. Only if I use the redirect mode, the data which I marked as DataModel is saved for this page. Can someone tell, why?

[Aleks Seovic]

Sorry it took so long, I just started going through the list of posts to close all of the minor issues up and realized I never responded to this post.

The reason is that Transfer method, as I believe you pointed out in another post, throws ThreadAbortException, so the code that should execute after it, including the code that saves the data model, never gets executed.

- Aleks

[angryrobot]

Aleks,

Is this possible to fix, or not, due to the .NET design? Transfer is preferable to redirect for all the reasons outlined in your docs, but not if DataModel can't work when you SetResult() in an event handler. I would think this is a common way to use both features.

-Dave

[Aleks Seovic]

Hi Dave,

As Microsoft would say "it's not a bug, it's a feature" ;)

Personally, I think that using exceptions to control application flow is a code smell, but in this case there is nothing we can do to fix the problem as ASP.NET relies on that ThreadAbortException being thrown.

That said, the whole discussion is quickly becoming irrelevant, as 1.1 P3 will not have DataModel attribute, which is gonna be replaced with a much better state management mechanism that won't suffer from this problem.

Regards,

Aleks

[angryrobot]

Aleks,

That's great...thanks. I can't wait to see it all come together!

-Dave