mpc tool improvement

[kurtcz]

Make the mpc tool more useful:

1. It should take an assembly (or a set of assemblies) rather than a csproj as an input and

2. it should also be able to pick up classes decorated with [DataContract] and [DataMember] attributes.

That way I could create resolvers/formatters for an entire assembly which may itself contain decorated classes declared from multiple projects. It would also allow for creating resolvers/formatters without having an access to the source code. These attributes are commonly used.

[neuecc]

First, the assembly base is easier to implement.
However, for several reasons, we use source code base analysis.

• Make it possible to generate even incomplete (including errors) source code
• Make it possible to generate directory-based files that do not have csproj such as Unity.
• I want to avoid double maintenance

[DataContract] may be supported in option.

[kurtcz]

Thanks for your comments. On the other hand source level forces you to generate one resolver per csproj. Perhaps it could support both modes?

• Are you saying I can just dump all files into one directory and then run the tool over that without a csproj file? Can you share an example of this please?
• Is the DataContract supported as an option today? Which switch do I need to use? Or you would include that optionally in the future?

Thanks for your comments!

[neuecc]

new version(WIP) of mpc supports that without a csproj file.
#396

DataContract support is the future.

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.