About Working in Visual Applications in VB Studio

The way projects and your visual applications are organized in VB Studio is slightly different. Here are some key differences of the VB Studio ecosystem that you'll need to get familiar with:

• Within a single VB Studio instance, you and your team members who use that instance are considered an organization. Within your organization, you will likely belong to one or more projects, each of which is devoted to a discrete software effort. For example, you might have a project for building a new Financial mobile app, and a different project for creating an HR web application. A project brings together all the tools you need to create those artifacts, such as a Git repository for storing your source code, a pipeline to provide continuous integration and delivery, an issue tracking system, team wikis, and more.

• All of your work in VB Studio is done in the context of a workspace, a completely private area where you can work on your visual application. Your work is stored in your own clone of the project's Git repository, and is not visible to others until you a) merge it to the project's Git repo, b) choose to Share it with other for testing, or c) deploy it. A workspace also includes a pointer to the development or test environment where you plan to deploy your app, which must be a separate Visual Builder instance (also known as a "runtime environment"). You can deploy your app manually, or wire it up to a pipeline to do it automatically, such as when a developer on your project merges his or her branch to the master branch.

While the Visual Builder's Designer is still available, you can see that some things have changed. For details about tasks that you now do differently in VB Studio, see For Visual Builder Users.