-
Notifications
You must be signed in to change notification settings - Fork 21
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
GoToWindow.0.7.2.zip - I get this error #53
Comments
Mmh I'll check this when I get a chance, in the meantime can you check in log4net.config, set some path for the log file and check if there's any error or warning in the file? Also just in case, try disabling your anti-virus, and ensure the referenced dll is indeed there. |
INFO GoToWindow - Updates are disabled because GoToWindow is not running from the AppData directory. |
Mmmh, that's weird. I just uninstalled it, downloaded the zip file from GitHub directly, extracted it and everything works fine. This error means the MEF engine (the thing that actually loads the behavior of GoToWindow from the executable) could not find any DLL file. The WMI events line is normal if you don't run GoToWindow as an administrator. So we have to go to the basics;
Did it work before? You might also want to try changing the log level to DEBUG and see if there's something helpful there. |
|
Mmmh that's very weird. You did try without an anti-virus? Can you run from source? Otherwise I'll have to think of how to gather more clues... |
No. No intention to disable the anti-virus, sorry. |
For me, BitDefender [Enterprise] didn't let GoToWindow to work. I had to ping them to tell it was false positive, and still got it blocked few times after getting AV updates. I never got deep enough to check the logs etc as you did, cannot confirm if that was similar to your errors. |
Yeah to be honest the AV is a shot in the dark, this specific error should be fairly simple. I think adding some logs might help there. Can you build and run the app from visual studio? That will make it easier to diagnose the problem. Otherwise, maybe you are extracting in a unc path? E. G. \somewhere? Or in Program Files directly? |
D:\GoToWindow\GoToWindow.exe |
Nope, should not make a difference here... Let me add some diagnostic logs tonight and see if that helps.... |
Hi @Stamimail - try https://github.com/christianrondeau/GoToWindow/releases/tag/v0.7.3, and change this in the log4net.config file:
Change Then, run GoToWindow, and check the log file again. Also make sure you extract in a clean folder to make sure we don's have conflicting versions. |
2017-11-13 23:28:14 INFO GoToWindow - Updates are disabled because GoToWindow is not running from the AppData directory. Executable: D:\GoToWindow.0.7.3\GoToWindow.exe, App Data: C:\Users\Stamimail\AppData\Local |
Well I'm stumped. The next step would be to go all in and do something like https://blogs.msdn.microsoft.com/dsplaisted/2010/07/13/how-to-debug-and-diagnose-mef-failures/ but then you'll need to build a custom mefx executable, etc. etc. Are you willing to go to the next step? Also, do you have a C# environment to build the solution? The only variables I can think of are corrupted .NET installation, anti-virus preventing from loading the DLL files, bogus extract... |
Startup Error
No plug-ins found. Check that at least GoToWindow.Plugins.Core.dll can be found in the Plugins directory and restart GoToWindow.
The text was updated successfully, but these errors were encountered: