-
-
Notifications
You must be signed in to change notification settings - Fork 710
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 not parsing MessagePackObject contained in .Net Core class library projects correctly #42
Comments
Feels similar to #23 |
@Rurouni Agree. Just wonder if the author has any workarounds in mind though. |
Thank you. |
support for mono, set Environment path, it works for new csproj, etc. |
related to #188 and close(discussion move). |
Use agent jobname for for symbols folder
I tried to use mpc to generate resolvers for some of my classes marked with MessagePackObject attribute from a .Net Core class library project.
However, GeneratedResolverGetFormatterHelper.GetFormatter(Type) in the resulting file only contains an empty switch statement which is different from what I got by generating from a ,Net console application project.
When I built mpc from source and attached a debugger to it, I found that when generating from a .net Core class library project, it throws an exception. The exception indicates the constructor parameter is empty for MessagePackObjectAttribute and KeyAttribute when supplying with a csproj file from a .net Core class library project.
It looks like Roslyn fails to parse those construct parameters in this case.
Is there something you could do fix it? Thanks!
The text was updated successfully, but these errors were encountered: