asp.net mvc - What is the correct architecture when upgrading multiple small vb6 applications to a centralized MVC app -

asp.net mvc - What is the correct architecture when upgrading multiple small vb6 applications to a centralized MVC app -

challenge:

we have 100+ vb6 applications. our setup every desktop server have (currently 20), apps should installed. in all, can math. users approach server, or connect through rdc, , generate reports there. problems have popped up, main reason management chose upgrade because not have vb6 dev't licenses anymore.

what using: visual studio 2010 sp1 professional microsoft server 2008 r2 (for deployment) oracle 11g (where info coming from) the question:

given cards dealt, seek proper strategy in consolidating these decentralized reports. right now, i'm suggesting mvc. however, not how should done in such way multiple developers can contribute in development simultaneously. how/what layers (dal/bll)?

we new coming vb6 background. thanks!

well, not rain on parade, questions boil downwards roi (return on investment), , based on you've said, roi incredibly small. mvc bet, since it's based on pattern applications should follow greater or lesser extent, but if you're stuck vs2010, won't able work latest , greatest versions of mvc/web api/entity framework/etc. means brand spanking new app out of date , rotting before kick out door.

if organization unwilling or unable upgrade @ to the lowest degree vs2012 (but long you're doing might go way 2013), can utilize mvc5, web api 2, , entity framework 6, forego new development , bare minimum create current applications work. cost perspective it's insane go new development on old, out-dated technology.

asp.net-mvc architecture vb6