Errors building fhir-net-api in VS 2015

[as...@yahoo.com]

I downloaded the FHIR .NET API source tree from GitHub today and attempted to load the Hl7.Fhir.sln solution into VS 2015.  The load failed with the following errors - am I missing something obvious?

C:\fhir-net-api-master\src\Hl7.Fhir.Core\Hl7.Fhir.Core.csproj : error  : The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.  C:\fhir-net-api-master\src\Hl7.Fhir.Core\Hl7.Fhir.Core.csproj

C:\fhir-net-api-master\src\Hl7.Fhir.Core.Tests\Hl7.Fhir.Core.Tests.csproj : error  : The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.  C:\fhir-net-api-master\src\Hl7.Fhir.Core.Tests\Hl7.Fhir.Core.Tests.csproj

C:\fhir-net-api-master\src\Hl7.Fhir.Specification\Hl7.Fhir.Specification.csproj : error  : The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.  C:\fhir-net-api-master\src\Hl7.Fhir.Specification\Hl7.Fhir.Specification.csproj

C:\fhir-net-api-master\src\Hl7.Fhir.Specification.Tests\Hl7.Fhir.Specification.Tests.csproj : error  : The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.  C:\fhir-net-api-master\src\Hl7.Fhir.Specification.Tests\Hl7.Fhir.Specification.Tests.csproj

C:\fhir-net-api-master\src\Hl7.Fhir.Support\Hl7.Fhir.Support.csproj : error  : The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.  C:\fhir-net-api-master\src\Hl7.Fhir.Support\Hl7.Fhir.Support.csproj

C:\fhir-net-api-master\src\Hl7.FhirPath\Hl7.FhirPath.csproj : error  : The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.  C:\fhir-net-api-master\src\Hl7.FhirPath\Hl7.FhirPath.csproj

C:\fhir-net-api-master\src\Hl7.FhirPath.Tests\HL7.FhirPath.Tests.csproj : error  : The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.  C:\fhir-net-api-master\src\Hl7.FhirPath.Tests\HL7.FhirPath.Tests.csproj

C:\fhir-net-api-master\src\Hl7.Fhir.Support.Tests\Hl7.Fhir.Support.Tests.csproj : error  : The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.  C:\fhir-net-api-master\src\Hl7.Fhir.Support.Tests\Hl7.Fhir.Support.Tests.csproj

[Brian Postlethwaite]

You need to have VS 2017 to build it and produce the assemblies / NuGet packages, as there are .net core packages included.
The output you can then use with VS2015, which you can get from NuGet without needing to build it yourself.

[as...@yahoo.com]

Thanks.

[as...@yahoo.com]

Brian - per your guidance, I installed VS 2017 Professional and downloaded fhir-net-api-0.94.0-stu3.zip from GitHub.  I opened the solution and attempted a Rebuild All.  1626 errors occurred.  Package Manager appears to have restored all NuGet packages.

I've attached a file containing all the errors.  Most of the errors seem to be due to a fundamental mis-configuration.

Is there something else I need to do to prepare the build environment in order to successfully build the API?

[Brian Postlethwaite]

Hoping you grabbed the appropriate branch, did you just build it again?did you also install the dotnetcore libs/options in VS?
Looks like might be missing that too.

[as...@yahoo.com]

Many thanks for the fast reply.  I attempted the build several times with the same results.

When I installed VS 2017, I installed several of the Windows "workload" options, including most, if not all, of the .NET Framework ones.  Are there specific workloads I should install?

I've posted a screenshot of my installed workloads.  Let me know if one is missing.

[Brian Postlethwaite]

The netcore at the end is required to build too.

[as...@yahoo.com]

Thanks again.  I'll modify the installation and retry the build.

[as...@yahoo.com]

Applied the last workload and still no success.  I've attached two additional screenshots showing the netstandard1.0 and netstandard1.3 contexts possibly being the problem?

The third screenshot shows the .NET Desktop Development workload settings.

[as...@yahoo.com]

As follow-up, I was able to resolve the build issues.  Strangely, I had to build the Hl7.Fhir.Core project first, followed by Rebuild Solution.  Thanks for the assistance.

[Brian Postlethwaite]

Glad it's now working.
I'm wondering what you're wanting to change that has you building it rather than just using the NuGet packages, and also if it's seeing that you'd be happy to continue back to the library.

Rewards
Brian

[as...@yahoo.com]

Hi Brian - I'm investigating if the model classes (generated and otherwise) are compatible with an Entity Framework code first implementation and allow for the EF to generate a relational schema.

[Brian Postlethwaite]

You're welcome to give it a whirl, but I'm pretty sure you'll find that it won't work like that.
The main issue you'll find is that the EF wants to create fixed tables in the database and the FHIR model has extensibilty built in, so it can't support those extensible bits.
You will need to choose how you want your server to handle this.
My server stores the fhir content as XML and has some other metadata to assist with searching and indexing. Bit this is a choice you'll need to make.
If you have a static schema, with a fixed set of identified extensions, then you could create those tables.
My server uses T4 templates to generate the ef schema reflecting on the fhir models in this assembly.

Hope this info helps you understand some issues that you'll find.

[as...@yahoo.com]

Interesting.  It sounds like your server works very similarly to the HAPI JPA Server which I've worked a bit with recently.

We're exploring how to relationally express parts of the FHIR XSD in order to support a data warehouse implementation.  The HAPI JPA Server is currently covering us on the OLTP side, but we'll need an OLAP solution for data analysis.  We're willing to forgo parts of the FHIR definition in the XSD (i.e., extensibility) in order to create the relational model.  We're starting with a fixed number of FHIR resources to support for data analysis.

To clarify, are you saying that Entity Framework-based schema is already being generated by T4 templates acting on the generated model classes?

[Brian Postlethwaite]

Yes, it is Similar t the HAPI approach.

I'd actually suggest using a profile (structure definition) as the basis for defining your model instead of the c# model.
This will then mean you can define the extensions you want, and the properties you don't want.

In my fork of the library there is a project Hl7.Fhir.QuestionnaireServices that has some functionality that might help.

[as...@yahoo.com]

I see several forks under your username at GitHub.  Which one would have QuestionnaireServices?

[Brian Postlethwaite]

https://github.com/brianpos/fhir-net-api/tree/feature/structure-tree-stu3/src/Hl7.Fhir.Questionnaire
There is a dstu2 branch there too.