Are there any potential drawbacks to using DotNetNuke 5.4 with ASP.NET 4.0 vs. ASP.NET 3.5?
The only real big risk at the moment would be with third-party components that might not have been tested/validated with the .NET 4.0 runtime.
Related
I want to develop a general project, the desktop application must be .Net Framework and I will use EF Core 5.0 in the background and the libraries must be .net standard so that they are compatible with xamarin and Asp.net Core. Everything is fine, but the net framework does not support 2.1. How do I overcome this problem?.
NET 5.0 desktop toolbox has problems. I am someone who uses Devexpress and it does not come out in vehicles. I asked Devexpress and they said they have microsoft-side problems. I didn't know what to do. Syncfusion components do not look the same, unfortunately :(
You have to develop Winforms application using .NET 5. It is replacement of .NET Framework which become deprecated.
https://learn.microsoft.com/en-us/dotnet/desktop/winforms/?view=netdesktop-5.0
I am using Asp.Net Core to write API Layer for one of my legacy application developed using WPF (.Net Framework 4.5). I have used https://www.nuget.org/packages/Microsoft.Extensions.DependencyInjection/ in Business layer which I want to access from WPF application. The version of this DI is not supported by .Net Framework 4.5 so I am unable to use it from WPF. Any suggestions how should I go with this ? The other approach is to use anyother DI container supported by .Net framework 4.5 and Asp.Net Core
I have upgraded my WPF project to .Net Framework 4.6 and rest of the layers are created using .Net Standard Library 2.0.
I have a standard WPF application developed in .Net framework 4. Now, my client wants a website which I am planning to develop using .Net Core. In order to share the business logic, I need to move the database along business layer to a separate project and here I am planning to use .Net Core. So, all the layers i.e. Data/ Business/ API will be re-written using latest version of .Net Core.
Would I be able to reference business layer written in .Net Core from WPF (.Net Framework 4) project?
Any pointers will be highly appreciated.....
You should implement the common functionality in a .NET Standard library. You will then be able to reference this assembly from all apps that are compatible with the version of the .NET Standard that your common project targets.
The various .NET implementations target specific versions of .NET Standard and the following table on MSDN lists all versions of .NET Standard and the platforms supported: https://learn.microsoft.com/en-us/dotnet/standard/net-standard.
The latest version of .NET Core (currently 2.0 at the time of writing) implements .NET Standard 2.0. The oldest version of the .NET Framework that implements .NET Standard 2.0 is 4.6.1. This means that your WPF app should target 4.6.1 to be able to consume a .NET Standard 2.0 assembly.
.NET Core 1.0 and .NET Framework 4.5 support .NET Standard 1.0.
The .NET Framework 4.0 doesn't support any version of .NET Standard though so you should re-target your WPF app against (at least) .NET Framework 4.5.
Would I be able to reference business layer written in .Net Core from WPF (.Net Framework 4) project?
The answer is yes. You can try it: In Visual Studio create a WPF application project and a .NET Standard library project and then add a reference from the application project to the library project.
There will be NuGet packages that you cannot reference in your .NET Standard project because they only support full .NET Framework but most popular NuGet packages can be referenced from a .NET Standard project. Your question is also tagged [entity-framework-6]. If you want to use Entity Framework from a .NET Standard project you will have to use Entity Framework Core as Entity Framework 6 requires the full framework.
You should probably create a quick spike to determine if you can build your application how you intend to.
A set of UserControls I've developed for in-house use were written in .NET 2.0 but my current development is in .NET 3.5. Assuming the following:
no need to update these controls in my 2.0 projects
there are no 3.5 features I need in my library
Is there any advantage at all (beyond satisfying a misplaced sense of tidyness) for me to update my control library to 3.5?
I believe even if a machine using my controls doesn't have the .NET 2.0 runtime installed, my library will run fine if it has the 3.5 runtime.
The only reason to bring them to 3.5 would be the tidiness concern. Otherwise they will work just fine with .NET 3.5 in every other aspect. Keep in mind that 3.0 and 3.5 were library extensions to 2.0. I.e. They run top of 2.0. (Things changed with 4.0 however.)
I wrote an application using RIA services in a .net 4.0 project that used domain services to communicate with a client-side Silverlight 4 application. By the way this is my first data driven Silverlight.
I just found out that I will need to make it run in a MVC2 project running .net 3.5 on the server.
Is it possible to make RIA services work in 3.5?
If not, what would be the best way to recreate the project in 3.5?
Unfortunately this scenario is not going to work. Your choices are either host the server on .NET 4.0 or backport with .NET 3.5, SL3 and Beta2 of RIA Services.