>> What steps will reproduce the problem?
1. Use a sample that uses AspNetOAuthRequest and SessionRequestStateStore
2. Set the ASP.NET web.config to use SQLServer session state. (StateServer is
also likely to have the same problem.)
3. Run the sample. At some point when AspNetOAuthRequest wants to store
request tokens in the session, the site will crash.
>> What is the expected output? What do you see instead?
- I expected it to work. Instead, I saw an exception from ASP.NET that
specific classes from OAuth.Net weren't serializable.
>> What version of the product are you using? On what operating system?
- OAuth.Net v0.8.1.1 on Windows Server 2008 R2 with SQL Server 2008 R2 for
session state storage.
>> Please provide any additional information below.
- Modifying the following two classes to have the [Serializable] attribute
fixed the problem for me:
OAuth.Net.Consumer.RequestState
OAuth.Net.Consumer.RequestStateKey
I notice that OAuthToken was already marked [Serializable], so perhaps on these
other classes lack of such was an oversight? I suggest a future build ensure
compatibility with out-of-process session state - such is common in web farm
deployment scenarios.
BTW, thanks for software! Other than this problem that I've worked around,
everything else so far worked as expected.
Original issue reported on code.google.com by chris.w....@gmail.com on 11 Aug 2010 at 1:00
Original issue reported on code.google.com by
chris.w....@gmail.com
on 11 Aug 2010 at 1:00