In this issue....

Announcing Latest Synergy Releases  

As the year wraps up, we’ve wrapped up a couple more product releases.

Synergy/DE 12.2.1.1010, our final 12.2 feature release, delivers a Synergy .NET runtime that targets .NET 8. Test your applications with this version and send us feedback so we can incorporate it into our upcoming 12.3 LTS release. 

SDI 2023.12.1823, our latest Synergy DBL Integration for Visual Studio release, includes fixes to issues identified by SonarQube’s static code analysis, as well as other updates to enhance your developer experience.

Good, fast, cheap. Choose two. The project management “iron triangle” expands on the common law of business balance by contending that a project is constrained between scope, cost, and time. A change in one of these constraints necessitates adjustments in the others to compensate, or quality will suffer.

This article delves into the history of the evolution of different software development processes, from the waterfall model, to ad hoc development, to agile, and beyond.

If you didn’t join us for our recent webinars, now’s a great time to watch them. As the year winds down, catching up on the latest Synergy news will position you for a great start in 2024. 

Synergy Update: What’s New, What’s Next (Dec. 2023) provides the latest news on Synergy/DE, SDI, Harmony Core, some work we’re doing with Apache Kafka, and Developer Support. 

Getting to Visual Studio May Be Easier Than You Think (Nov. 2023) shares insights from our solutions architect, Dan Ellis, on his experiences moving customers to Visual Studio.

You can increase the efficiency and maintainability of your Synergy DBL code, whether it be traditional or .NET, by learning some implementation details of the Synergy compilers. By having a general understanding of what the compiler is doing, you can reduce build times and boost program performance.

This article discusses how to make programs faster, how to get extra performance out of the Synergy compiler, and how to make developer collaboration easier by focusing on code maintainability and readability. The choices made by a Synergy developer can have a major impact for applications running in the far future. This advice regarding the Synergy compilers will allow you to make better, more informed choices.

While it’s common to adjust compile and build options for Synergy projects by setting options on Visual Studio’s project properties pages, this can also be done directly in MSBuild commands. However, before you can set a Synergy-specific option in an MSBuild command, you will need to edit the project file (.synproj) to include a custom property for that option. You can then use that custom property in MSBuild commands to set the option.

For example, if you want to set the Synergy compiler warning level in MSBuild commands, you can add a custom property to the DBLCmdOptions setting in .synproj. When you first open the .synproj file, this setting will look something like this:

• <DBLCmdOptions>-W4</DBLCmdOptions>

To enable this to be set in an MSBuild command, add a custom property such as $(WarningOverride):

• <DBLCmOptions>-W4 $(WarningOverride)</DBLCmdOptions>

Then, in your MSBuild command, set the property with something like “-property:WarningOverride=-W0”, which changes the warning level to 0:

• msbuild -property:WarningOverride=-W0

Further reading: Understanding the project file (Microsoft documentation explaining project files and properties)

Industry News & Articles

• Announcing .NET 8
• DevOps and Automation
• Why Is Building an Effective Agile Product Development Process So Complicated?
• Visual Studio 17.9 Preview 2 Has Arrived!
• Want to Know if Your Data Are Managed Responsibly? Here Are 15 Questions to Help You Find Out
• Reducing the Total Cost of Ownership of Software Testing
• Data Structures and Types Explained
• Navigating the Cybersecurity Landscape

Looking for past issues of Synergy-e-News?