It comes down to the same and as you mentioned to use suffixes, not prefixes, but with the mandatoryAffixes it doesn't affect the choice between them.
It comes down to the same and as you mentioned to use suffixes, not prefixes, but with the mandatoryAffixes it doesn't affect the choice between them.
When working with NuGet packages and the BCCH, the “installedPlatform” parameter uses this and then downloads a wrong artifact.
We’ve run into this with an ISV app in our ADO pipelines
When working with NuGet packages and the BCCH, the “installedPlatform” parameter uses this and then downloads a wrong artifact.
We’ve run into this with an ISV app in our ADO pipelines
If you can make it to Antwerp this summer, we should do a Beerinar combined with waffles 😅
If you can make it to Antwerp this summer, we should do a Beerinar combined with waffles 😅
Was fun to see if I could find the specific model based on the modelnumber of the chips, the closed I could find looks like this 🤗
Was fun to see if I could find the specific model based on the modelnumber of the chips, the closed I could find looks like this 🤗
What would be the best solution? I was thinking of a IoT Edge-device, IoT Hub and a Azure Function (API) where I then could do an API-call from BC.
Are there other approaches to this?
What would be the best solution? I was thinking of a IoT Edge-device, IoT Hub and a Azure Function (API) where I then could do an API-call from BC.
Are there other approaches to this?
#AskingForAFiend 😅
#AskingForAFiend 😅
Both of them points to the "System Application", where it seems there isn't a "0000JIR" value in the source code.
Both of them points to the "System Application", where it seems there isn't a "0000JIR" value in the source code.
It's not in the documentation it seems
learn.microsoft.com/en-us/dynami...
It's not in the documentation it seems
learn.microsoft.com/en-us/dynami...
In this way new objects are validated against the rules of the code analyzer and the older objects can be refactored in the future.
In this way new objects are validated against the rules of the code analyzer and the older objects can be refactored in the future.
For example, this converted from the-good-old-NAV-days to BC, still carries those solve-it-all-management codeunits 🤨
In your pipelines, I’d argue there should be a maximum, anything over like 100 should be treated as an compile error
For example, this converted from the-good-old-NAV-days to BC, still carries those solve-it-all-management codeunits 🤨
In your pipelines, I’d argue there should be a maximum, anything over like 100 should be treated as an compile error
I would like to store both values as a SecretText in a IsolatedStorage. I could Encode these while I save them in the IsolatedStorage, but that feels wrong somehow 🤔
I would like to store both values as a SecretText in a IsolatedStorage. I could Encode these while I save them in the IsolatedStorage, but that feels wrong somehow 🤔
How do I apply a urlEncode to a SecretText? 🤔
How do I apply a urlEncode to a SecretText? 🤔
At our company, we have several projects where the new rules found quite some potential defects that weren't detected during code reviews.
At our company, we have several projects where the new rules found quite some potential defects that weren't detected during code reviews.
Working on a new LinterCop rule: 'Set values for FlowFilter fields using filtering methods.'
This will raise a diagnostic in VS Code for cases like the example below.
I'm doubting of what the default severity should be:
⚠️ Warning or ℹ️ Info?
github.com/StefanMaron/...
Working on a new LinterCop rule: 'Set values for FlowFilter fields using filtering methods.'
This will raise a diagnostic in VS Code for cases like the example below.
I'm doubting of what the default severity should be:
⚠️ Warning or ℹ️ Info?
github.com/StefanMaron/...
After seeing the real Copilot features at #DirectionsEMEA, I’m not impressed with this and, honestly, even surprised they’d dare to call this Copilot.
After seeing the real Copilot features at #DirectionsEMEA, I’m not impressed with this and, honestly, even surprised they’d dare to call this Copilot.