search

mamift / LinqToXsdCore

LinqToXsd ported to .NET Core (targets .NET Standard 2 for generated code and .NET Core 3.1, .NET 5+ for the code generator CLI tool).
Microsoft Public License
44 stars 15 forks source link

Fix content model and enum related bugs. #36

Closed rvuistin closed 2 years ago

rvuistin commented 2 years ago

I have added some unit tests in ContentModelCodeGenTests, ContentModelRuntimeTests and EnumsCodeGenTest

All tests are green and the code generated for a custom application which contains very complex schemas is now functional.

mamift commented 2 years ago

Hello, are you able to increment the version number in LinqToXsd/LinqToXsd.csproj?

rvuistin commented 2 years ago

Hi Muhamamd, I'm still working on some enum issues. I hope to finish today. I will increment the versions (XObjectsCore is concerned too) when I finish. Roger

mamift commented 2 years ago

Ok sure.

rvuistin commented 2 years ago

Hi Muhammad,

That’s it for now. The version (3.2.2) is now centralized in the Version.props file for all projects (see my last commit)

Some stuff to review...

rvuistin commented 2 years ago

The build scripts needed a refresh. It’s done.

The LinqToXsd tool is now ready to be migrated to net6...

mamift commented 2 years ago

I'm happy with the changes. Ready to merge?

rvuistin commented 2 years ago

I have changed the vmImage to windows-2022 in the azure-pipelines.yml to support .NET6 but the check still fails. Do you understand what's wrong with it ? I've never used azure pipelines before...

rvuistin commented 2 years ago

I'm happy with the changes. Ready to merge?

Other than that azure pipelines thing, yeah.

mamift commented 2 years ago

I was able to fix the pipeline issue, but was unable to run another rerun of the PR check for some reason.