.NET Framework 4.7 Feedback

[richlander]

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

[NickCraver]

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.

[weltkante]

The .NET Framework 4.7 now uses DirectX 11 components for WPF.

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.

[richlander]

@weltkante The new DirectX dependency is very targeted so it will not help with that scenario. Will pass on the feedback.

[IlyaGrebnov]

From release notes: "JIT performance improvements [223169]"
.NET folks could you please expand on what JIT improvements are in 4.7? Interesting to know.

[bbarry]

Can we target this from VS2015 or will it require 2017?

[lstyles]

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:
`Server Error in '/' Application.

An item with the same key has already been added.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

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.]
System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) +56
System.Collections.Generic.Dictionary2.Insert(TKey key, TValue value, Boolean add) +14643456 Telerik.Sitefinity.Configuration.ConfigElementDictionary2.Add(TKey key, TElement element) +194
Telerik.Sitefinity.Security.Configuration.SecurityConfig.LoadDefaults() +2235
Telerik.Sitefinity.Security.Configuration.SecurityConfig.OnPropertiesInitialized() +92
Telerik.Sitefinity.Configuration.ConfigSection.InitializeProperties() +27
Telerik.Sitefinity.Configuration.ConfigElement.EnsurePropertiesInitialized() +122
Telerik.Sitefinity.Configuration.ConfigElement.get_Properties() +21
Telerik.Sitefinity.Configuration.Data.XmlConfigProvider.LoadAttributes(ConfigElement element, XmlReader reader, ConfigPolicyHandler policyHandler, String policyName, UpgradingInfo upgradingInfo, Boolean isNew) +214
Telerik.Sitefinity.Configuration.Data.XmlConfigProvider.LoadElement(ConfigElement element, XmlReader reader, ConfigPolicyHandler policyHandler, String policyName, UpgradingInfo upgradingInfo, Boolean isNew, Boolean validateTagName) +198
Telerik.Sitefinity.Configuration.Data.XmlConfigProvider.LoadSectionFromReader(ConfigSection section, XmlReader reader, ConfigPolicyHandler policyHandler, String policyName, Boolean checkForUpgrade, UpgradingInfo& upgradingInfo) +240
Telerik.Sitefinity.Configuration.Data.XmlConfigProvider.LoadSectionFromFile(ConfigSection section, ConfigPolicyHandler policyHandler, String policyName, Boolean withUpgrade) +134
Telerik.Sitefinity.Configuration.Data.XmlConfigProvider.LoadSection(ConfigSection section, ConfigPolicyHandler policyHandler, String policyName) +72
Telerik.Sitefinity.Configuration.ConfigSection.Initialize(ConfigProvider provider, ConfigPolicyHandler policyHandler, String policyName, Boolean singlePolicy) +301
Telerik.Sitefinity.Configuration.ConfigSection.Initialize(ConfigProvider provider) +28
Telerik.Sitefinity.Configuration.Config.GetSectionInternal(Type sectionType, Boolean safeMode, String sectionName) +168
Telerik.Sitefinity.Configuration.Config.GetSectionPrivate(Type sectionType, Boolean safeMode, String sectionName) +178
Telerik.Sitefinity.Configuration.Config.GetSectionPrivate(Boolean safeMode) +99
Telerik.Sitefinity.Security.SecurityManager..cctor() +369

[TypeInitializationException: The type initializer for 'Telerik.Sitefinity.Security.SecurityManager' threw an exception.]
Telerik.Sitefinity.Security.SecurityManager.GetCurrentUserId() +0
Telerik.Sitefinity.Services.SitefinityContextBase.get_BackendCulture() +152
Telerik.Sitefinity.Localization.Resource.ResolveCulture(CultureInfo culture) +59
Telerik.Sitefinity.Localization.Resource.GetString(ResourceDataProvider provider, String classId, ResourceProperty property, CultureInfo culture, Boolean falback) +81
Telerik.Sitefinity.Modules.ControlTemplates.ControlTemplates.RegisterTemplatableControl(Type controlType, Type dataItemType, String resourceClassId, String areaName, String controlDisplayName) +162
Telerik.Sitefinity.Modules.ControlTemplates.ControlTemplates.RegisterTemplatableControl(Type controlType, Type dataItemType) +110
Telerik.Sitefinity.Services.SystemManager.Initialize() +1234
Telerik.Sitefinity.Abstractions.Bootstrapper.RegisterRoutes() +1027
Telerik.Sitefinity.Abstractions.Bootstrapper.Bootstrap() +593
Telerik.Sitefinity.Web.SitefinityHttpModule.Init(HttpApplication context) +259
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +612
System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +172
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +421
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +359

[HttpException (0x80004005): The type initializer for 'Telerik.Sitefinity.Security.SecurityManager' threw an exception.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +534
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +117
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +726

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?

[lextm]

@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.

[lstyles]

@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?

[jonoallen]

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.
If I pause the debugger, I see five threads:

1. PresentationFramework.dll?System.Windows.Controls.Grid.ResolveStartMaxDiscrepancy,
2. Worker Thread showing < not available > for location
3. Worker Thread showing < not available > for location
4. ProtocolHandler.ReadThread at Microsoft.VisualStudio.DesignTools.WpfTap.dll?Microsoft.VisualStudio.Design.Tools.WpfTap.Networking.AnonymousPipe.WaitForCondition
5. ProtocolHandler.SendThread at Microsoft.VisualStudio.DesignTools.WpfTap.dll?Microsoft.VisualStudio.DesignTools.WpfTap.Networking.ProtocolHandler.SendThread

[aynefd]

@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.

[lstyles]

@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.

[SamBent]

@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).

[935main]

@SamBent Take a look at https://github.com/935main/DotNet47Test and you can re-produce the behavior.

[SamBent]

@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.
This will be fixed in .Net 4.7.1. Meanwhile you can set
Switch.System.Windows.Controls.Grid.StarDefinitionsCanExceedAvailableSpace=true
to get the old algorithm. This will avoid the hang, but re-introduce the bugs the new algorithm was intended to fix; this is probably not a problem in your case.

See System.AppContext for details about setting app-context switches.