"oldbear" wrote:

> Hi
>
> If this was a web service, you'd have access to WSE, which would do most of
> the work for you. However, as this is an ASP.Net app, it's a bit more tricky.
> You'll need something client-side to do the signing for you.
>
> A primary requirement here is to determine which types of client will be
> accessing your application.
>
> Often, this is achieved using a Java applet, as this gives greater
> cross-platform compatibility. However, this greater compatibility is not as
> easy as simply using Java applets.
>
> If it's only aimed at Internet Explorer on Windows, then you're able to
> create a much richer client by placing code in a control that can be loaded
> into the browser. However, this component may be restricted from accessing
> all of the resources necessary because of Code Access Security.
>
> If you're using more recent versions of Windows (XP, 2003, 2000) then you
> could consider the Smart Client technologies, such as a ClickOnce forms
> application that calls a web service. This would allow digital signatures to
> be created on the client, files to be accessed etc., and then the Smart
> Client could send the information vai a web service. ClickOnce would also
> take care of Code Access Security restrictions.
>
> Hope this helps
>
> Chris Seary
>
>