If you have some years as developer, for sure you’ll remember the mother or grandmother of a colleague that “has complicated the easy use of references in a development project“. Even with diferent words, the functionality of the references in different languages is the same: import a module which provides a feature XYZ. And caution, because this import action can involve bringing modules locally or create proxies to work with them in a “service” mode.
With the passage of time, these modules began to be more complex and of course, it was not just a single module, but it also had dependencies with other modules. So package managers like NPM for node.js or NuGet for .net arrived. These apps allow us to manage package dependencies in a “transparent” way and it was easier to work with them.
However, the concept of reference is something that has already evolved much. Once upon a time they started as a simple requeriment unit. Now the business apps needs tend to be something like
-Connect to Dynamics AX and create purchase orders
-Automatically create entries in platforms such as Twitter or Yammer
And of course, in addition to references or references packages, there are connected services, scripts and configuration files, and much more. When you create or maintain a robust app (not the typical Hello World) you are taking account of these actions for configuration and maintenance can lead to many problems.
It is at this point where it becomes “Connected Services“, such as a new option within Visual Studio 2015. The first thing that draws our attention is that the option is next to the classics “add reference”, “add service reference” and “manage nuget packages”
When we add a new connected service will see that we access a small “store” with different options to add services in an intelligent way.
If for example you select an Azure Storage, first thing we need to do is login credentials from Azure to be able to select the same. In this case we can see proof of Machine Learning in a trial of Azure account.
We also have the possibility of creating a new element, although this is specific for each option within Connected Services.
Finally, after finishing the process, we see in the project we have the references and NuGet packages already configured. We also have a Getting Started, created specifically to “remember” mode.
And most importantly, this “store” of connected services is 100% expandable. If in the previous step, we decided to add other services, this action will take us to Visual Studio Gallery where we have a category “Services”. From here we only have to download the VSIX, install, restart Visual Studio and ready
We can already see new options within the “Connected Services” window
What was said… Visual Studio 2015, productivity to the limit 😀
Greetings @ Madrid (with a rain of these)