I literally have my .net security book from Apress holding up my monitor and it's about 10cm away from my fingers at the moment. I spent ages learning that and all the other stuff you mention.
I spent a considerable time in my early career building RPC over serial ports in C and assembler so that will always hold a place in my heart :-D But having spent years (!) time doing XML-based services I'm perfectly happy to see fewer angle brackets though! regards, Preet, in Auckland NZ On Fri, 25 Mar 2022 at 12:03, Greg Keogh <gfke...@gmail.com> wrote: > TGIF folks, > > I've had a large suite of projects stuck on Framework 4.5 because of old > servers, but finally I have the chance to upgrade them to newer platforms > and use newer tools and libraries. I have decided that all existing full > Framework projects will simply go up to 4.8, but all new projects will be > in .NET 6 and all web apps will be Blazor (death from above to server-side > web apps!). > > During my research I noticed some interesting obsolete technologies in > .NET Core. You probably all know this, but I'd like to make a personal > eulogy. > > *Remoting > <https://docs.microsoft.com/en-us/dotnet/core/porting/net-framework-tech-unavailable#remoting>* > - Farewell old chum. I used this in Framework 1.0 to write a distributed > client-server suite with callbacks for notifications. The amount of core > code was surprisingly small and simple. Before the arrival of Remoting, > writing such a thing would have scared the pants off the most confident > coder. You could have used a VB6 server or written C sockets or RPC or > whatever, but think of the effort and the fragile results! > > *AppDomains* - Strange things, but useful in certain circumstances to > load (and unload) libraries. Closely related to Remoting and the next item. > Using separate processes to get a similar effect is a heavyweight and > cumbersome alternative. I found I own a single old utility project that > uses an AppDoman. > > *CAS > <https://docs.microsoft.com/en-us/dotnet/core/porting/net-framework-tech-unavailable#code-access-security-cas>* > - Yeah, don't slam the door on the way out. What a weird thing ... > sophisticated security boundaries buried inside .NET. I never used a single > CAS feature in 20 years, preferring to just handball security issues to the > operating system. I think it's historically interesting that something so > comprehensive was created and advertised prominently in books and articles, > then trivially dismissed as not useful. > > *WCF* - Mostly good riddance. Jeez that thing was complicated to > configure, because it tried to do everything for everyone everywhere. I > still miss the SOAP protocol and WSDL. What angers me is that it's all been > replaced by REST, an omni-shambles of a so-called convention that looks > like some kid's high school project. > > There endeth the rant. Comments and recriminations welcome. > > *Greg K* >
