Windows Server 2012 and .NET FW 2.0: do they fit together? - winforms

Do you know if Windows Server 2012 can run .NET Framework 2.0 applications?
So far I tried to install .NET framework 2.0 (for running an application that's based on this version) but it fails.
Microsoft website informs that WS 2012 includes .NET FW 4.5 or 4.5.1 but does not say about .NET 2.0
Do you know?
Thank you

Yes it does, but you have to install the feature.
Click the start button, type Windows Features and click Turn Windows features on or off. That should bring up the Server Manager and automatically after a second or two bring up the "Add Roles and Features Wizard." Click next until it gets to Features. Check the box at the top that says ".NET Framework 3.5 Features." This includes .NET 2.0 and 3.0.

Related

Windows Forms (.NET Core) is missing in the Visual Studio Community 2019

I have a problem which I struggle for 3 days. It seems that my Visual Studio Community 2019 doesn't want to recognise the ".Net core" for Windows Forms. I even install it manually (downloaded from Microsoft - .NET Core 3.1 SDK) but doesn't help. I used this blog Microsoft blog. They said that I have to install " Windows Forms .NET Core Designer VSIX package" because "it isn’t yet bundled with Visual Studio", but there is no link to download. I don't have ".NET Core" in "Project solutions" and "Visual Studio Installer" (I cannot download it from the installer). The version of VSC 2019 - 16.8.2
SS:
Installer
Project Picker
Installer2
Settings
So I had the same problem and yes you can't find .NET core windows form directly to open windows form that support windows form you will need to first open non .NET framework windows from app there you can select if you want core which version.
Windows Form Application
Selecting Desired Framework
You'd have to select Windows Forms App (.Net) from the available project types and that will open up as the latest .NET core Windows Froms.

Is "Click Once" supported for .Net Core WPF?

What is the correct pattern/ what packages to use for WPF click once deployment in .net core 3.0( earlier versions are okay too)?
I am currently migrating a WPF app from netframework 4.8 to .net core 3.0. I have been using click once deployment in in the previous version. I was using System.Deployment package which is not supported in .net core. Is there any substitution for the package and what is the correct way to implement click once deployment in .net core and is it even possible? Should it be done using MSIX, if so is there any good guide about MSIX click once deployment?
Support for ClickOnce is now available in .NET Core 3.1 and higher (you need Visual Studio 2019).
Source Microsoft Docs:
Starting in Visual Studio 2019 version 16.8, you can use the Publish tool to publish .NET Core 3.1, or newer, Windows Desktop applications using ClickOnce from Visual Studio

Patch update of Microsoft .Net Framework 4.6.1(KB4040973) causing issue in the WPF Combobox

Our application was created using WPF with .Net framework 3.5 and that rendering in the Internet Explorer. In my office, yesterday(20-SEP-2017) patch got updated for the laptop and that shown in the below.
Update for Microsoft Windows (KB4040980)
Security Update for Microsoft Windows (KB4040966)
Security Update for Microsoft Windows(KB4038779)
Security Update for Microsoft Windows (KB4036586)
Update for Microsoft Windows (KB4019990)
Update for Microsoft .NET Framework 4.6.1 (KB4040973)
Security Update for Microsoft .NET Framework 4.6.1 (KB4040957)
Prior to this update, the data to combobox was showing correctly and after this update combo box value is displayed briefly then disappeared.
In one of our servers still, this patch didn't get updated so that we can see the correct value in the combo box.
Tried:
uninstall 4.6.1 frameworks update - didn't work
Installed 4.6.1 frameworks from Microsoft site- didn't work
Installed 4.6.2 frameworks from Microsoft site- didn't work
Please provide suggestion/fix to overcome this issue.
Since KB 4041083 / KB 4040973 (Security and Quality Rollup for the .NET Framework 3.5.1, 4.5.2, 4.6,
4.6.1, 4.6.2, and 4.7 for Windows 7 SP1 and Windows Server 2008 R2 SP1:
September 12, 2017) was installed rendering no longer works and I end up with a blank image.
This only seems to be a problem when running in a service and not when running via a windowed application.
KB 4041083 / KB 4040973 has broken WPF Rendering in Services
Rendering issues after the September 12, 2017, .NET Security and Quality Rollups are installed

Do I need 4.5 hosting for a Visual Studio 2012 project?

Do I need 4.5 hosting for a Visual Studio 2012 project? I am using 2012 SQL Server as well. Does this require 4.5 framework for hosting?
It depends on the settings of your project. In VS2012, in the Project --> Properties dialog, you can set the target framework version. Depending on what you're doing you may or may not need the full 4.5 framework.
No you do not require .NET 4.5 - You can choose what version of the framework you need by going to Project -> Properties. SQL Server seems to rely only on .NET 4 (NOT .NET 4.5)
No, unless your project is using .NET Framework 4.5

Is there a CLR profiler that works with .NET 3.5 SP1 and WPF?

In all of my searching, I've only been able to find this one link that suggests the old CLR Profiler for .NET 2.0 should work with .NET 3.0 or 3.5 applications.
When I try and profile my .NET 3.5 SP1 WPF application with the CLR Profiler for .NET 2.0 it starts up my application just fine, but it throws up a dialog that says "Waiting for application to start common language runtime".
Since my application clearly uses the CLR, I can only conclude that the CLR Profiler for .NET 2.0 does not work with newer versions of the framework (maybe it's just a problem with 3.5 SP1 apps).
So, does anyone know if there is a version of the CLR profiler that works with 3.5 SP1? If there isn't a version of Microsoft's profiler, is there another free profiler that I could use that has similar functionality?
I just tried running CLR Profiler with a WPF application, and it works fine. It takes a while for the application to start (longer than with non-WPF applications, it feels like), but it works.
Update: just to keep the answer up to date; according to the comments below, the solution was to run the CLR Profiler with administrative rights.
CLR Profiler 4 is released by microsoft on Jan 31, 2011.
This version supports .NET frameworks 2.0 to 4.0 as well as support for WPF and Silverlight.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=be2d842b-fdce-4600-8d32-a3cf74fda5e1
Note that it requires .NET framework 4.
Regards
The CLR used in 2.0 framework and 3.5 framework differs only by a service pack. The CLR has the version 2.0 and 2.0SP1 for the respective versions. The CLR profiler will work against the 2.0SP1 version of the CLR.
Small Correction: There is no 3.5 version of the CLR. The most recent versions are 2.0, 2.0SP1 and 2.0SP2 (associated with .Net Framework SP1).
I've just used the CLR profiler 2 with my .NET 4.0 WPF application. It could launch the App but when click on "Show Heap Now" or any items under "View" menu it showed report windows with empty figures. So I wonder if anyone already tried it successfully? Or it is just not supports for .NET WPF apps.
I made the mistake of running the x86 version of CLR Profiler for .NET Framework 2 on my 64-bit machine, which just showed the "Waiting for application to start common language runtime" message permanently. If you have a 64-bit machine, you probably have to run the version of CLR Profiler that matches the process you want to profile (i.e. normally the one in the "x64" folder)
For some reason WPF is extremely slow under the profiler.
Don't make the stupid mistake I did and try to use CLR profiler v1.1 – the correct one is CLR Profiler for .NET Framework 2.0 (even if you use .NET 3.5).

Resources