Greg next time get a dump and you can use VS to debug it back on your own
machine. The AV could be something as simple as de-referencing a null.
Merge something like this into the registry
https://github.com/dotnet/project-system/blob/main/docs/repo/content/AlwaysSaveDevEnvCrashDumps.reg
Back then C++ wasn't so complex. The STL was in the process of being
developed. Pentiums were state of the art
On Fri, 1 Sept 2023, 10:57 Greg Keogh via ozdotnet,
wrote:
> I have never understood the fixation with C++ unless you're in the
>> business of writing kernels, device drivers,
>
> I have never understood the fixation with C++ unless you're in the
> business of writing kernels, device drivers, embedded systems, etc.
>
The library we're phasing out was started around 1997, so you can throw the
authors a bone because the world was very different back then. Your main
You really need to be generating the pdb files and storing them in a symbol
server. If you want to view the source code associated with it, store that
as well. For every build you want to be able to debug. I used to store it
for all builds, and clean up later, because internal builds sometimes
I have never understood the fixation with C++ unless you're in the business
of writing kernels, device drivers, embedded systems, etc.
On Fri, 1 Sept 2023 at 08:44, Greg Keogh via ozdotnet
wrote:
> Folks, it's Friday and I have an anecdote to share before I return to
> today's coding fiasco.
Folks, it's Friday and I have an anecdote to share before I return to
today's coding fiasco. I'll just tell you what happened and try to avoid
making judgements, I'll leave that to you.
For about 4 years we've had an Azure hosted Web API/service driving a
moderately complex Blazor app and some
