Improved debugging allowed edit and continue functionality: when a running application was paused in the debugger, code could be modified on the fly and the execution continued using the modified code.Nullable value types were also relying on them, for example. Generics weren’t limited to collections, though. Alternatively, custom collection classes had to be derived for each data type. When used with other data types, code had to cast the objects back to the correct type after retrieving them from the collection. Before generics, only objects could be stored in the provided collection classes. Generics was widely used in collection classes, such as lists, stacks, dictionaries etc. The introduction of generics allowed creation of templated data structures that could be used with any data type while still preserving full type safety.Let’s name only the ones with the biggest impact: It built on the recognized weaknesses of the previous two versions and introduced many new features to boost developer productivity. NET framework 2.0 was a different story, altogether. There wasn’t a particularly convincing reason to migrate to v1.1 unless you had a specific need for one of these features. The most notable new features were support for IPv6, mobile controls for ASP.NET Web Forms and an out-of-the-box ADO.NET data provider for ODBC. Although it featured a newer version of CLR (the Common Language Runtime), it was mostly to enable side-by-side installation of both versions on the same computer. ASP.NET Web Forms based web applications, and.Console and Windows Forms applications for the desktop,.Only the following types of applications were supported: NET framework 1.0 included a very limited set of application frameworks. Here’s a quick rundown of the major features in every. Most of the features we are casually used to, were not even available then and we would have a hard time if we wanted to use it for development of modern applications today. NET framework 1.0 and looking at it today, it seems much less impressive than it did at that time. NET FrameworkĪs of this writing, it’s been over fifteen years since the original release of. NET framework even when using the latest development tools.Įditorial Note: If you are looking to create cross-platform apps, supporting Windows, macOS and Linux, and that can be used on the web, mobile, cloud, and embedded/IoT scenarios, make sure to read What’s New for. NET framework versions and explore how we can still target older versions of. In this article, we’ll take a look at the major differences between the. Subscribe to the DotNetCurry (DNC) Magazine for FREE and download all previous, current and upcoming editions. NET Core, MVC, Azure, Angular, React, and more. NET framework features.Īre you keeping up with new developer technologies? Advance your IT career with our Free Developer magazines covering C#, Patterns. They make sure that all critical business software will keep running without issues, before doing any large-scale updates.Īs a result, the software we write can’t always take advantage of the latest. However, that’s not always the case in enterprise environments where IT personnel are often a lot more conservative. NET developers we’re used to running the latest version of the operating system on our computers and having the latest updates installed.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |