Skip to main content

Happy 15th Birthday .NET

Today marks the 15th anniversary since .NET debuted to the world. On February 13th, 2002, the first version of .NET was released as part of Visual Studio.NET. It seems just like yesterday when Microsoft was building its “Next Generation Windows Services” and unleashed a new level of productivity with Visual Studio.NET.
Since the beginning, the .NET platform has allowed developers to quickly build and deploy robust applications, starting with Windows desktop and web server applications in 2002. You got an entire managed framework for building distributed Windows applications, ASP.NET was introduced as the next generation Active Server Pages for web-based development, and a new language, C# (pronounced “see sharp” :-)) came to be.
Over the years, .NET and it’s ecosystem has grown and expanded to meet the needs of all kinds of developers and platforms. As the technology landscape has changed, so has .NET. You can build anything with .NET including cross-platform web apps, cloud services, mobile device apps, games and so much more. We have a vibrant open-source community where you can participate in the direction of .NET.
With the release of Visual Studio 2017 coming on March 7th and Visual Studio’s 20th anniversary, .NET Core tools reach 1.0. Tune in March 7th and watch the keynote and live Q&A panels. A few nights ago we got together with the Microsoft Alumni Network and threw a big .NET birthday bash with former .NET team members & rock stars.
 Ref: https://blogs.msdn.microsoft.com/dotnet/2017/02/13/happy-15th-birthday-net/

Comments

  1. rmouniakNovember 29, 2018 at 3:13 PM

    Thanks for sharing valuable information. Your blogs were helpful to Dot NET learners. I
    request to update the blog through step-by-step. Also, find the Dot net news at Dot NET Online Course Bangalore

    ReplyDelete

Post a Comment

Popular posts from this blog

IPv4 header to requests when a client is using IPv6

  What is Pseudo IPv4? As a stopgap to accelerate the adoption of IPv6, Cloudflare offers Pseudo IPv4 which supports IPv6 addresses in legacy applications expecting IPv4 addresses. The goal is to provide a nearly unique IPv4 address for each IPv6 address, using Class E IPv4 address space, which is designated as experimental and would not normally see traffic. To learn more see  here . Options Add header:  Add additional Cf-Pseudo-IPv4 header only Overwrite headers:  Overwrite the existing Cf-Connecting-IP and X-Forwarded-For headers with a pseudo IPv4 address Cloudflare
Post a Comment
Read more

Intrusion detection system

An   intrusion detection system   ( IDS ) is a device or   software application   that monitors network or system activities for malicious activities or policy violations and produces reports to a management station.  IDS come in a variety of “flavors” and approach the goal of detecting suspicious traffic in different ways. There are network based (NIDS) and host based (HIDS) intrusion detection systems. Some systems may attempt to stop an intrusion attempt but this is neither required nor expected of a monitoring system.  Intrusion detection and prevention systems (IDPS) are primarily focused on identifying possible incidents, logging information about them, and reporting attempts. In addition, organizations use IDPSes for other purposes, such as identifying problems with security policies, documenting existing threats and deterring individuals from violating security policies.  IDPSes have become a necessary addition to the security infrastru...
Post a Comment
Read more

Amazon AWS - Cloudfront configuration

Amazon Cloudfront Dynamic Content Delivery HTTP GET and HEAD   requests are currently supported by Amazon CloudFront. Over time, we will add support for POST requests.   Our sample setup You can convert your existing blog or setup a new blog from scratch to use cloudfront. For demonstration purpose, I'm going to setup a new blog called www.contentdeliverynetworklog.com and serve the whole blog via cloudfront as follows: Blog domain name:   www.contentdeliverynetworklog.com   (CNAME to cloudfront) Blog origin domain name:   cp.contentdeliverynetworklog.com . To fetch web content from this origin web server. Static asset domain name:   s0.contentdeliverynetworklog.net   (CNAME to cloudfront). Static asset origin domain name:   origin.contentdeliverynetworklog.net . Custom origin IP address for both static/dynamic assets:   75.126.153.203 Caching ruleset for your dynamic and static assets: I am going to use a combination of Batca...
8 comments
Read more