Earlier this year I had the awesome opportunity to share my SQL Database From A Dev’s Perspective session to the overwhelming audience of Transylvanian software developers in Cluj-Napoca (Romania) during one of the very best IT conferences in Eastern Europe, namely ITCamp.
I do realize you might have had the chance of downloading the slides before (either from my post-event blog-posts ) or you might have attended the session at WinDays in Croatia, NT Konferenca in Slovenia or CloudBurst in Sweden. However, if that is not the case or if you just needed a quick reminder on DDM, RLS, AlwaysEncrypted, InMemory OLTP etc. (what are all these?!), here’s your chance to watch the session from the comfort of your own couch.
All the best and happy entertainment/learning 🙂
Azure SQL for Developers – Alex Mang from ITCamp on Vimeo.
The entire DevOps story with the Microsoft Stack is expanding its reach to more and more services and with an ever-growing set of advanced features. During this article, I will cover the benefits and ways to configure Service Endpoints within either Visual Studio Team Services and Team Foundation Service, in order to create a highly coupled ALM story for your apps.
What are Service Endpoints?
Back in the days of Team Foundation Services (2013 and prior to that), everyone was asking for a way to make Release Management expand to other project types rather than .NET and VB/C++. Taken this feedback (along with many other requests) Microsoft rewrote Team Build. Personally, I believe the entire DevOps story using the Microsoft Stack has become more mature than ever and ready to solve the most complex requirements your application has. In order to achieve this type of extensibility, Team Build allows one to add features in two ways: (1) by installing extensions which can either be wrote and uploaded by yourself or by installed from the Visual Studio Marketplace or by (2) taking advantage of the TFX Command Line Interface which allows you to add custom designed tasks. The latter is especially useful when it comes to creating a single-task functionality as an atomic process part of the build or release definition, rather than leverage several tasks individually. This ensures that in the situation of build and release processes which have to do the same tasks over and over again a few times are easily configurable and thus reduces the error-prone nature of a highly-configurable workflow system, such as Team Build.
The beauty of these tasks are that they are not exclusively designed to Microsoft-specific products and services – in fact, most of the tasks which have to deal with external services will specify the external service’s endpoint in the form of a connection setting which is team-project wide. Again, this helps prevent errors related to connection strings and such.
These connection settings are known as Service Endpoints and can be configured from the Settings pane of any team project, both in Visual Studio Team Services and Team Foundation Services, under the Services tab.
Read More →