Repository navigation
Packaging & redistribution of mdoc.exe & mono-symbolicate in a .NET 6 world? #35852
Description
In Xamarin.Android 10.5 and previous releases, Xamarin.Android redistributes mdoc.exe and mono-symbolicate.exe -- along with other assemblies -- which come from a "mono archive."
These utilities are used from various targets, e.g. from the BuildDocumentation target in Xamarin.Android.Bindings.targets or the SignAndroidPackage target in Xamarin.Android.Common.targets.
In a .NET 5 world, where should these utilities reside? Should they continue to be distributed as part of Xamarin.Andrdoid/Microsoft.Android? Should they be part of dotnet itself? Some other NuGet package?
Activity
jonpryor commentedon May 5, 2020
@steveisok: Thoughts?
jonathanpeppers commentedon May 5, 2020
A few more of these:
I don't know how many of these will be relevant going forward, though.
steveisok commentedon May 5, 2020
Good question. It's something I'll bring up in our next stand up.
jonpryor commentedon May 5, 2020
mono-api-htmlandmono-api-infowere previously used for xamarin-android's API compatibility checks. They should no longer be necessary.We've agreed that we can drop
mkbundlesupport for .NET 5, at least momentarily, so that's not a concern.cil-strip.exewill likely be "folded" into thedotnet build/dotnet publishinfrastructure, as part of AOT/etc. It may not need to be used directly from Xamarin.Android.aprofutil.exeandillinkanalyzer.exeare intended for "end-developer use", to view profiler output and analyze linker behavior. They don't need to be part of Xamarin.Android per-se, but they need to be present somewhere. Perhaps they should becomedotnet tools?[build] enable more One .NET MSBuild tests (#4820)
CoffeeFlux commentedon Sep 29, 2020
While not pressing, netcore
mkbundlesupport might be nice at some point just for the purpose of trying to reproduce Blazor-related issues outside of the browser and to generally be more confident in our single-file functionality. cc: @lambdageekmarek-safar commentedon Sep 30, 2020
There is already single-file like support in .NET 3.1 and .NET 5.0. Maybe it can be redesign for the 3rd time to support all .NET scenarios in .NET 6.0
/cc @agocke
[-]Packaging & redistribution of mdoc.exe & mono-symbolicate in a .NET 5 world?[/-][+]Packaging & redistribution of mdoc.exe & mono-symbolicate in a .NET 6 world?[/+][xabt] remove `<CreateMsymManifest/>` MSBuild task & `$(MonoSymbolArc…
dotnet-policy-service commentedon Oct 29, 2025
Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.
This process is part of our issue cleanup automation.
dotnet-policy-service commentedon Nov 13, 2025
This issue will now be closed since it had been marked
no-recent-activitybut received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.