When using .NET9 pre7 build and run, will throw System.Windows.Markup.XamlParseException

[ssccinng]

Description

When using the above code, an error will be thrown

System.Windows.Markup.XamlParseException
HResult=0x80131501
Message=“在“System.Windows.StaticResourceExtension”上提供值时引发了异常。”，行号为“12”，行位置为“10”。
Source=PresentationFramework
StackTrace:
在 System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
在 System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
在 System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
在 System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
在 System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
在 WpfBugTest.MainWindow.InitializeComponent() 在 D:\wcsrepo\WpfBugTest\MainWindow.xaml 中: 第 1 行

此异常最初是在此调用堆栈中引发的:
[外部代码]

内部异常 1:
IndexOutOfRangeException: Index was outside the bounds of the array.

Reproduction Steps

https://github.com/ssccinng/WpfBugTest

Run it using the latest preview version

Please note that this error does not occur when selecting net9 for the targetframework, but only when selecting net8
net8.0-windows

Expected behavior

not throw error

Actual behavior

throw error

Regression?

No response

Known Workarounds

No response

Impact

No response

Configuration

No response

Other information

No response

[heku]

I got same issue after upgrading my VS2022 preview to latest, my workaroud is installing .NET 8 SDK and adding a global.json to force .NET SDK to version 8.

[Taiizor]

When the project is compiled with .NET 9 Preview 7, it only runs successfully with .NET 9. Unfortunately, it encounters errors on lower versions.

[pchaurasia14]

@ssccinng @heku @Taiizor - Thanks for the report.

We have a candidate fix already in place for addressing this issue - #9584

[Taiizor]

@heku @Taiizor - Thanks for the report.

We have a candidate fix already in place for fixing this issue - #9584

So, will there be an interim release of .NET 9 to fix this, or do we need to wait until the .NET 9 RC version?

[pchaurasia14]

We are working out the logistics on this one. Currently awaiting approval from .NET.
I'll keep this thread posted on updates.

[melytc]

My team is also being impacted by this. Commenting to get notified of any update! cc: @haileymck

[Jakedahl94]

I am having this issue after upgrading VS this week.

[singhashish-wpf]

Apologies for the inconvenience. This happened because of regression of Setter.Value ContentProperty change.
We have reverted the changes and the changes are included in RC1 builds, this will be reflected in RC1.
There are two workarounds for now:

• Use global.json and pin the dotnet sdk version to 8. Something like below:

{
  "sdk": {
    "version": "8.0.300"
  },
}

• Use RC1 nightly builds - The builds which have the reverted changes included.

[AlanHauge-Interacoustics]

This also happens in .NET framework 4.8, so it might not be isolated to .NET 9

[i2van]

This also happens in .NET framework 4.8, so it might not be isolated to .NET 9

global.json can be used as WA:

{
  "sdk": {
    "version": "8.0.107",
    "rollForward": "latestFeature"
  }
}