Microsoft Visual Studio Community 2022
Version 17.6.0
VisualStudio.17.Release/17.6.0+33712.159
Microsoft .NET Framework
Version 4.8.09032
.NET version
6.0, 7.0
Did this work in a previous version of Visual Studio and/or previous .NET release?
Yes in .Net framework designer
Issue description
When you press F1 on any property in designer's propertygrid you must be redirected to appropriate msdn page. But currently designer trying to use proxy object for this case. For example Form.Text property:
Expexted
https://learn.microsoft.com/en-us/dotnet/api/system.windows.forms.form.text?f1url=%3FappId%3DDev16IDEF1%26l%3DEN-US%26k%3Dk(System.Windows.Forms.Form.Text)%3Bk(System.Windows.Forms.Form)%3Bk(VS.Properties)%26rd%3Dtrue&view=windowsdesktop-7.0
Current
https://msdn.microsoft.com/query/dev16.query?appId=Dev16IDEF1&l=EN-US&k=k(Microsoft.DotNet.DesignTools.Client.Proxies.ControlProxy`1 .... very very long string and as result:
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
This is also a problem for custom control designers. I've asked same question here, but never got answered :(
Environment
Microsoft Visual Studio Community 2022 Version 17.6.0 VisualStudio.17.Release/17.6.0+33712.159 Microsoft .NET Framework Version 4.8.09032
.NET version
6.0, 7.0
Did this work in a previous version of Visual Studio and/or previous .NET release?
Yes in .Net framework designer
Issue description
When you press F1 on any property in designer's propertygrid you must be redirected to appropriate msdn page. But currently designer trying to use proxy object for this case. For example
Form.Text
property: Expextedhttps://learn.microsoft.com/en-us/dotnet/api/system.windows.forms.form.text?f1url=%3FappId%3DDev16IDEF1%26l%3DEN-US%26k%3Dk(System.Windows.Forms.Form.Text)%3Bk(System.Windows.Forms.Form)%3Bk(VS.Properties)%26rd%3Dtrue&view=windowsdesktop-7.0
Current
https://msdn.microsoft.com/query/dev16.query?appId=Dev16IDEF1&l=EN-US&k=k(Microsoft.DotNet.DesignTools.Client.Proxies.ControlProxy`1 .... very very long string
and as result:This is also a problem for custom control designers. I've asked same question here, but never got answered :(