Moq v5

[kzu]

Pendings:

• Interface proxies
• Abstract class proxies
• Allow customizing the proxy generation
• Consume the generator Sdk from Moq.Sdk to inject IMocked interface
• Override all virtual members
• Add design-time proxies support via analyzers and code fixes
• Add support for updating out-of-date proxies (analyzer + codefix)
• Returns
• Callbacks
• Events
• Throws
• Setup void methods
• Default value for Task/Task
• Overridable default value behavior
• Named mocks
• Make debugging and inspecting mocks and their state awesome
• Recursive mocks
• Verify
• Verifiable
• All Moq v4 features available in v5
• Linq to Mocks @marianor
• Stunts nuget package via NuGetizer
• Stunts.Sdk nuget package via NuGetizer
• Moq.Sdk nuget package via NuGetizer
• CI nuget feed with all packages
• Analyzer/code fixes for legacy APIs via nuget
• New website, maybe docfx? See https://www.dennisdel.com/how-we-build-documentation/. Autofac.org uses RTD...
• Code coverage badge via coveralls.io
• Bring back dynamic run-time proxies

[drieseng]

With moq/moq.spikes@6a10327 done (which is great, btw), I assume you can also mark the Verify and/or Verifiable tasks done. Or what else did you have planned for these tasks?

[kzu]

@marianor I'd love it if you could rebase on top of main and see how it's all working out for the Linq implementation 💯

[RealGoodAnthony]

Would it be possible to see mocks of sealed types and non-virtual methods? It could be done with an IL hooking mechanism such as MonoMod.RuntimeDetour.

[kzu]

@RealGoodAnthony won't happen, nope. Moq has always been about automating what you could already do by hand. Sealed and non-virtual interception is something you could never do by hand, so, highly unlikely to ever happen (I personally wouldn't spend a minute on it, TBH).

[udlose]

Is there any timeline for Moq v5? I see this issue was opened in Apr 2017.

[kzu]

I'm resuming work on it this year. Should be able to ship it, finally :)