Not really. People can still use the current IDE. But for those of us who use Visual studio day in day ,day out, it would be good to have such a addin.
I think it would be a great addition to already powerful dev environment.
Instead, how about telling Erel what you think is missing in B4A IDE compared to Visual Studio and he will add those features.
Integrating an addin into Visual Studio does not sound like a good idea to me, because then people will demand integration with VS Designer, Object views etc etc...the support required for that will be too large, and almost impossible since VS is not open source.
I like that B4A is compact, straight-forward, stand-alone, familiar and easy to use. Visual Studio feels overwhelmingly large and complex by comparison. It does seem that there would be a market opportunity for a VB4Android plugin for Visual Studio - I don't have an opinion about that. I'm just satisfied to be using B4A as it already is.
Those interested in a VS plugin will be those that run Visual Studio already, and with Visual Studio costing a lot of money, you can therefore assume that the people using the tool can afford to pay a lot of money.
I say make the plugin and then sell it for a high price.
But for a quirk of fate we might have all been using VS anyway. When Google was developing Android they nearly used C# instead of Java, but there happened to be more Java developers in their organization.
But for a quirk of fate we might have all been using VS anyway. When Google was developing Android they nearly used C# instead of Java, but there happened to be more Java developers in their organization.
Why would they have used C#, a proprietary language that outputs to MSIL, which only runs in .NET on an NT-based system?
There is no way they were designing a mobile OS in cooperation with Microsoft. Sorry, but that just seems unrealistic. Keep in mind that Mono was awful when Android was being developed.