Visual Studio 25th Anniversary!! I have used Visual Studio for 25 years!!

Time flies!

It is Visual Studio 25th Anniversary. It also means that I have worked on Visual Studio for 25 years too. (Oh no, getting old so fast…… from a young kid to an old man…)

[1997] I learn NT3.51 and VB during my last year on my bachelor degree study. I graduated from my bachelor degree. I still remember that I learn VB5 with VS1997 in my first job in a software company which is a Microsoft Certified Partner.

 

[1999] Then I start using VS 6.0 for VB6, Traditional ASP, and also using Visual SourceSafe.

 

[2000] Then I start building .NET application from VS.NET beta. At the same time, I heard from Microsoft .NET team saying that .NET will be last for at least 10 years, from 2000 to 2010. It will be the first language to do all the Web Development and Win Development in same preferred programming language.  Microsoft introduce C# at the same time. I choose staying in VB.NET as I have VB background. Start developing some Web Services.

[2001-2003] I made friends with other local .NET developers and also local Microsoft MSDN team. We then formed a local community HK .NET User Group. At the same time, I participle a lot on Microsoft Forum HK and TW. I was then awarded to be Microsoft Community Star TW, then Microsoft Community Star HK, and then Microsoft MVP @TW on VB technology.

 

[2005] .NET Framework 2.0 released with VS2005. As being VB MVP and attended 3 times Global MVP Summit. We VB MVPs always complained that the sample code are in C# more than VB.NET in MSDN library. in the end of 2005, I started moving into C#. I could do VB.NET and C# at the same time.

 

[2006] I helped VB team to translate the hands on lab from C# into VB.NET.
Windows Workflow Foundation and Visual Basic .NET
My previous blog links:
Windows Workflow Foundation(WF) Hands-On Lab01 to Lab03 in VB2005
Finished the Translation on WF HOL Lab04 to VB2005

 

[2008] Microsoft introduced Entity Framework. We called it Database-First EDM.

 

[2010] With VS2010, I start learning and developing ASP.NET MVC. Microsoft released Silverlight, a web version of WPF. (at least I think so)

 

[2012] EF 4 released, now it supported Code-First EDM.

 

[2015] EF 6, Owin, OAuth, WebAPI…

 

[2017] MVC5, Dependency Injection, .Net Core…

 

[2019] .NET Core 3

 

[2022] .NET core and .NET Framework now becomes .NET, starting from .NET 5. With this version, the experience on windows app development is not good as in VS2019. Specially right after I stopped the debugger.

 

Now, you could also download this special VS 25th Anniversary Theme Pack. Don’t wait, get it and try it.

 

 

 

 

 

 

Renew Your Microsoft Certification for free

Microsoft role-based and specialty certifications expire every year, unless renewed. You can renew a Microsoft certification by simply passing the online renewal assessment on Microsoft Learn. Certification renewal is designed to promote continuous learning and help you keep up with technology updates. Renewal content covers technology updates only, making it shorter and less time consuming. Renewal is free, and the process doesn’t involve taking an exam with Pearson VUE. Learning modules are available to help you prepare for renewal. You can renew any time at your convenience soon after the renewal window opens, approximately six months prior to certification expiration.

I know about this “Certification Renewal” for long time. I have a lot of questions in my mind which I don’t know the answers because I haven’t really experience it. Some questions like,

  1. how long does it take?
  2. how many times I could take?
  3. what happen if I fail?
  4. Is it very hard?
  5. Is it online test?
  6. Do I need to reserve a time slot like the general Pearson VUE exam?
    …etc

Few days ago, I received an email from Microsoft Certification like this,

And then it redirect me to Microsoft Learn portal and the page state that I still have 180 days before it is expired. I could take the online exam every day. After a fail result, I will need to wait 24 hours before I could take the second time.

In the first time, I failed. It then shows my score. And it also suggests me some Microsoft Learn links and ask to you learn from it. After spending some time to read all of them, I finally passed the exam. Yes, passed and the certificate is now extend for another year to 17th July, 2023.

Visual Studio 2022 (v17.0) Preview 1.1

In the past, I have blog that VS2022 Public Preview will be released in the summer time. It has been released and you could download and try it now.

On 17th June, 2021, VS Team has released VS2022 Preview 1.0.
Yesterday (24th June, 2021) VS Team released, VS2022 Preview 1.1.

The only issue addressed in Preview 1.1 on top of the Preview 1.0 is,

  • Fixed an issue causing Test Explorer to run very slow

What’s New in Preview 1.0?

  • Devenv.exe is now 64-bit
  • .NET 6 SDK (preview) is included in VS2022 Preview 1.0
  • New Git experience
  • …More

Some features are not yet ready in this preview 1.0/1.1

  • Web Live Preview
  • Instrumentation profiler
  • Azure Cloud Service project support
  • T-SQL debugger
  • Web Load Test and TestController/TestAgent
  • Azure DataLake
  • Coded UI Test
  • DotFuscator
  • Incredibuild IDE integration
  • IntelliCode find and replace by example

 

Try the Preview now

More Detail: Microsoft Official Site – Visual Studio 2022 Preview

Next version of Visual Studio, “VS2022”, Public Preview will be released this summer

Amanda Silver, CVP of Product-Developer Division announce that the next version of Visual Studio will be called VS2022. And its Public Preview will be available to download this summer. Let me do a short summary about the changes and share with you.

  • IDE will be running faster
    • VS2022 will be in 64-bit
  • New Design
    • Better clarity, legibility, and contrast
    • Cascadia Code
    • Personalization, you could make your own “IDE” just right for you.
  • Develop Modern Apps
    • Azure, better integration with GitHub for CI/CD, and with Azure
    • VS2022 will have full support for .NET 6.
    • .NET Multi-platform App UI (MAUI) will be included. You could build client apps on Windows, Android, macOS, iOS. You could also use ASP.NET Blazor for Web App.
  • Innovation 
    • Performance improved for Diagnostics and Debugging
    • Using Live Share to enable Real-Time Collaboration
    • AI IntelliCode engine provide more and deeper integrations into your daily workflows.
    • New support for Git and GitHub.
    • Improved Code Search
    • refreshing VS for Mac

Well, let’s wait and test this new VS2022 in the coming summer time.  Meanwhile, you could read from the original post here.

Enable TLS 1.2 or above on your ASP.NET Web App or WebAPI

The Transport Layer Security (TLS) 1.2 is a stadnard that provides security improvements over previous versions. More and more thrid-party APIs were configured to disable any requests from clients that were using TLS 1.0/1.1. So if your ASP.NET Web App or WebAPI Services Web Site will need to update to TLS 1.2 as well if your ASP.NET Web App or WebAPI Services Web Site has some calls to the third-party APIs, otherwise they will only return empty responses.

You could disable TLS 1.0/1.1 and only enable TLS 1.2 in your Web Server or in Azure, so that your hosting environments will no longer accept requests from earlier version of TLS.

But what happens on your application (ASP.NET Web App or WebAPI Services)? Depend on what version of .NET framework your project usrs will dicate the possible solutions available to you.

  1. If your project compiles against .NET Framework 4.7 or above, then you don’t have to do anything.
  2. If your project has been developed in a earlier version of .NET Framework, then you could either
    1. Recompile your project using .NET Framework 4.7 or above
    2. If recompiling is not an option, then you will have to update your .config file as below,
<configuration>
  <runtime>
    <AppContextSwitchOverrides value="Switch.System.Net.DontEnableSystemDefaultTlsVersions=false"/>
  </runtime>
  <system.web>
    <compilation targetFramework="x.y.z" />
    <httpRuntime targetFramework="x.y.z" /> 
  </system.web>
</configuration>

It is preferred that x.y.z are the same. So if your application is 4.6.2, then replacing x.y.z into 4.6.2.

Microsoft also has post a useful document on describing the best pratices to TLS 1.2. It will be great if you could read them all and understand them in order to fully secure your application(ASP.NET Web App or WebAPI Services).
https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls