-
-
Notifications
You must be signed in to change notification settings - Fork 677
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
mpc tool improvement #554
Comments
First, the assembly base is easier to implement.
|
Thanks for your comments. On the other hand source level forces you to generate one resolver per csproj. Perhaps it could support both modes?
Thanks for your comments! |
new version(WIP) of mpc supports that without a csproj file. DataContract support is the future. |
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. |
Make the
mpc
tool more useful:It should take an assembly (or a set of assemblies) rather than a csproj as an input and
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.
The text was updated successfully, but these errors were encountered: