While I do not have the ‘answer’ to keeping or abandoning open source ( or MS products) I can offer a few suggestions on things to consider.
-Consider asking the questions to the staff. Maybe you will be surprised e.g. they could say we hate the open source/VB.Net and wish we had used product-X. Or they might say if you change to using development tool-Y we will all leave.
-If the products need to communicate/integrate can they as two different development tools. Or how well can they? If they are separate, why not continue development in different tools?
-Does the Open-Source Licenses agreement make sense to your business? E.g. do you have to create open source version of your software also? Do you have to send copies of the code to the open source tool developers, in general what restrictions are placed on the software that your company makes? There may not be any of significance, or there may be lots.
-Your company may very well me strengthen by having two development platforms, if the developers can communicate with each other on a professional level, e.g. I learned this trick in VB.Net might you be able to do that in the Open Source tool?
-Will the open source be able to keep up with MS-OS changes like VB.Net will? Will Vb.Net be able to run on other OS like Linux that the open source might?
-Do you think your customers will care? Will they think Open Source Development mean that your company is not serious about development? Will the customer praise you for not following the big bad Microsoft? Will they know or give a rat’s &(*@^#?
-Does the MS or Open source have the tools for future expansion?
-If for some reason all of the developers failed to show up in the morning, can you find replacements, e.g. who else using VB.Net/Open Source.
Lion Crest Software Services
Anthony L. Testi
President