-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix content model and enum related bugs. #36
Conversation
Hello, are you able to increment the version number in LinqToXsd/LinqToXsd.csproj? |
Hi Muhamamd, |
Ok sure. |
- skip schemas which trigger exceptions during code generation. - skip schemas which generate erros during compilation.
- use Directory.Build.props and Version.props to share project information. - disable nuget package generation in debug mode.
Hi Muhammad, That’s it for now. Some stuff to review... |
- remove redundant or unused code. - centralize documentation management. - hide additional documentation warnings. - fix ambigous documentation cref.
The build scripts needed a refresh. It’s done.
The LinqToXsd tool is now ready to be migrated to |
I'm happy with the changes. Ready to merge? |
I have changed the |
Other than that azure pipelines thing, yeah. |
I was able to fix the pipeline issue, but was unable to run another rerun of the PR check for some reason. |
.NET 6
I have added some unit tests in
ContentModelCodeGenTests
,ContentModelRuntimeTests
andEnumsCodeGenTest
All tests are green and the code generated for a custom application which contains very complex schemas is now functional.