Issue with .Net Framework out-of-process designer. Cannot Add 32-bit Controls to Toolbox
- Dominant language
- C#
- Stars
- 4.9k
- Forks
- 1.1k
- Avg merge
- 20h 23m
- Merged PRs (30d)
- 103
Description
### Environment
VS 2022 (v. 17.8.0 Preview 4.0). My current project is set to use the .Net Framework 4.8.1. This is the only area to submit issues with an out-of-process designer that I can see right now.
### .NET version
4.8.1 (but would also like to do with with Framework 4.7.2)
### Did this work in a previous version of Visual Studio and/or previous .NET release?
Yes! It works fine in Visual Studio 2019.
### Issue description
I primarily develop solutions for Microsoft Dynamics SL as an ISV. Using the out-of-process designer with the current preview of VS 2022 (v. 17.8.0 Preview 4.0 according to Help > About), I can view the SL SDK 32-bit controls on the design surface, reposition, and save them using a project initially created with VS 2019. I cannot load and view the project in the current release version (17.7.5) without seeing many yellow error messages stating “Could not find type…”. This is a welcome improvement!
However, I cannot add the 32-bit controls to the Toolbox. When I try to add the Microsoft.Dynamics.SL.Controls.dll to the toolbox using “Choose Items…” after browsing on the .Net Framework Components tab, I see an error message stating “The file ‘C:\Program Files (x86)\Common Files\Microsoft Shared\DynamicsSL\Microsoft.Dynamics.SL.Controls.dll’ is not valid.” Please make is possible to add this, and other valid 32-bit dlls containing .Net Framework Component controls to the toolbox. Without this I can’t add new SL SDK controls to the form when they are required.
### Steps to reproduce
When I try to add the Microsoft.Dynamics.SL.Controls.dll to the toolbox using “Choose Items…” after browsing on the .Net Framework Components tab, I see an error message stating “The file ‘C:\Program Files (x86)\Common Files\Microsoft Shared\DynamicsSL\Microsoft.Dynamics.SL.Controls.dll’ is not valid.”
### Diagnostics
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.