You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was recently upgrading MassTransit's referenced version of MessagePack to the latest major version, when I discovered some tests were failing for ONLY for.NET Framework 4.7.2, due to the following exception:
System.NotSupportedException: A non-collectible assembly may not reference a collectible assembly.
Upon some research I found the cause, which appeared to be a MassTransit generating dynamic assemblies that are collectible, while MessagePack's dynamic assemblies are non-collectible.
Please see my discussion for my MassTransit PR: MassTransit/MassTransit#5726
Additionally, I found an earlier issue for MessagePack involving the same issue for .NET 5, rather than .NET Framework 4.7.2: #1150.
The PR that resolved the mentioned issue only affects non-framework builds, so I am curious if there is a specific reason why the .NET Framework builds do not share the same AssemblyBuilderAccess flag.
With these changes, both MessagePack & MassTransit pass their respective tests, so I would love to hear your thoughts and concerns.
Since Save wasn't supported in .NET(Core) for a long time, I had only enabled it for .NET Framework.
However, now that .NET 9 finally supports Save, I'm actually thinking about switching to using Save. dotnet/runtime#15704
However, since this is for debugging purposes, and the demand has decreased significantly after migrating to Source Generator, it would be acceptable to change it to Collect.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi.
I was recently upgrading
MassTransit's referenced version ofMessagePackto the latest major version, when I discovered some tests were failing for ONLY for.NET Framework 4.7.2, due to the following exception:Upon some research I found the cause, which appeared to be a
MassTransitgenerating dynamic assemblies that are collectible, whileMessagePack's dynamic assemblies are non-collectible.Please see my discussion for my
MassTransitPR: MassTransit/MassTransit#5726Additionally, I found an earlier issue for
MessagePackinvolving the same issue for.NET 5, rather than.NET Framework 4.7.2: #1150.The PR that resolved the mentioned issue only affects non-framework builds, so I am curious if there is a specific reason why the
.NET Frameworkbuilds do not share the sameAssemblyBuilderAccessflag.With these changes, both
MessagePack&MassTransitpass their respective tests, so I would love to hear your thoughts and concerns.