Skip to content

FhirStarter STU3 is updated with different type of logging

Compare
Choose a tag to compare
@verzada verzada released this 03 Oct 10:04
· 24 commits to master since this release

The logging has changed with this version of FhirStarter.STU3 and the framework has also been updated to 4.6.2
The log can now catch requests to the FhirService which should make it easier to debug faulty requests.

This release requires the following packages to work:

FhirStarter.Bonfire.STU3 - 0.9.35 - https://www.nuget.org/packages/FhirStarter.Bonfire.STU3/0.9.35
FhirStarter.Flare.STU3 - 0.9.36 - https://www.nuget.org/packages/FhirStarter.Flare.STU3/0.9.36
Fhirstarter.Spark.Engine.STU3 - 0.9.6 - https://www.nuget.org/packages/FhirStarter.Spark.Engine.STU3/0.9.6

Log4Net and AppSettings configuration

To see an example how to configure the log, take a look at the
https://github.com/verzada/FhirStarter.STU3/blob/master/src/FHIRStarter.Inferno.Template/Web.config

The AppSettings key
<add key="LogRequestWhenError" value="true"/>
enables logging for requests when exceptions or error occurs

The Log4net entry in the web.config has been routed to a separate log4net.config file
https://github.com/verzada/FhirStarter.STU3/blob/master/src/FHIRStarter.Inferno.Template/log4net.config
to make it easier to override the settings during deployment.

FAQ

I can't make my Fhir Service work after the update

Make sure you have upgraded the framework from 4.5* to 4.6.2

The references does not work when I start the IIS service

Copy the contents of the runtime tag from the template web.config
https://github.com/verzada/FhirStarter.STU3/blob/master/src/FHIRStarter.Inferno.Template/Web.config
and add it to your web.config file.

Check that the packages.config file from https://github.com/verzada/FhirStarter.STU3/blob/master/src/FHIRStarter.Inferno.Template/packages.config has the same main libraries as your service. The Hl7.Fhir packages are especially sensitive to changes, not mention to the third party packages which ninject uses.