Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
165518 stories
·
33 followers

PostgreSQL 19 Released with Online Table Repacking and Query Planning Controls

1 Share

The PostgreSQL Global Development Group released PostgreSQL 19, introducing changes to database maintenance, query planning, replication, and application development. The release focuses on reducing administrative overhead and improving performance, with new tools for reorganizing tables without downtime and controlling query plans.

By Robert Krzaczyński
Read the whole story
alvinashcraft
just a second ago
reply
Pennsylvania, USA
Share this story
Delete

Claude Code Has Been Leaking Secrets Through Its "Don't Ask Again" Feature

1 Share

Agentic security firm Apiiro found that Claude Code has been exposing secrets in public repositories due to how it stores them in local file on developers' machines to implement "Don't Ask Again". The company identified 1,122 secrets in claude/settings.local.json files and another 1,160 in git history, in the shared settings.json, and in agent chat transcripts stored in repos.

By Sergio De Simone
Read the whole story
alvinashcraft
16 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Community projects at .NET Conf 2026, my favorites

1 Share

I was one of the presenters at .NET Conf 2026, and if I'm honest, most of my attention went to my own session, Taking Cake 7 to Eleven: Pipelines as Code with C# and .NET 11. The week was busy, as I was also part of shipping Cake 7 with day one support for .NET 11. Now that every session is available on YouTube on demand, I've been catching up on the ones I missed. There was no dedicated .NET Foundation state of the union this year, but the impact of community-led projects was impossible to miss. They turned up in demos, in code samples and in the talks themselves.

Here are the ones that stuck with me, starting with two favorites and then a quick roundup of the rest.

Build a .NET TUI in 30 Minutes

Isaac Levin's talk from Community Day 1 is the one I'd point anyone to first if they want to build something in the terminal. Isaac walks through terminal user interfaces (TUIs) in .NET, and Spectre.Console is the library he uses throughout. Prompts, tables, colors, spinners and progress bars all come from it, and the difference from plain Console.WriteLine is night and day once you've seen it live.

What I liked most was the part about testing. Isaac shows how to mock the Spectre.Console abstractions so the UI code can be tested without a real terminal, and then separates the concerns into layers so the prompting and rendering don't leak into the rest of the application. It's a practical talk, built live, and it does exactly what the title promises.

C# File-based apps turned up to 11!

Damian Edwards' Day 2 session was a live coding tour of file-based apps, starting with the basics from .NET 10 and moving on to what landed in .NET 11. No slides, just code, which I always appreciate.

The part that made me smile was when Damian opened a cake.cs file. I'm one of the lead maintainers of Cake, so seeing it on a .NET Conf stage was nice recognition. It was great to see community projects like Cake, Humanizer and Spectre.Console getting airtime across the sessions, not just in their own talks.

The rest of the roundup

Beyond the two favorites, a handful of community projects showed up across the sessions.

  • Rx.NET: Ian Griffiths talked about where Async Rx.NET is today and what's planned next. It's part of the .NET Foundation Rx.NET project, and it's a good reminder that Rx is still very much alive.
  • Oqtane and DNN: Shaun Walker introduced BlazorKit, which is built on Oqtane, a Blazor application framework. He also gave a bit of history on DNN, which he started back in 2003 and which is still widely used today.
  • Verify and FsCheck: Davide Bellone's talk on unit tests not being enough covers snapshot tests with Verify and property-based tests with FsCheck, all on top of xUnit. If you've ever stared at a large expected object in a test, this one is worth your time.
  • Orchard Core: Zoltán Lehóczky's session on end-to-end testing uses an Orchard Core site as the demo app, combining xUnit, Selenium, accessibility checks with axe and security scanning with ZAP.
  • NUnit: Jeffrey Palermo mentioned that he still uses NUnit, in this case for architecture tests that check patterns rather than behavior.
  • Polly: Marc Gravell's SE.Redis talk compares retries inside the library with retries you'd normally add using Polly. His argument is that the library has more context about what's going on, so it can retry when it's safe rather than just failing.

Other favorites from .NET Conf

A few more sessions that stuck with me, beyond the community ones mentioned.

Closing thoughts

What I took away is that community projects are part of the core of the .NET ecosystem. Most are maintained by volunteers, often with little thanks, so it was great to see them show up in the demos, the testing talks, and the tools people use every day, even when the session itself was about something else. Watching the sessions on demand is the best way to see that for yourself, and the full .NET Conf 2026 playlist is there whenever you have time.

A big thank you to all the maintainers of .NET community projects. The hours spent on issues, pull requests, documentation, and releases mostly go unseen, yet they are what keep these projects alive for the rest of us. Thank you for your service.



Read the whole story
alvinashcraft
29 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Rotating credentials in Azure API Management

1 Share

Credentials covered by this guidance

  • Subscription keys
  • Named values that contain secrets
  • Backend credentials (headers, query parameters, client certificates)
  • OAuth 2.0 and OpenID Connect client secrets
  • Connection strings (for example, Event Hubs loggers)
  • Credentials written directly into policies

How to rotate safely

Use this order when both credentials can remain valid:

  1. Create a new secret where it is issued.
  2. Update API Management with the new secret.
  3. Test your APIs.
  4. Revoke the old secret.

Important: Rotate each credential where it is issued (for example, the backend service or identity provider), not only in API Management. Updating the value in API Management alone does not invalidate the old credential.

Find your instances and credentials

Step 1: List your API Management instances

In the Azure portal, search for API Management services, or use Azure CLI:

In one subscription:

az apim list --subscription {subscriptionId} --query "[].{name:name, resourceGroup:resourceGroup}" --output table

Across accessible subscriptions (one Azure Resource Graph page):

az graph query -q "resources | where type =~ 'microsoft.apimanagement/service' | project name, resourceGroup, subscriptionId, location"

Step 2: List the credentials in each instance

In the commands, replace {base} with https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{rg}/providers/Microsoft.ApiManagement/service/{apimName}, and the other values in braces with your own. In policies, look for values such as Authorization headers, keys, passwords, tokens or connection strings written out in full instead of referenced as a named value.

Subscription keys are under APIs > Subscriptions in the Azure portal.

az rest --method get --url "{base}/subscriptions?api-version=2024-05-01"

Named values are under APIs > Named values. The Type column shows whether each secret is stored in API Management or in Key Vault.

az apim nv list --resource-group {rg} --service-name {apimName} --output table

Backend credentials are under APIs > Backends > Authorization credentials.

az rest --method get --url "{base}/backends?api-version=2024-05-01"

OAuth 2.0 and OpenID Connect providers are under Developer portal > OAuth 2.0 + OpenID Connect. Developer portal sign-in providers are under Developer portal > Identities.

az rest --method get --url "{base}/authorizationServers?api-version=2024-05-01"
az rest --method get --url "{base}/openidConnectProviders?api-version=2024-05-01"
az rest --method get --url "{base}/identityProviders?api-version=2024-05-01"

List providers under APIs > Credential manager:

az rest --method get --url "{base}/authorizationProviders?api-version=2024-05-01"

Loggers that use connection strings (Event Hubs, Application Insights):

az rest --method get --url "{base}/loggers?api-version=2024-05-01"

Check global, API, and operation policies under Design. For product policies, select Products > the product > Policies.

az rest --method get --url "{base}/policies/policy?format=rawxml&api-version=2024-05-01"
az rest --method get --url "{base}/apis/{apiId}/policies/policy?format=rawxml&api-version=2024-05-01"

Step 3: Read the current secret values

Read each secret to identify which systems use it before you rotate it. This requires permission to read secrets on the instance. Store the output securely and delete it when you are finished.

az rest --method post --url "{base}/subscriptions/{sid}/listSecrets?api-version=2024-05-01"
az apim nv show-secret --resource-group {rg} --service-name {apimName} --named-value-id {namedValueId}
az rest --method post --url "{base}/authorizationServers/{id}/listSecrets?api-version=2024-05-01"
az rest --method post --url "{base}/openidConnectProviders/{id}/listSecrets?api-version=2024-05-01"
az rest --method post --url "{base}/identityProviders/{id}/listSecrets?api-version=2024-05-01"
az rest --method post --url "{base}/tenant/access/listSecrets?api-version=2024-05-01"

Rotate each credential type

The commands below use the same {base} placeholder as in Step 2. Replace the other values in braces with your own.

Subscription keys

Move callers to the secondary key, regenerate the primary key, move callers to the new primary key, then regenerate the secondary key.

az rest --method post --url "{base}/subscriptions/{sid}/regeneratePrimaryKey?api-version=2024-05-01"
az rest --method post --url "{base}/subscriptions/{sid}/regenerateSecondaryKey?api-version=2024-05-01"

For additional details, see Subscriptions in Azure API Management.

Named values

If the named value is backed by Key Vault, store the replacement in Key Vault, point any pinned reference to the new version, and refresh the named value. If the secret is stored in API Management, update the value with a new credential and consider moving it to Key Vault.

az rest --method post --url "{base}/namedValues/{namedValueId}/refreshSecret?api-version=2024-05-01"
az apim nv update --resource-group {rg} --service-name {apimName} --named-value-id {namedValueId} --value "{newValue}"

For additional details, see Use named values in Azure API Management policies.

Backend credentials

Stage the replacement at the backend. Update and test API Management before revoking the old credential. Example for a backend with only one credential, using its current ETag:

az rest --method patch --url "{base}/backends/{backendId}?api-version=2024-05-01" --headers 'If-Match={etag}' --body '{"properties":{"credentials":{"header":{"{headerName}":["{newKey}"]}}}}'

For additional details, see Backends in API Management.

OAuth 2.0 and OpenID Connect client secrets

Create the secret at its issuer. Update API Management, republish the portal if used, and test before deleting the old secret. For Microsoft Entra ID:

az ad app credential reset --id {appId} --append --display-name "apim-rotation"
az ad app credential delete --id {appId} --key-id {oldKeyId}

For additional details, see Add and manage application credentials in Microsoft Entra ID.

Connection strings

For Event Hubs, switch the logger to the secondary connection string and test delivery before renewing the namespace rule’s primary key:

az eventhubs namespace authorization-rule keys renew --resource-group {rg} --namespace-name {namespace} --name {ruleName} --key PrimaryKey

For additional details, see How to log events to Azure Event Hubs in Azure API Management.

Credentials in policies

Create the replacement at the source. Reference its Key Vault-backed named value as {{display-name}}. Test the policy before revoking the old credential.

For additional details, see Use named values in Azure API Management policies.

Management API access keys

For legacy Direct Management API keys, switch callers off each key before regenerating it.

az rest --method post --url "{base}/tenant/access/regeneratePrimaryKey?api-version=2024-05-01"
az rest --method post --url "{base}/tenant/access/regenerateSecondaryKey?api-version=2024-05-01"

For additional details, see Tenant Access - Regenerate Primary Key.

Best practices going forward

  • Use managed identities instead of keys and connection strings wherever supported.
  • Store secrets in Azure Key Vault and reference them as named values. Use a secret identifier without a version for automatic refresh.
  • Rotate credentials regularly and automate rotation where possible.
  • Review your configuration for subscriptions, users, policies or backends that you did not create.

Additional documentation

Read the whole story
alvinashcraft
4 hours ago
reply
Pennsylvania, USA
Share this story
Delete

Database Performance: Counting Rows with EF Core vs. ADO.NET

1 Share
Counting rows may seem simple, but the data-access approach can affect both execution time and memory allocations. This benchmark compares Entity Framework Core, compiled EF Core queries, and direct ADO.NET with SQLite to reveal which approach handles frequently executed count operations most efficiently.
Read the whole story
alvinashcraft
4 hours ago
reply
Pennsylvania, USA
Share this story
Delete

Typemock Isolator++ 5.4.7: Making C++ Unit Testing More Predictable

1 Share

C++ unit testing is rarely simple, especially when working with large applications, legacy dependencies, and complex runtime behavior. Mocking can help isolate code, but the mocking framework itself must be reliable.

Typemock Isolator++ 5.4.7 focuses on exactly that: predictable behavior, clearer errors, and more reliable test execution.

This release improves handling of Microsoft debugging symbols, fixes unnecessary copying of reference return values, and addresses potential deadlocks involving During filters.

These changes are particularly valuable for teams testing complex C++ applications where subtle runtime behavior can make failures difficult to diagnose.

Clearer Errors When Microsoft PDB Files Are Missing

Typemock Isolator++ uses debugging symbols to support its isolation and mocking capabilities. For some Windows system components, the required PDB files must be downloaded from Microsoft’s symbol servers.

Previously, missing required symbols could allow execution to continue, potentially leading to confusing runtime failures or crashes later in the test.

Version 5.4.7 changes this behavior.

When required Microsoft PDB files cannot be downloaded, Isolator++ now reports an explicit exception rather than continuing execution in a state where essential symbols are unavailable.

This is a breaking behavior change, but an intentional one.

A clear failure explaining that required debugging symbols are missing is far more useful than an unexplained crash several steps later.

For developers debugging complex C++ unit tests or CI pipeline failures, this means faster diagnosis and fewer misleading symptoms.

More Accurate Mocking of Reference Return Values

C++ references are fundamental to many APIs, especially those involving large objects, shared state, and performance-sensitive operations.

When a mocked method returns a reference, preserving the expected C++ semantics is essential.

Isolator++ 5.4.7 fixes unnecessary copying of reference return values in the CallTo API.

This helps ensure that mocking does not introduce unintended copying behavior when working with methods that return references, improving correctness and compatibility with real-world C++ code.

Improved Reliability of During Filters

Complex unit tests often require controlling mocked behavior within specific execution contexts.

Typemock Isolator++ provides During filters to support this kind of isolation.

Version 5.4.7 fixes potential deadlocks associated with these filters, improving reliability when running tests involving more complex interactions.

For developers working with large C++ codebases, avoiding intermittent hangs is especially important. A test that occasionally deadlocks can undermine confidence in the entire test suite.

Reliable C++ Mocking Matters

Mocking is supposed to remove obstacles from unit testing, not introduce new ones.

With version 5.4.7, Typemock Isolator++ continues improving the stability and predictability of C++ isolation. More informative failures, correct reference handling, and fewer potential deadlocks all contribute to a more dependable testing experience.

Whether you’re maintaining legacy C++ code, testing tightly coupled components, or building a reliable automated testing pipeline, these improvements help keep the focus where it belongs: testing your code rather than debugging your test framework.

Download Typemock Isolator++

The post Typemock Isolator++ 5.4.7: Making C++ Unit Testing More Predictable appeared first on Typemock.

Read the whole story
alvinashcraft
4 hours ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories