Public Beta
Last updated
Was this helpful?
Last updated
Was this helpful?
To install Wisej.NET 4, you will need two files: the "Wisej.NET-4-VS2022.vsix" extension and the "Wisej-4.4.0.0-beta.#.nupkg" package. The most current "Wisej.NET-4-VS2022.vsix" can be downloaded from the link provided below.
Meanwhile, the latest beta versions of the Wisej-4 package, and all the Wisej-4 extensions, will be accessible on .
Be sure to obtain both files for a successful setup and to enjoy the full feature set offered by Wisej.NET 4, incorporating advancements like managed System.Drawing, the .NET Core out-of-process designer, and the new fluent markup extensions.
Please be aware that the designer is no longer included within the VSIX extension. Instead, it is now deployed with each NuGet package. The VSIX extension, however, is still necessary for the replacement of the and several other enhancements within Visual Studio.
Editors, especially collection editors, present the most significant challenges when migrating to the out-of-process designer. As of now, we have integrated the following collection editors using the basic editor system that comes with the designer. However, we are planning to transition the more complex editors in an upcoming release.
DataGridViewColumnCollection
TreeNodeCollection
In Progress
The ImageSourceEditor is presently unable to load icons from icon packs. However, this functionality will be completed and available before the official release.
Completed
The cell style editor is functional but incomplete. It does not provide a preview of the style changes being made. Additionally, any modifications are applied directly to the DataGridViewCellStyle instance. Consequently, if you press the Cancel button, the edits will still be committed.
Completed
Data binding and the associated editors function as expected. However, it's worth noting that Microsoft has not yet provided an implementation for the typed DataSet editor. Currently, Microsoft suggests using the new Object Data Source Binding as an alternative to accommodate this gap.
If you prefer to use .NET 9 or .NET 10 instead of .NET 8, you can do so with minimal issues. However, it's important to note that with .NET 9, Microsoft has completely removed the BinaryFormatter, as part of their ongoing initiative to improve developer security by protecting them from themselves.
Interestingly, they have reintroduced the same "unsafe" classes by offering them as a NuGet package.
This change affects all designer .resx files that contain values serialized with the BinaryFormatter. While these files are safe as internal .resx files — something even Microsoft acknowledges — they will not load properly in .NET 9 and above unless you include the following NuGet package reference in your project:
Additionally, we are actively working on removing the binary serialization of custom snap lines and responsive properties to align with the latest security practices and ensure optimal compatibility with .NET 9 and new releases.
