Teams Toolkit 3.0 boosts collaboration between multiple developers – Visual Studio Magazine
Teams Toolkit 3.0 boosts collaboration between multiple developers
Microsoft’s Teams Toolkit 3.0 debuted with several new features, including better collaboration between multiple developers and improved multi-environment management.
The company said the toolkit is the fastest way to develop Teams apps with Microsoft 365 and Azure integrations. It is available in the Visual Studio Code Marketplace as a preview extension. The tool helps developers build, debug, and deploy Teams apps with built-in identity, access to cloud storage and data from Microsoft Graph and other Azure and Microsoft 365 services, delivering a zero-configuration approach to business. developer experience.
It comes with a visual interface and a command line tool (TeamsFx CLI), providing:
- Tabs: These are embedded web pages that support Teams, made up of simple HTML tags that point to domains declared in the app manifesto and can be added as part of a channel within a team, d ‘a group chat or a personal application for an individual user.
- Robots: These allow users to interact with a developer’s web services through text, interactive maps, and task modules.
- Mail extension: This allows users to interact with a developer’s web services through buttons and forms in the Microsoft Teams client.
In the new extension v3.0, it is now easier to collaborate with other developers.
“Did you wish it was easier to collaborate on a Teams app project with your coworkers?” Tomomi Imura of the development team asked in a blog post on December 2. Publish announces v3.0. âWell, I have good news! This much anticipated feature for managing multiple environments was introduced in the latest version of Teams Toolkit and supports project collaborations between multiple developers. Previously, you had to manually manage permissions for Teams and Azure AD. But from now on, the toolkit will take care of that for you. ”
Multi-environment management, meanwhile, is improved with the possibility of adding a more remote environment beyond the default “local” and “dev” (for remote) environments which are generated when a new project is created. with the toolbox.
This is useful, Imura said, because developers typically start developing in a local environment, but will eventually have to manage multiple environments. “In addition to your locale, you will likely end up having multiple environments, such as ‘dev’, ‘qa’, ‘stage’, and the production environment to deploy.”
For more information on this topic, Microsoft has provided guidance to Manage multiple environments in Teams Toolkit.
Also detailed in the announcement:
- Provision Azure resources using ARM and Bicep: Developers can now provision declaratively to create an Azure Resource Manager (ARM) template. It is a set of Biceps files (biceps is a domain-specific language that uses declarative syntax to deploy Azure resources) that defines the infrastructure and configuration of a project.
- CI / CD support: Developers can now enable CI / CD workflows to automate Teams application development processes for the multi-environment scenarios described above. As an example, the post explains how to configure GitHub actions or configure CI / CD pipelines with other software, such as Azure DevOps or Jenkins, for which the team has prepared sample configuration files (with others).
âI hope these new features give your Teams app development workflow more confidence and we can’t wait to see your amazing apps in production!â Imura said in conclusion.