I am a supporter of Apex and know little about .Net: but the choice of platform and development architecture should include consideration not only of requirements and capabilities (although this is very important, of course), but also the skills and experience of most developers and system developers.
Apex and .NET do not have such a large number, but if the team does not have experience in Apex, but has experience in .NET, this will be the main factor when choosing .Net.
Other considerations are cost and simplicity. Apex is probably much simpler than .Net (fewer moving parts, tighter database integration) and cheaper (i.e., free with an Oracle license).
(plus: what Tony said.)
source share