No more exporting Environment Variable Values

by Dec 14, 2023

No more exporting Environment Variable Values

Next month, the default experience will no longer export environment variable values in your solution.

This makes it easier to follow best practices and avoid inadvertent mistakes.

A new โ€œExport valueโ€ toggle within the environment variable settings will allow you to opt-in to exporting the value, if needed.

I never understood why a solution export would also export the Environment Variable values, but glad it is going to be solved.

#

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

SpecFlow: Great concept, flawed execution.

SpecFlow: Great concept, flawed execution. SpecFlow, a BDD framework designed to make writing scenarios a breeze for requirement analysts. The problem: It falls short of its promise. โŒ The reality? Analysts rarely, if ever, write the specs themselves. Instead,...

read more

What if…? Production has a Staging slot.

What if...? Production has a Staging slot. Staging or QA environment needs to be the same or as close to production as it can be. Preferably, you want to restore a recent backup ๐Ÿ’พ from Production as Staging and then deploy your changes ๐Ÿ”„. Kudos ๐Ÿ‘ if you've fully...

read more

UUID v7 coming in .NET 9

UUID v7 coming in .NET 9 For those that didn't know, you can create Guids in different ways (algorithms). System.Guid supports UUID v4 out-of-the-box, the most used version. UUID v7 is now added, which creates Guids based on the current time. This means Guids can be...

read more