We are considering writing the next version of the project using .Net 3, but we are wondering if we can take a hit on forcing end users to install .net framework version 3.
If you want to make sure that you are using only .NET 2.0 compatible functionality, you only need to use .NET 2.0 assemblies. Then you know your safe and healthy sound.
This article by Jean-Baptiste Evain explains how you can use C # 3.0 and LINQ and targeting machines that only have .NET 2.0 installed runtimes.
System.Core Mono, MIT/X11.
.NET 3.0 is a bad name for some of the new libraries: WPF, WCF, Workflow, and InfoCard. The CLR is still version 2.0, ASP.NET is still version 2.0, and Windows Forms is still version 2.0.
In development, .NET 3.0 was called WinFX.
Source: https://habr.com/ru/post/1697295/More articles:Play ZX Spectrum AY-3-8912 in XNA Game Studio - xnaflex client webservice - flexhttps://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=https://fooobar.com/questions/1697292/shut-down-script-on-windows-to-delete-a-registry-key&usg=ALkJrhh7Exly7ysQBlRTLnqG2OeYrogijACan .Net 3.5 applications run on machines running .Net 2.0 runtime? - .netКак определить, когда больше нет данных для чтения в NetworkStream? - c#php: output [] w / join vs $ output. = - phpКак установить маскированный пакет в Gentoo 2008? - installsource control with VB2005 Express - version-controlSeparating C # class into header and .cs file - c #Search for regular expression patterns in a 30 GB XML dataset. Using 16 GB of memory - javaAll Articles