dnSpy VS Fody

dnSpy https://github.com/0xd4d/dnSpy

Protip: Use a debugger like dnSpy or Visual studio to trace the source of error, by stepping the program line by line. Inner exception callstack: No inner exception was thrownOuter exception callstack: at TaleWorlds.CampaignSystem.Actions.LeaveTroopsToSettlementAction.ApplyInternal(MobileParty mobileParty, Settlement settlement, Int32 numberOfTroopsWillBeLeft, Boolean archersAreHighPriority) at TaleWorlds.CampaignSystem.SandBox.CampaignBehaviors.GarrisonTroopsCampaignBehavior.OnSettlementEntered(MobileParty mobileParty, Settlement settlement, Hero hero) at TaleWorlds.CampaignSystem.MbEvent`3.InvokeList(EventHandlerRec`3 list, T1 t1, T2 t2, T3 t3) at TaleWorlds.CampaignSystem.CampaignEvents.OnSettlementEntered(MobileParty party, Settlement settlement, Hero hero) at TaleWorlds.CampaignSystem.CampaignEventDispatcher.OnSettlementEntered(MobileParty party, Settlement settlement, Hero hero) at TaleWorlds.CampaignSystem.Actions.EnterSettlementAction.ApplyInternal(Hero hero, MobileParty mobileParty, Settlement settlement, EnterSettlementDetail detail, Object subject, Boolean isPlayerInvolved) at TaleWorlds.CampaignSystem.Actions.EnterSettlementAction.ApplyForParty(MobileParty mobileParty, Settlement settlement) at TaleWorlds.CampaignSystem.Campaign.HandleSettlementEncounter(MobileParty attackerParty, Settlement settlement) at TaleWorlds.CampaignSystem.Campaign.HandleSettlementEncounter(MobileParty attackerParty, Settlement settlement) at TaleWorlds.CampaignSystem.Campaign.CheckSettlementEncounter(MobileParty mobileParty) at TaleWorlds.CampaignSystem.Campaign.HandleEncounters(Single dt) at TaleWorlds.CampaignSystem.Campaign.Tick(Single dt) at TaleWorlds.CampaignSystem.Campaign.RealTick(Single realDt) at TaleWorlds.CampaignSystem.MapState.OnMapModeTick(Single dt) at TaleWorlds.Core.GameStateManager.OnTick(Single dt) at TaleWorlds.Core.Game.OnTick(Single dt) at TaleWorlds.Core.GameManagerBase.OnTick(Single dt) at TaleWorlds.MountAndBlade.Module.OnApplicationTick_Patch2(Module this, Single dt) at TaleWorlds.DotNet.Managed.ApplicationTick_Patch2(Single dt)

While Fody works at binary (MSIL) level, Metalama Compiler is a fork of Roslyn and allows for AST transformations, at the C# level.

As an alternative to PostSharp you may take a look at Fody.

Working with IL weaving as part of the building process is quite complex though, and this is where Fody enters into the picture. Fody is an extensible tool that allows to simplify the weaving process by taking care of all the heavy lifting.

Fodyplugins can modify exists code during compilation.

I've seen coworkers using Fody for such MSIL weaving stuff, but I have a bad feeling about this. It's a little bit like jailbreaking your phone. Cool stuff ahead, but voids warranty.

Implement your own (in C++/outside dotnet/CLR) IHostAssemblyManager stuff, this is the "replace/bypass how assemblies are loaded" trick. There used to be a prebuilt thing on the old old codepages, but I can't find it. I wonder if newer code/assemblie weavers such as Fody can do the similar thing?

Great place to start is https://github.com/Fody/Fody and existing 'addins' - fody does it at compile time - generally quite useful for your own code if you want to dip into aspect oriented programming.