After I add GroupDocs Search to .NET9 project, UI editor doesn’t work. When I take a button and drop it on the form, it gets added to the bottom of the form and not to the actual form. If I uninstall Search, everything works again.
Can someone explain what is going on?
Thanks
GroupDocsSearch.png (75.3 KB)
Can you please provide more details about the version of GroupDocs Search you are using and any specific error messages you are encountering?
Version is 25.4.0
@NPozdniakov
This issue is reproduced at our end. Therefore, we have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): SEARCHNET-3484
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
This issue exists. Windows Forms generates the output:
Request failures: Types/GetEditor.
Microsoft.DotNet.DesignTools.Client.DesignToolsServerException: Could not resolve type, 'System.ComponentModel.ComponentEditor, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
We do not face such an issue using WPF. And this, by the way, is a more modern and productive platform for building applications with a visual user interface.
Otherwise, you can use WinUI3, an even more modern platform. An example of using WPF is in this GitHub repository.
I have existing WinForms app I’m trying to add search functionality to. Are you saying WinForms is not supported? This makes no sense to me.
Please spare us sometime to further look into this matter. We’ll notify you as soon as we have a solution or workaround.
WinForms are supported. The problem is only in Visual Studio Designer.
The problem is solved by disabling the GroupDocs.Search dependency at the stage of developing the graphical interface in the Designer.
We will also do our best to fix the incompatibility with Visual Studio Designer.
For example, as a workaround, the dependency can be attached to a separate DLL, and this DLL can be attached dynamically during application execution.
Try using this version
If there are problems, then use it only at the interface development stage in Visual Studio Designer. And to run the application, use this version
Please implement proper fix as soon as possible. These workarounds are not great and I would rather not deal with them. I just want to install a package and it have it work. Thank you.
Try using this package. You may not need anything else.
Mine is .NET app. I use the one and had issues. Prob not a good idea to add Framwork package to .net app.
I tried to create a WinForms .NET9 application using GroupDocs.Search.NETFramework - it worked, documents are indexed, search is performed.
The compatibility issue is that the .NET version of GroupDocs.Search uses a different version of System.dll, which does not have the System.ComponentModel.ComponentEditor class required for Visual Studio Designer. And for some reason the Designer looks for this class, apparently, in this other System.dll.
So far we have not found a way to fix the problem.
.NETFramework seem to work but now I have a warning that says "package restored with .NET framework … ". Would be great to avoid that. Any progress on proper fix?
No solution found for .NET Core library yet.
The warning is not an error, is it? The project compiles, no exceptions occur in runtime?
We are still working on finding a proper solution for the issue.
The core of the problem lies in incompatibilities between Microsoft system libraries, and we are continuing to investigate potential resolutions.
We fully understand that adding a .NET Framework-compiled library as a dependency in a .NET project is not an ideal approach. However, it remains a temporary workaround while we work toward a more appropriate solution.
Thanks
Sounds good. Thank you.
We would like to suggest another workaround that avoids the warning.
You can use the GroupDocs.Total package, which includes GroupDocs.Search as part of the bundle.
The main drawback of this approach is the larger package size — approximately twice as large — since GroupDocs.Total contains multiple GroupDocs products.
However, this solution will allow you to work without encountering the warning while we continue working on a fix for the standalone GroupDocs.Search package.
Thanks
Please use the GroupDocs.Total package:
It contains all GroupDocs products and is free from the incompatibility problem with the WinForms Designer.