You might consider whether .NET 7 is appropriate versus .NET 6. The pattern has generally been for every other .NET release to be an LTS (long-term service~3yrs) release versus an STS (~1.5yrs) release.
.NET 7 will hit end of support May 14, 2024.
.NET 6 will hit end of support November 12, 2024.
Meanwhile, we should see an LTS of .NET 8 in November.
Are you looking for this, or offering it for others?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
There is no difference in type of PDF between a PDF with all text and a PDF with all images and a PDF with both text and images. I assume image PDF means image in a PDF. When an image is extracted from a PDF it is the same as if the image was not in the PDF.
If you want to learn more, add stopwatches to see which "parts" are slower. Startup? Shutdown? Something else? What's the footprint? Debug versus release?
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
Reported issue. They suggested running from console with DOTNET_TC_QuickJitForLoops=0 env var defined.
That speeds it up slightly, although 6.0 is still a bit faster. I read somewhere that in 6.0, setting that to 0 speeds things up but that in .NET 7 there's no difference. Though to me it looks like it might be the other way round!
So for 6.0 I get 0.53/0.54s (two successive runs). For 7.0 it is 0.57/0.58s.
Dispose should rollback the transaction. However, the behavior of Dispose is provider specific, and should not replace calling Rollback.
In other words, the using block should roll-back the transaction if you haven't called Commit; but different database providers might not implement that correctly, and might require you to explicitly call Rollback.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
I can not understand how to set the timeout of a .net 6.0 web api application.
In the .net 4.8 application I set the executionTimeout parameter of the httpRuntime section in the web.config.
Is there anyone who can help me?
I have a Silverlight application I want to salvage.
I have no intention of rewriting (no chance I will trash all the work I've done on the code over the years).
Any solutions or alternatives you'd recommend?
Last Visit: 31-Dec-99 18:00 Last Update: 23-Sep-23 10:53