|
That took me way too long  
|
|
|
|
|
Glad it's not just me. 
Wrong is evil and must be defeated. - Jeff Ello
Never stop dreaming - Freddie Kruger
|
|
|
|
|
Why did the Star Wars movies come out as episodes 4,5,6,1,2,3,7,8,9
Because Yoda, releases, in charge of, he was.
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
Someone was kind enough to gather them up into one blog post for your cautionary enjoyment: .NET 5 - The breaking changes you need to know about | Miguel Bernard's Blog[^]
(( I figured it was noteworthy, but not newsy enough for the newsletter. Please forgive me and/or indulge me.
Let me know if you feel otherwise, as I know you would have even without this notice.
Why am I still writing? ))
TTFN - Kent
|
|
|
|
|
Most code access security APIs are obsolete
Ouch! 
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: Most code access security APIs are obsolete
Ouch!
Yes, indeed. But I'd have thought that most people using CAS are still on NET Framework. Or am I wrong about that?
** edit **
Ah yes, everyone using CAS is still on NET Framework.
modified 11-Nov-20 16:09pm.
|
|
|
|
|
Assuming that's true (and I am) then in standard and core ThreadPool.QueueUserWorkItem() and ThreadPool.UnsafeQueueUserWorkItem() must do the same thing. Interesting.
Real programmers use butterflies
|
|
|
|
|
I based my "Ah yes, everyone using CAS is still on NET Framework" from the quote below from Breaking changes, version 3.1 to 5.0 - .NET Core | Microsoft Docs[^] in the 'Reason for change' subsection[1]:
Quote: Reason for change
Code access security (CAS) is an unsupported legacy technology. The infrastructure to enable CAS exists only in .NET Framework 2.x - 4.x, but is deprecated and not receiving servicing or security fixes.
Due to CAS's deprecation, the supporting infrastructure was not brought forward to .NET Core or .NET 5.0+. However, the APIs were brought forward so that apps could cross-compile against .NET Framework and .NET Core. This led to "fail open" scenarios, where some CAS-related APIs exist and are callable but perform no action at run time. This can lead to security issues for components that expect the runtime to honor CAS-related attributes or programmatic API calls. To better communicate that the runtime doesn't respect these attributes or APIs, we have obsoleted the majority of them in .NET 5.0.
This does seem to me to imply that the only people successfully using CAS will be in NET Framework.
Footnote:-
1: I'd have linked directly to the 'Reason for change' subsection but the anchor in the website appears to link to the wrong 'Reason for change' subsection.
|
|
|
|
|
It certainly seems so. Well, I learn something new everyday - at least if I'm lucky. Thanks!
Real programmers use butterflies
|
|
|
|
|
News -> Type: Developer News?
anyhow, thanks for the link. Definitely going to look at this later tonight.
|
|
|
|
|
I love that "Environment.OSVersion returns the correct operating system version" is a breaking change.
"Dammit! Now I have to unfix my code!"
cheers
Chris Maunder
|
|
|
|
|
Linked blog wrote: If you try to migrate from .NET Core 3.1 to .NET 5 you may run into a few breaking changes
Well, I couldn't care less.
Are there any breaking changes if I update from .Net 4.5 or 4.8 to .Net 5?
Wrong is evil and must be defeated. - Jeff Ello
Never stop dreaming - Freddie Kruger
|
|
|
|
|
|
You're doing this on purpose aren't you?  
Updated my answer
Wrong is evil and must be defeated. - Jeff Ello
Never stop dreaming - Freddie Kruger
|
|
|
|
|
Kent Sharkey wrote: I figured it was noteworthy, but not newsy enough for the newsletter.
Mwahahaha. 
|
|
|
|
|
Thanks for the link. I was pleased when I updated the SDK on my Pi from 3.1 to 5.0, edited the csproj file and ran my dotnet applications. It still gets the temp, humidity, and pressure within 85%.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
Miguel and I have very different definitions of "a few"
Anyway, I'm on .NET 3.1 with most of my projects so this is basically more work (read: money) for me 
|
|
|
|
|
Working on an app that is very much table driven. I have "table data"; but not in text form; only images.
Windows 10 has OCR!
Using a PDF reader (and a nice zoom), I use the "Snipping Tool" to snip my "table", and save it as an image file. Then using the C# sample OCR app, I load the image and it extracts the text. I'm getting 95 to 100% recognition. The app highlights what it extracted from the image so you can see what "noise" was the issue (you could then pixel adjust the image, for example). Since it's possible to access clip board images, you could eliminate the file step altogether. Brilliant stuff, IMO.
OCR sample - Code Samples | Microsoft Docs
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
I did not know Win10 had OCR out of the box for free.
I used to use LEADTools OCR a couple of year's ago but that is mega expensive.
Interesting.
|
|
|
|
|
Yep, for $3,000 (LeadTools) you could purchase a "whole lotta" Windows licenses, depending on your source and version and student status.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
It does and you can even use the OCR API in a WPF or WinForms application: OCR in WPF using the WinRT OCR API
"As beings of finite lifespan, our contributions to the sum of human knowledge is one of the greatest endeavors we can undertake and one of the defining characteristics of humanity itself"
|
|
|
|
|
I am missing something. If that requires a C# sample app how is it that W10 has OCR?
If it requires an external app then W10 does NOT have OCR at all. The app provides OCR.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I thought it was an app showing you how to use Windows 10 OCR assemblies. Perhaps I am missing something.
Shows how to use the OCR API:
Windows.Media.Ocr
|
|
|
|
|
I wouldn't post a turd party crap and claim "Windows 10 has OCR". That would be spam, IMO.
It's a "native" UWP app from the SDK "master" collection of "samples". (examples?)
I included the link so people could "examine" the code and decide if it was useful (since it is quite "small"), and runs "out of the box".
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
Apparently we have a different understanding of the word, "has."
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
