Added strong-typed request token message to sample.

This proves that messages can be derived from and tailored to provide type-safe additions where the OAuth protocol permits it.
As can be seen, several more types and members had to be made public for this to work.

1 files changed, 20 insertions, 0 deletions

diff --git a/samples/ServiceProvider/App_Code/RequestScopedTokenMessage.cs b/samples/ServiceProvider/App_Code/RequestScopedTokenMessage.cs
new file mode 100644
index 0000000..e8dbdeb
--- /dev/null
+++ b/samples/ServiceProvider/App_Code/RequestScopedTokenMessage.cs
@@ -0,0 +1,20 @@
+using DotNetOAuth.Messages;

+using DotNetOAuth.Messaging;

+

+/// <summary>

+/// A custom web app version of the message sent to request an unauthorized token.

+/// </summary>

+public class RequestScopedTokenMessage : RequestTokenMessage {

+	/// <summary>

+	/// Initializes a new instance of the <see cref="RequestScopedTokenMessage"/> class.

+	/// </summary>

+	/// <param name="endpoint">The endpoint that will receive the message.</param>

+	public RequestScopedTokenMessage(MessageReceivingEndpoint endpoint) : base(endpoint) {

+	}

+

+	/// <summary>

+	/// Gets or sets the scope of the access being requested.

+	/// </summary>

+	[MessagePart("scope", IsRequired = true)]

+	public string Scope { get; set; }

+}