Stream: dotnet
Topic: STU3
Brian Postlethwaite (Jul 09 2016 at 07:43):
The https://github.com/ewoutkramer/fhir-net-api/tree/ft-connectathon-sept2016 branch has been updated with the current content (and 1.5 version number)
No Nuget package, so you'll need to build it yourself if you need it (and have a server to test it with)
Not all the STU3 changes are in here, just the model updates basically
Brian Postlethwaite (Jul 19 2016 at 10:56):
Just a note to all that if anyone wants to try out the new client and/or debug any issues with it once servers are available the code has been pushed to github (https://github.com/ewoutkramer/fhir-net-api/tree/ft-connectathon-sept2016)
Grahame Grieve (Jul 24 2016 at 12:12):
@Brian Postlethwaite - builid 9227 should be good for generating code from (after being broken for various reasons for a while) - can you test that for QA reasons please
Brian Postlethwaite (Jul 24 2016 at 12:13):
Sure.
Grahame Grieve (Jul 24 2016 at 12:13):
thx
Brian Postlethwaite (Jul 24 2016 at 22:38):
Current build generates ok. Won't do a commit till we're final unless needed.
Grahame Grieve (Jul 24 2016 at 22:56):
ok thanks. I guess the only need would be if people want to use my STU3 server, since that is rolling with the spec. but no one has asked me
Brian Postlethwaite (Jul 24 2016 at 23:04):
Is that what is live at http://fhir3.healthintersections.com.au/open
Grahame Grieve (Jul 24 2016 at 23:07):
yes. upgarding it now
Brian Postlethwaite (Jul 25 2016 at 00:46):
Your conformance statement still has the custom resource type in it. (so my test for conformance fails to de-serialize)
Brian Postlethwaite (Jul 25 2016 at 00:47):
(Maybe a better way of describing that now could be an extension on the basic resource)
Grahame Grieve (Jul 25 2016 at 00:50):
hmm I better get rid of that. next upgrade
Brian Postlethwaite (Jul 25 2016 at 01:00):
no problems.
Brian Postlethwaite (Jul 29 2016 at 13:24):
Hi all, I've pushed a new update with the final models generated into it a short time ago.
There isn't a Nuget package for this just yet, and the latest changes fro the develop branch aren't in there yet, but should serialize correctly.
Brian Postlethwaite (Aug 11 2016 at 06:04):
Hi all, the STU3 (1.6.0) source is ready on GitHub in the ft-sept2016-dev branch.
This will be built into a NuGet package soon and published as a pre-release package.
Peter Jordan (Aug 11 2016 at 22:34):
@Brian Postlethwaite What's the difference between the feature/ft-sept2016-dev and ft-connectathon-sept2016 branches? It looks as if they've both been updated at the same time.
Brian Postlethwaite (Aug 11 2016 at 22:43):
Right now nothing.
The one in the feature/ft-sept2016-dev is the development branh where new work is done before releasing to the ft-connectathon-sept2016 branch
Brian Postlethwaite (Aug 11 2016 at 22:43):
Extra validation using the fluentpath will appear in the feature/blah area soon while it is worked on.
Brian Postlethwaite (Sep 10 2016 at 11:56):
Announcing another release of the STU3 dotnet client.
This has all the current great work on validation and the current fluentpath integrated into it.
The NuGet package will be a following in a few days, but for those that want to get a heads up, source is available on GitHub in the ft-connectathon-sept2016 branch
Ewout Kramer (Sep 15 2016 at 11:20):
I just pushed the STU3 port of the .NET API to NuGet. As usual, to be able to find it, you have to allow NuGet to look for "prerelease" packages. The latest version is alpha7 now.
Angus Millar (Oct 31 2016 at 05:41):
Having a lot of trouble getting the latest nuget pakages to play ball with each other.
Angus Millar (Oct 31 2016 at 05:43):
It appears that the Hl7.Fhir.STU3 (0.90.6-alpha7) has a dependancy on the hl7.FluentPath which the nugget install does not know about. And even then when both of the latest pakages are inplace I get this error:
Angus Millar (Oct 31 2016 at 05:43):
Could not load type 'Hl7.ElementModel.IValueProvider' from assembly 'Hl7.FluentPath, Version=0.4.0.0, Culture=neutral, PublicKeyToken=d706911480550fc3'
Angus Millar (Oct 31 2016 at 05:44):
When trying to serialize i.e: string Resource = Hl7.Fhir.Serialization.FhirSerializer.SerializeResourceToXml(Ob, Hl7.Fhir.Rest.SummaryType.False);
Ewout Kramer (Oct 31 2016 at 10:10):
Yes, I failed to add a dependency from 0.90.6-alpha7 to fluentpath. And if you add that FP reference manually, you will be tempted to use the latest (0.4.0.0) version of fluentpath - which is not compatible with alpha7 of the .NET API. You could fix it by using a 0.3.x version of the FluentPath library. Did you try with 0.90.6-alpha8? That should have the correct dependency on a 0.3.x version of the fluentPath library.
Ewout Kramer (Oct 31 2016 at 10:10):
As well, I will soon post an alpha9 that should reference the newest 0.4.x FP.
Ewout Kramer (Oct 31 2016 at 10:11):
Sorry for the confusion - we're moving towards .NET core and I have to get used to the new tools and versioning process...
Ewout Kramer (Oct 31 2016 at 10:12):
Oh, I did not post an alpha8 for STU3. Right. so, that option is not there. Try to add a <0.4.0 reference to FP, that should work. Let me know how if the problems persist.
Angus Millar (Nov 01 2016 at 01:38):
Thanks Ewout
Angus Millar (Nov 03 2016 at 05:15):
Sorry Ewout but I can't find a way past this. You said "you will be tempted to use the latest (0.4.0.0) version of fluentpath - which is not compatible with alpha7 of the .NET API. You could fix it by using a 0.3.x version of the FluentPath library."
Angus Millar (Nov 03 2016 at 05:22):
I don't think I can fix it, I have reverted back to Hl7.fluentPath (0.3.1-alpha7) and continued to use hl7.Fhir.STU3 (0.90.6-alpha7). Yet I still get this error when trying to ‘Resource resource = FhirXmlParser.Parse<Resource>(XmlString);’
Error: Could not load file or assembly 'Hl7.FluentPath, Version=0.4.0.0, Culture=neutral, PublicKeyToken=d706911480550fc3' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
It appears that the dependency link is checked at a key level so I can’t hoodwink it. Maybe I can turn that off somehow in Visual Studio, will google to see if that is possible.
Angus Millar (Nov 03 2016 at 07:27):
OK I got it working, after much diging around. In the App.config file of my project I commented out this section:
<dependentAssembly>
<assemblyIdentity name="Hl7.FluentPath" publicKeyToken="d706911480550fc3" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-0.4.0.0" newVersion="0.4.0.0"/>
</dependentAssembly>
Angus Millar (Nov 03 2016 at 07:31):
I also then also needed Newtonsoft.Json (9.0.1) and it all worked again.
Michel Rutten (Nov 03 2016 at 08:39):
Sounds familiar. After updating the FHIR API .NET nuget package, sometimes I had to manually remove redirections from app.config in order to be able to build the solution. Not sure what causes these.
Ewout Kramer (Nov 03 2016 at 11:06):
<dependentAssembly>
<assemblyIdentity name="Hl7.FluentPath" publicKeyToken="d706911480550fc3" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-0.4.0.0" newVersion="0.4.0.0"/>
</dependentAssembly>
Bites me every time..
Ewout Kramer (Nov 03 2016 at 11:07):
I always check my git commit log and undo any changes to app.config like these....
Brian Postlethwaite (Nov 18 2016 at 11:05):
Those interested in trying out a FHIR dev STU3 branch, I have put a version that has almost all the current develop version of the DSTU2 libs build with the STU3 mods applied.
Source can be found here:
https://github.com/ewoutkramer/fhir-net-api/tree/ft-connectathon-jan2017
(There is no NuGet package at yet)
Brian Postlethwaite (Nov 18 2016 at 23:37):
And if you want to try out interacting with a server running that fhir client inside, mine is now up and going
http://sqlonfhir-stu3.azurewebsites.net/fhir/
Note that the terminology server functionality is pretty broken at the moment, and won't be fixed for a while
Brian Postlethwaite (Dec 06 2016 at 12:16):
Progress update on the dotnet client supporting the Jan 2017 connectathon build, there is now code up on GitHub that should support this build. I'm doing my own tests on this before we publish a NuGet package for it, but if anyone else wants to use it, please feel free to, and let us know if there are any issues.
https://github.com/ewoutkramer/fhir-net-api/tree/ft-connectathon-jan2017
Last updated: Apr 12 2022 at 19:14 UTC
