Site Sections
Posts
38
Comments
48
Trackbacks
1
<< IIS e il misterioso errore COM object that has been separated from its underlying RCW cannot be used | Home
An application built on traditional .Net framework is not a legacy application

Se seguite i vari blog MS avrete notato che sull'argomento .Net Core e full .Net Framewotk spesso citano/abusano il termine "legacy application" per fare riferimento alle applicazioni basate sul .Net Framework.

Il loro obiettivo, alla fine dei conti, è spingere sempre più Dev all'adozione del nuovo nato .Net Core parlando per le esistenti (legacy?) applicazioni di porting da un framework all'altro.

Ecco quindi la doverosa precisazione di Cesar de la Torre in occasione del post relativo all'aggiornamento del libro "Microservices and Docker containers: Architecture, Patterns and Development guidance (Updated for .NET Core 2.0)"

"Legacy applications based on the traditional .NET Framework” literally means legacy apps (apps that have a significant time since they were built) that are based (were built) using the traditional .NET Framework. On the contrary, we are not saying, at all, that any new application built on the traditional .NET Framework is a legacy application.

Fonte: Microservices and docker containers architecture patterns and development guidance
posted on lunedì 20 novembre 2017 19:09 Print
Comments have been closed on this topic.
News
Locations of visitors to this page Blog personale
Archives
Post Categories
Bloggers
Tempo libero