-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.8.1 build success on Visual Studio 2022 Community but getting ANSI Error when installing the plugin #161
Comments
Version 0.8.2 build fine for Rebuild started at 6:15 AM... |
If anyone wants to try building MarkdownViewerPlusPlus on Visual Studio 2022 Community check this out: Open Legacy Projects (4.5 Framework) In Visual Studio 2022 |
Another recommendation for ANSI issue: NotePad++ Plugin - ANSI vs UNICODE From the reddit post:
|
I was able to build 0.8.2 as well on Debug - Any CPU and Debug - x86 with the following settings:
The ANSI error is gone and the the build is successful. I tested installing the plugin and it works! |
Issue description
0.8.1 build success on Visual Studio 2022 Community but getting ANSI Error when installing the plugin
Following up on this:
#70
@monoblaine I was able to build version 0.8.1 in Visual Studio 2022 for x86 using PDFSharp
1.50.4000-beta3b
as suggested by @DimitrijeKOther packages:
HtmlRenderer.Core -> 1.5.1-beta1
HtmlRenderer.PdfSharp -> 1.5.1-beta1
HtmlRenderer.WinForms -> 1.5.1-beta1
When copying the plugin files to Notepad++ 8.6.8 (x86) plugins folder I still get the same error "This ANSI plugin is not compatible with your Unicode Notepad++"
kbilsted/NotepadPlusPlusPluginPack.Net#52
This mentions running "makerelease.ps1" for NotepadPlusPlusPluginPack.Net:0.94.00 but it seems like all the files in v0.8.1 are already UTF-8.
Also, on this Npp community thread, "C# Plugin Development and Error: This ANSI plugin is not compatible with your Unicode Notepad++" Paul Baker suggested changing the post-build tasks but I am lot at this.
Has anyone tried to build it recently? Any luck?
Environment
The text was updated successfully, but these errors were encountered: