New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET Framework 4.7 Feedback #393
Comments
The DirectX requirement on server was quite surprising to us, just as an FYI: this will delay or prevent the install at Stack. That ship has sailed, so there's nothing to be done, but I'm providing the feedback in case it's useful. |
Does this mean we can now use D3DImage without having to interop with DirectX 9? Or are you still forcing everyone to go through DirectX 9 for backwards compatibility? Any documentation updates or blog posts on that? Besides the fix for a memory leak on D3DImage I can't find anything on that topic in the release notes. |
@weltkante The new DirectX dependency is very targeted so it will not help with that scenario. Will pass on the feedback. |
From release notes: "JIT performance improvements [223169]" |
Can we target this from VS2015 or will it require 2017? |
Windows 10 Creators Update (and therefore I'm assuming NET Framework 4.7) has broken my ASP.NET site running on Sitefinity (somewhat old - 8.0.5710). Is there any way to downgrade .NET Framework (uninstall 4.7) in Windows 10? I've tried a lot of things and the site throws an error in Cassini, IIS and IIS Express. I ran out of ideas what could be wrong after a good few days of investigating and decided to spin up a VM without Creators Update. Installed IIS and deployed the site, which was working. I then installed Creators Update and right after the installation launched the site. Here's what I get: An item with the same key has already been added. Exception Details: System.ArgumentException: An item with the same key has already been added. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [ArgumentException: An item with the same key has already been added.] [TypeInitializationException: The type initializer for 'Telerik.Sitefinity.Security.SecurityManager' threw an exception.] [HttpException (0x80004005): The type initializer for 'Telerik.Sitefinity.Security.SecurityManager' threw an exception.] Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.2046.0` This looks like a config parsing issue but I am out of ideas where to look next and how to pinpoint the exact problem? |
@lstyles It was Telerik Sitefinity who blowed, so you should contact its vendor. I think there is no way to downgrade .NET Framework 4.7 once you upgraded your Windows 10 installation. Telerik should be able to locate the cause and give it a fix. |
@lextm Thanks. I've got a support case open with Telerik. I'm just bit stuck especially that Telerik couldn't have predicted what changes .NET Framework 4.7 will bring when they were writing the version I'm using, 2 years ago. Does it often happen that new version of .NET breaks existing applications? |
I upgraded an existing WPF app to .net 4.7 and whereas before I was able to paste large amounts of text into a WPF textbox, after the upgrade to .net 4.7 once I paste a large text string (2,700+ characters) the entire application pauses. Task Manager doesn't show the process as Not Responding, it just shows a bunch of CPU activity as if the program is just stuck in an infinite loop or something. No other change to the application, just flipping it to .net 4.7 (and removing the ValueTuple nuget package). Run it on .net 4.6? Perfect. Run it on .net 4.7? The app dies and the process must be killed. This is bad.
|
@lstyles Did you find out what was causing the error? Was it really the upgrade to 4.7 that caused it? I am experiencing the same issue. |
@aynefd I don't know. Telerik/Progress have released a hotfix to all Sitefinity versions they support, so for me the problem has been resolved. I am not sure what changed in the framework that caused it. |
@jonoallen I cannot repro your problem - paste a string of length 10,000 into a textbox works instantaneously. Thread 1 Grid.ResolveStarMaxDiscrepancy suggests the problem might be in Grid layout, rather than in textbox. You can probably build a simple repro by extracting your textbox and the Grid(s) surrounding it, together with dummy content for the other cells in the Grid(s). Please share such a repro (file a bug at http://connect.microsoft.com, if necessary). |
@SamBent Take a look at https://github.com/935main/DotNet47Test and you can re-produce the behavior. |
@jonoallen Thanks, the problem is definitely in Grid layout (nothing to do with TextBox). Your grid has two rows declared with MinHeight=50, MaxHeight=100. When the first row's MinHeight (plus other rows with fixed or Auto height) already exceeds the available height, the new grid layout algorithm mistakenly tries to re-allocate the second row and gets into an infinite loop. See System.AppContext for details about setting app-context switches. |
This change for Windows Forms:
causes a changed/ugly look for some existing applications. Refer to this SO question for a screenshot. |
@bbarry You can target the .NET Framework 4.7 with Visual Studio 2015. Get the developer pack: https://www.microsoft.com/net/targeting |
@chm-tm, We are reverting header color to InactiveBorder in the default windows theme in the next release of the .Net Framework, which most likely will be included in the Windows 10 Fall Creators Update. The reason this change was introduced, was that the foreground and background colors were not contrasting enough in one of the High Contrast themes, this is why we are reverting to the previously used color only in the default theme. |
Hello, As most of our clients switched to Windows 10 Creators Update it was noticed that our app became slow and sluggish. I'm talking slow response to mouse clicks and scroll, and the thing gets worse when the number of active controls and forms increases. Now, I've tried profiling the app and didn't notice anything unusual, most of the time is spent on drawing text inside WinForm controls and forms. We've isolated the problem to .NET Framework 4.7 because older Win10 versions started behaving the same way upon installing NET 4.7 via automatic updates. The issues were gone by manually uninstalling the update, but there is no way of doing so (uninstalling net 4.7 manually) in Creators Update. Our application is quite old and we use WinForms, targeting .NET 4.5.1 atm. I've tried retargeting all modules to .NET 4.7 but the issue remains. There is a (closed) thread on stack, describing the similar issue. Anyone having a clue what the heck is going on? |
@urosjovanovic, can you share some specifics of your WinForms app? Are you using 3rd party controls. Would it be possible to share a sample WinForms project, that exhibits this issue? |
@NikolaMilosavljevic
The key is this: If this is removed or moved outside of the loop everything runs smooth. Luckily, there is only a couple of references to Screen.FromControl in our solution. Since this worked flawlessly on Win10 Anniversary without .NET 4.7, I suppose that the new .NET framework run-time embedded in Win10 Creators Update has to do something with this changed behavior. The weird thing is that CPU profiling didn't show any significant change in elapsed ticks between .NET 4.6 and .NET 4.7 for this command but the choppy performance is really evident in UI while using the app. This is tested and verified on at least 10 machines in our company. Just to be clear I am strictly talking about .NET 4.7 run-time, our app is still targeting 4.5.1 but changing it to 4.6 or 4.7 has no effect on this issue. |
@urosjovanovic |
@NikolaMilosavljevic |
@urosjovanovic Official patches for Windows 10 creators Update that take care of bug in Screen constructor are available here: |
OS Version = 10.0.14393, SP = 0.0, Platform 2 |
I am closing this issue now. Please create specific issues for problems you find. |
Pretty sure that if Microsoft "upgrades" something it just means a couple weeks of development time wasted before downgrading back to the "un-upgraded" version. Too bad we can't harness all the MS development time and awesome MS developer capabilities for more useful work. What terrible stewards of their "leadership" position. |
Please share your feedback using the .NET Framework 4.7.
See the release notes for more information: https://github.com/Microsoft/dotnet/blob/master/releases/net47/README.md
The text was updated successfully, but these errors were encountered: