-
Notifications
You must be signed in to change notification settings - Fork 241
The file SciLexer.dll is not valid. #122
Comments
Can you please include the exact error message you are seeing and what version/build of ScintillaNET release and/or nuget package you are using? |
"The file SciLexer.dll is not valid." is the error message. It is version 3.6.0 what I would like to add. Thanks, |
The instructions for using v3.x have changed from v2.x. In the past you had to have an external SciLexer.dll present in your DLL search path and there were instructions for placing it there that you had to follow. Version 3.x does not require a separate file. The single ScintillaNET file is all you need. What I suspect is happening is that you have your old SciLexer.dll file in the search path somewhere and the new ScintillaNET.dll is attempting to load that one by mistake. Trying removing those old SciLexer DLLs from your search path. |
Okay, thank you. But can you please send me the link, where I can download the new ScintillaNET.dll file? Because I did not find any .dll file named "ScintillaNET.dll" on this site: https://github.com/jacobslusser/ScintillaNET/tree/master/src Thanks, |
Thank you! M |
I downloaded the signed version, but it does not have "verilog" lexer when I want to choose lexer in Visual Studio. Is this a way to use a verilog lexer, when I use only the ScintillaNET.dll for Visual Studio? |
I've been adding lexer support on an "as needed" basis and you are the first to request Verilog. I've added support in commit 7accb08. You can find instructions for configuring lexers in the documentation. |
I want to add Scintilla to Visual Studio 2015. I added the directory to my path on windows, And when I try to choose the dll file in Visual Studio to my Windows Forms Application project I get this error message. Adding SciLexer.dll is enough? I had the Scintilla v 2.6 before, and it worked fine. I tried it again, I added the ScintillaNET.dll to Visual Studio 2015 and it worked fine again, I do not get any error.
Thank you.
M
The text was updated successfully, but these errors were encountered: