I started working on a Wisej project again, it’s not very complex but it doesn’t start anymore, it gives an error: messages not found and it crashes.
It’s an almost empty project, there is only one form to open, I tried to download and reload it but it doesn’t work. All this scares me a lot because I would like to be able to trust Wisej and these surprises are not good news for your reliability. I can’t believe I have to live in fear of losing a project for no reason, that’s easy to understand. Can I really trust Wisej?
I also tried with a new empty project, same problem.
Greetings.
Francesco
The problem was Javascript debugging, now it’s fine.
What kind of error you got? Design time or Runtime? A screen-shot may help a lot.
The project load correctly in Visual Studio.
The included ChilkatDotNet48.dll is 32 bit.
I see a potential problem at runtime and debug because a mix of 32 bit and 64/AnyCPU can not be loaded by a default IIS application pool wich is a 64bit one.
You cannot load 32 bit DLL in a IIS 64 bit application pool
The ChilkatDotnet48.dll is a very particular piece of .NET code because contains native code…
https://chilkatsoft.com/win32_Framework48.asp
Try to change the dll with the 64 bit version or you need to configure IIS application pool to be a 32 bit one.
Please note that IIS (and IIS Express) on a 64bit Windows OS are configured by default with 64 bit application pools so the native DLL must be 64 bit and the .NET dll can be AnyCPU or 64 bit. Loading a 32 bit native DLL or a x86 (32 bit) .NET assembly lead to a load error.
Have a nice day.
Please do not upload real data……or license numbers….
Hi Francesco,
While this project does not contain many forms as you mentioned, there are still many customizations. The issue the project is displaying is related to one of the third-party dependencies added to the project (“ChilkatDotNet48”). I would suggest removing all unnecessary references from the project.
Additionally, there appear to be many customizations made within the Web.config file related to CrystalReports, AssemblyBindings, custom HttpHandlers, and more.
Your best bet is to start with a fresh working project template and start adding features until you can diagnose what functionality related to the dependency caused the application to break.
In summary, this is not a Wisej.NET issue, but we would be happy to diagnose and treat the issue for you with the purchase of consulting packages.
Best regards,
Levie
Please login first to submit.