Rich client options

Most of our HealthVault documentation on samples focuses on building web applications but you can also use HealthVault with your rich client application.  We support two high-level approaches to doing this: Intermediate web app With this approach, your rich client application communicates with a web service that you develop.  That web service, in turn, communicates…

0

ActionUrl, Privacy and Terms of Use

As many of you know, the HealthVault platform asks each application to register a single ActionUrl that understands a variety of redirect targets.  These redirects are generally used in scenarios where the application first redirects to the HealthVault Shell in order to accomplish some platformy task like App AuthZ or Record Picker and then the…

0

Absolute URLs for NonProductionActionUrlRedirectOverride

Our sample HealthVault applications in our HealthVault SDK all use relative paths for their NonProductionActionUrlRedirectOverride, but we have added support for absolute paths as well.  The “redirect” parameter in web.config now supports either a relative path or an absolute path. <add key="NonProductionActionUrlRedirectOverride" value="http://www.example.com/blah/Redirect.aspx"/> Just like with relative URLs, this is only supported in non-Production environments.

0

Creating your own ApplicationId and certificates

The Microsoft HealthVault SDK comes with a few sample applications and ApplicationIds which you can use in order to explore the platform and even to get started on your own application.  But at some point in your application development process, you will want to customize your ApplicationName and Logo.  You may also want to use…

0