We implemented support for 1C:Enterprise 8 platform version 8.3.20. You can use the updated version to run and debug configurations, as well as to develop end-user applications.
Mandatory Use of Java Virtual Machine (Server VM)
Now 1C:EDT runs on server Java Virtual Machine (server VM) by default. This ensures high performance compared to client VM previously used by default.
No additional setup is needed in case you use 1C:EDT Start to run the software. In case you start 1C:EDT with other tools, make sure you add a path to Java application in 1cedt.ini.
Select Development Environment to Run a Project
The mechanism of selection development environment in 1C:EDT Start now works differently in cases when a project has no assigned development environment, or a matching environment cannot be found.
We revised the project type card on the first page of the project creation wizard. Now it is easier to understand how to select non-default development environments. At that, we aimed to keep life simple for those who prefer to stick to the default and immediately proceed to the next step.
We added a new entity called Applications and introduced a new panel with the respective name. An application is a piece of software subject to download, update and deploy within a configuration. Applications represent a connection between a project and a 1C:Enterprise information database used to develop and debug such a project.
We might say that applications replaced project connections to information databases.
The Applications panel contains all applications connected to the active project (the project selected in the Navigator panel). You can manually add new applications to the project. Besides, when you import a new project from an information database, the EDT automatically creates an application for it.
The Applications panel is a convenient place to run and debug applications.
At that, applications have a dedicated editor that, among other things, allows users to select how a configuration should be updated. In previous versions you had to do it with the project editor. Also, you can set rights to access an information database or debug server port directly in an application. Previously we had to use startup configuration for this purpose. More to it, you can use the application editor to push an information database to a server of your choice.
1C:EDT Language Templates
We introduced plenty of changes to the built-in language templates. Now you can store templates in both the workspace and project. Additionally, you can automatically import templates from 1C:Enterprise ST-files. There is a convenient way to apply contexts to templates and add variables that describe actions after a template is inserted.
We dramatically modified the configuration check component. Now you can customize standard checks created by software 1C:EDT developers, set up your own, and connect them as 1C:EDT plugins.
You can apply or cancel checks for the whole configuration or create several check profiles that can be applied at different stages of configuration development.
You can suspend active checks for selected subsystems, configuration objects, forms, modules, procedures, and others. Thus, a check stays active just for some parts of the configuration that you select.
Saving Configuration into a File
Now, before we save information database configuration into a CF-file, we make sure the database is connected to a project, and its configuration is in agreement with this project. If the information database configuration is different from the project's one, 1C:EDT brings up the notification and automatically flags Update configuration before export to a file option. It means that the system adjusts the database configuration to the configuration of the connected project and only then saves it to a file.
You can start this wizard from the Information Databases panel by selecting Save configuration to a file... in the context menu of the selected database.
Updating a Project with an Information Database
If an information database is changed outside of 1C:EDT (say, in Designer), when you start a project or attempt to import a configuration into an existing project, 1C:EDT suggests importing to the project configuration the changes contained in the information database.
You can also set compare/merge parameters to apply during the merge of configuration with the project.
Pull and Merge...
Team > Pull and merge in Navigator panel received configuration compare/merge settings (comparison strategy, module comparison mode, etc.) These settings are available on page two of the wizard.
Note that Pull and merge command does not invoke a dialog box, and 1C:EDT applies standard compare/merge settings.