Controlling Visual Studio behavior for Synergy projects and files
You can customize many aspects of Visual Studio’s behavior for Synergy projects. You can control
- the behavior of IntelliSense and the Visual Studio code editor. For example, you can control the way tabs work and the way indentation is applied in code blocks. See Options for Synergy/DE projects for more information.
- settings that determine which Synergy version IntelliSense will be limited to. This can be useful, for example, if you have the latest version of Synergy on your development machine, while other members of your development team use older versions. If you set the “IntelliSense language version” option (on the Build page of Project Designer) to the lowest common Synergy version for your team, IntelliSense will limit completions, listings, etc., to features that were available in that version. This helps you avoid creating code that won’t work with other development team members’ systems. See Build page, Project Designer for more information.
- settings that determine how the project is built. This includes settings for platform target (x86, x64, or Any CPU), Synergy runtime target, debugging, and the compiler. For example, we recommend that you develop with the most recent version of Synergy/DE and SDI. If production machines use an earlier version, set the “Synergy runtime target” option (on the Build page of Project Designer) to the version of Synergy running on the production machines. See Build page, Project Designer for more information.
File types and build actions
There are also settings that control how different file types (files with different extensions) are treated in Synergy projects. By default, Visual Studio treats Synergy project files with the .dbl and .dbc extensions as compilable files, and it treats Synergy project files with the .def or .rec extension as content (non-compilable) files. You can customize this by
- adding file extensions to the “Additional Compile File Extensions” and “Additional Content File Extensions” fields in the IntelliSense dialog box for the Synergy DBL text editor, as illustrated in figure 1 below. See IntelliSense, text editor options. for more information.
- changing the Build Action for an individual file (e.g., right-click the file in Solution Explorer, select Properties from the context menu) as illustrated in figure 2 below.
You can set Build Action for a file in a Synergy project to one of the following. Files with unrecognized extensions default to None.
- Compile. The file is compiled and added to the build output.
- Content. The file is copied to the project output (without being processed).
- Embedded Resource. The file is processed by a specified tool and the results are embedded in a manifest resource exclusive to the assembly. This setting is ignored for traditional Synergy projects.
- None. The file is ignored by the build. It is not processed or included in the project output.
- Page. The file is compiled as XAML and is embedded in a shared assembly manifest resource. This setting is for WPF projects only. It is ignored for all others.
- Resource. The file is added as a linked resource (.resx). This setting is for WPF projects only. It is ignored for all others.
- ApplicationDefinition. The file (which must be a XAML or class file) is used to define the application. This setting is for WPF projects only. It is ignored for all others
1. Specifying additional file extensions for Synergy projects.
2. Changing the Build Action for a specific source file in a project.