[et_pb_section fb_built=”1″ fullwidth=”on” admin_label=”Hero Section” _builder_version=”4.22.0″ background_color=”#00A4E8″ background_image=”https:\/\/opinity.nl\/wp-content\/uploads\/2023\/07\/Opinity_header-2000×1400-1.webp” background_position=”bottom_right” background_blend=”luminosity” custom_padding=”|||” global_colors_info=”{}”][et_pb_fullwidth_header title=”.NET 8: to update or to not update?” button_one_url=”#Ready” content_max_width=”900px” _builder_version=”4.24.2″ title_font=”Raleway|700|||||||” title_font_size=”50px” title_line_height=”1.4em” content_font=”Poppins||||||||” content_font_size=”16px” content_line_height=”1.8em” subhead_font=”Poppins|600||on|||||” subhead_letter_spacing=”4px” subhead_line_height=”1.8em” background_color=”rgba(126,190,197,0)” custom_button_one=”on” button_one_text_size=”14px” button_one_bg_color=”#00A4E8″ button_one_border_width=”12px” button_one_border_color=”#00A4E8″ button_one_letter_spacing=”2px” button_one_font=”Poppins|600||on|||||” button_one_icon=”$||divi||400″ custom_button_two=”on” button_two_text_size=”14px” button_two_text_color=”#29cb8b” button_two_bg_color=”#ffffff” button_two_border_width=”12px” button_two_border_color=”#ffffff” button_two_letter_spacing=”2px” button_two_font=”Poppins|600||on|||||” button_two_icon=”$||divi||400″ custom_padding=”100px||100px||true” title_font_size_tablet=”40px” title_font_size_phone=”30px” title_font_size_last_edited=”on|desktop” content_font_size_last_edited=”off|desktop” subhead_font_size_tablet=”40px” subhead_font_size_phone=”30px” subhead_font_size_last_edited=”off|desktop” button_one_letter_spacing_hover=”2px” button_two_letter_spacing_hover=”2px” global_colors_info=”{}” button_one_text_size__hover_enabled=”off” button_two_text_size__hover_enabled=”off” button_one_text_color__hover_enabled=”off” button_two_text_color__hover_enabled=”off” button_one_border_width__hover_enabled=”off” button_two_border_width__hover_enabled=”off” button_one_border_color__hover_enabled=”off” button_two_border_color__hover_enabled=”off” button_one_border_radius__hover_enabled=”off” button_two_border_radius__hover_enabled=”off” button_one_letter_spacing__hover_enabled=”on” button_one_letter_spacing__hover=”2px” button_two_letter_spacing__hover_enabled=”on” button_two_letter_spacing__hover=”2px” button_one_bg_color__hover_enabled=”off” button_two_bg_color__hover_enabled=”off”][\/et_pb_fullwidth_header][\/et_pb_section][et_pb_section fb_built=”1″ custom_padding_last_edited=”off|desktop” admin_label=”About Section” _builder_version=”4.22.1″ background_color=”#000000″ module_alignment=”right” custom_padding=”80px||80px||true|false” custom_padding_tablet=”||120px|” global_colors_info=”{}”][et_pb_row column_structure=”1_4,3_4″ _builder_version=”4.16″ custom_margin=”||50px|” custom_padding=”60px|0px|60px|0px|true|false” border_color_all=”rgba(0,0,0,0.12)” border_width_bottom=”2px” global_colors_info=”{}”][et_pb_column type=”1_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_image src=”https:\/\/opinity.nl\/wp-content\/uploads\/2024\/03\/markus-winkler-cxoR55-bels-unsplash-scaled.jpg” title_text=”markus-winkler-cxoR55-bels-unsplash” _builder_version=”4.24.2″ always_center_on_mobile=”off” global_colors_info=”{}”][\/et_pb_image][\/et_pb_column][et_pb_column type=”3_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text ul_type=”circle” ul_position=”inside” _builder_version=”4.24.2″ text_font=”Poppins||||||||” text_font_size=”16px” text_line_height=”2em” ul_font=”Poppins||||||||” ul_line_height=”2em” header_font=”||||||||” header_3_font=”Raleway|700|||||||” header_3_font_size=”24px” header_3_line_height=”1.4em” background_layout=”dark” max_width=”750px” custom_margin=”|||” locked=”off” global_colors_info=”{}”]<\/p>\n
My .NET journey began back in 2014, just a few months after .NET Core 1.0 was released. Seven years in, and we\u2019ve now reached version 8: without the \u201cCore\u201d in the name. Recently, my client asked me: \u201cAre we going to upgrade our backend to .NET 8? And if so, why or why not?\u201d<\/p>\n
In this blog post, I\u2019ll walk you through the considerations I made when answering that question, highlighting the key differences between .NET 8 and .NET 7 along the way.<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row column_structure=”3_4,1_4″ _builder_version=”4.24.2″ global_colors_info=”{}”][et_pb_column type=”3_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text ul_type=”circle” _builder_version=”4.24.2″ text_font=”Poppins||||||||” text_font_size=”16px” text_line_height=”2em” ul_font=”Roboto Mono||||||||” ul_line_height=”2em” header_font=”||||||||” header_3_font=”Raleway|700|||||||” header_3_font_size=”24px” header_3_line_height=”1.4em” header_4_font=”|700|||||||” header_4_font_size=”16px” header_4_line_height=”1.4em” background_layout=”dark” max_width=”750px” custom_margin=”||50px|” global_colors_info=”{}”]<\/p>\n
Personally, I\u2019m a strong advocate for embracing change and updates. Adapting to something new is often just a matter of time and it brings a welcome sense of renewal. This may sound a bit blunt, but staying open to change makes you more adaptable and better equipped to adjust when needed. <\/p>\n
There are always people who hesitate to upgrade, pointing to early bugs or potential security risks. So they wait: \u201cLet\u2019s revisit this in a few months.\u201d But let\u2019s be honest\u2014postponing often turns into never. And if there are still issues now, are you just going to delay it again? <\/p>\n
Staying current with updates doesn\u2019t have to be a huge effort \u2014 unless you let them build up. That applies even to large platforms. Wait too long, and you\u2019ll often find that parts of your application need to be rebuilt. In the worst case, the whole thing needs replacing. That\u2019s a much bigger problem than just staying on top of things. <\/p>\n
[\/et_pb_text][et_pb_text ul_type=”circle” _builder_version=”4.24.2″ text_font=”Poppins||||||||” text_font_size=”16px” text_line_height=”2em” ul_font=”Roboto Mono||||||||” ul_line_height=”2em” header_font=”||||||||” header_3_font=”Raleway|700|||||||” header_3_font_size=”24px” header_3_line_height=”1.4em” header_4_font=”|700|||||||” header_4_font_size=”16px” header_4_line_height=”1.4em” background_layout=”dark” max_width=”750px” custom_margin=”||50px|” global_colors_info=”{}”]<\/p>\n
Beyond the \u201cto update or not to update\u201d philosophy, it\u2019s also worth taking a closer look at the new features that come with an update. In this post, I\u2019ll focus on the features Microsoft itself highlights, to better understand the direction they\u2019re heading in. Since there are too many to cover here, I\u2019ve selected a few. <\/p>\n
[\/et_pb_text][\/et_pb_column][et_pb_column type=”1_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_team_member name=”Noah Steijlen” position=”.NET Developer” image_url=”https:\/\/opinity.nl\/wp-content\/uploads\/2024\/03\/Noah-profielfoto.jpg” _builder_version=”4.24.2″ _module_preset=”default” header_text_color=”#00A4E8″ background_layout=”dark” global_colors_info=”{}”][\/et_pb_team_member][\/et_pb_column][\/et_pb_row][et_pb_row column_structure=”1_2,1_2″ _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”1_2″ _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][et_pb_blurb title=”Performance Improvements” use_icon=”on” font_icon=”||fa||900″ icon_color=”#00A4E8″ icon_placement=”left” _builder_version=”4.24.2″ _module_preset=”default” header_text_color=”#FFFFFF” border_radii_image=”on|1px|1px|1px|1px” global_colors_info=”{}” custom_padding=”||0px|||”]<\/p>\n
What\u2019s not to love? Performance across the board is up in .NET 8. Based on my own benchmarks and tests from other devs, we\u2019re looking at an average of 30% improvement. That really adds up when you think about the amount of LINQ queries your app runs. A great reason to upgrade.<\/p>\n
[\/et_pb_blurb][et_pb_blurb title=”Native AoT” use_icon=”on” font_icon=”||fa||900″ icon_color=”#00A4E8″ icon_placement=”left” _builder_version=”4.27.4″ _module_preset=”default” header_text_color=”#FFFFFF” hover_enabled=”0″ border_radii_image=”on|1px|1px|1px|1px” global_colors_info=”{}” custom_padding=”||0px|||” sticky_enabled=”0″]<\/p>\n
For those unfamiliar with it: AoT (Ahead-of-Time) compilation translates your .NET code directly into machine code. This differs from JIT, where source code is first compiled into IL (Intermediate Language) and then translated into machine code at runtime.<\/p>\n
With .NET 8, the file size of AoT applications has been reduced by approximately 40% compared to .NET 7. In addition, .NET 8 now supports all Apple platform architectures (macOS and iOS), as well as Android (x64 and Arm64). This is intresting, because it shows Microsoft\u2019s commitment to broad .NET support \u2014 and they\u2019re making strong progress.<\/p>\n
<\/p>\n
[\/et_pb_blurb][\/et_pb_column][et_pb_column type=”1_2″ _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][et_pb_blurb title=”.NET Aspire” use_icon=”on” font_icon=”||divi||400″ icon_color=”#00A4E8″ icon_placement=”left” _builder_version=”4.24.2″ _module_preset=”default” header_text_color=”#FFFFFF” border_radii_image=”on|1px|1px|1px|1px” global_colors_info=”{}” custom_padding=”||0px|||”]<\/p>\n
This is a new solution introduced with .NET 8. Aspire helps streamline your development experience for cloud applications. How? By simplifying the management of multi-project applications and running them within shared environments. This can significantly help you bring clarity and consistency to your application landscape. Aspire may be new, but it already offers promising features \u2014 enough to deserve a blog post of its own.<\/p>\n
[\/et_pb_blurb][et_pb_blurb title=”AI Integration” use_icon=”on” font_icon=”||divi||400″ icon_color=”#00A4E8″ icon_placement=”left” _builder_version=”4.24.2″ _module_preset=”default” header_text_color=”#FFFFFF” border_radii_image=”on|1px|1px|1px|1px” global_colors_info=”{}” custom_padding=”||0px|||”]<\/p>\n
With .NET 8, Microsoft introduces support for AI plugins and tooling, including seamless integrations with Azure. Since the global rise of ChatGPT, the capabilities of AI have become more widely understood. Needless to say, support for these innovations speaks for itself.<\/p>\n
[\/et_pb_blurb][\/et_pb_column][\/et_pb_row][et_pb_row column_structure=”1_3,2_3″ _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”1_3″ _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][et_pb_image src=”https:\/\/opinity.nl\/wp-content\/uploads\/2024\/03\/manuel-cortina-gAcKfakUSNM-unsplash-scaled.jpg” title_text=”manuel-cortina-gAcKfakUSNM-unsplash” _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][\/et_pb_column][et_pb_column type=”2_3″ _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.24.2″ _module_preset=”default” text_text_color=”#FFFFFF” header_2_text_color=”#FFFFFF” global_colors_info=”{}”]<\/p>\n
Safe to say, Microsoft is pushing forward on several fronts. From new solutions for cloud application management, to broader platform support for native .NET applications, and the integration of AI capabilities. I’m curious to see what they\u2019ll bring next.<\/p>\n
All in all, I\u2019ve recommended my current client to proceed with the upgrade, as the improvements in performance and usability offered by the new features are substantial.<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"
My .NET journey began back in 2014, just a few months after .NET Core 1.0 was released. Seven years in, and we\u2019ve now reached version 8: without the \u201cCore\u201d in the name. Recently, my client asked me: \u201cAre we going to upgrade our backend to .NET 8? And if so, why or why not?\u201d In […]<\/p>\n","protected":false},"author":9,"featured_media":0,"parent":1171,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","content-type":"","footnotes":""},"class_list":["post-1210","page","type-page","status-publish","hentry"],"yoast_head":"\n