[DCR] Bot runtime directory structure changes

Suggesting to change the concept of BotProject to bot runtime conceptually, since it seems like a more appropriate name.

As part of an effort to get Azure Functions integrated into composer I’m shuffling things around, and it marks a good time to re-think the folder structure for the bot runtime.

Proposed folder structure:

• runtime/dotnet/ Dotnet root
• runtime/dotnet/core/ Dotnet core shared libraries. Most of the dotnet code should be here.
• runtime/dotnet/azurefunctions/
• runtime/dotnet/azurewebapp/
• runtime/node/core/
• runtime/node/azurefunctions/
• runtime/node/azurewebapp/
• runtime/node/someothertechnology/

Note that we use dotnet in order to match with the botbuilder-* repos. We keep node since it really will host node bots for the first iteration. This also leaves the open slot for a js folder if / when we support browser js bots.

In a more generic way, the folder structure will be:

• runtime/{language}/core/
• runtime/{language}/{hostingTechnology1}/
• runtime/{language}/{hostingTechnology2}/

One neat thing about this, is that the eject or publish commands will onlyu require to move the core library plus the selected integration library.

[benbrown]

Looks grrrrrrrrreat!

[luhan2017]

That looks good to me. This new structure might impact the current implementation of bot folder reference, appsettings.json reference, also some copying logic in local and azure publish plugins, but they are all expected. Can’t wait for your cool feature, go go go @carlosscastro