brandonpoc

Costura worked, *after* the nightmare of getting it to work properly with VS Studio 2015. I'm not sure what the deal is but it couldn't compile the right version, and then when I'd try to switch versions, the previous ones info would be embedded in the metadata of the project and I'd have to start a new one. Apparently the MSBuild format for the project isn't right on the latest version of Costura. So, to help people out - if you need Costura.Fody to work w/ VS Studio .Net 2015 (or if it's giving you the MSBuild XML errors anywhere else), try this: Make sure you have .Net 4.7.2 installed a

Is doing all of that statically thread-safe for uBot, as long as the functions themselves are thread safe? And do you know of any examples of plugins that the source is avaialble for that do something similar- such as a SQL database plugin or something? Thanks

Thanks, going to give it a try! I have several other plugin-related queries as well, being that the Plugin development page on the Wiki while being somewhat informative and describes the interfaces and implementation to each class, isn't too clear on how they all work together and to the uBot program itself, and the examples of source code available of actual working plugins are somewhat lacking. For instance, for my plugin I intend on having it work like this: 1) Create a redis connection (returned by function, assigned by variable); this will be an instantiated object that is unique to

I decided to try my hand at extending uBot functionality and write a plugin. I'm writing a Redis database plugin to allow interfacing with the server, set/get'ing, etc; however, uBot is not able to load the plugin because, I assume, the DLL provided (installed by "nugat", a package manager for .Net that installs assemblies) isn't being found. After snooping on system calls I see uBot is trying to access a key in the registry with the assembly DLL in the name, but not looking for the DLL file in any capacity. I would assume that the function(s) being used from the assemblies would get included

Okay - is there anything listing other limitations with external browser use such as that limitation with proxies?

Thanks, I hope it solves the problems for time being so people can start crankin' at v6.. Also have a comment on something I found weird, might want to take a look into it- the UBotCefBrowser executable log was reporting that it couldn't find CEFSharp.core.dll or something like that even though it could load it and it did load it. The DLL is located in the %APPDATA%\uBot Studio\Browser\<ubot version>\ directory, exactly where it would expect to find it. Not sure if's related or maybe causing an issue for others. But I verified it did load yet it still complained in the log. Regards

Which version of Firefox must be installed on the computer in order to use the gecko driver? Firefox is not executing for me, however Chrome is. And with that said - is there a version of Chrome that will work best? Also, is there some kind of updated documentation for 6.x? I got all these emails saying that it would be the greatest coming since Jesus Christ, but I'm at a loss for some documentation to really dig in. On the scripting reference page there is no reference to the 'external browser' command, for instance.

Try installing the 32-bit redistributable MSVC++ libraries from Microsoft on the computer trying to run the bot. This fixed the issue with uBot 5.9 and 6.0 on various computers. It might solve your issue as it sounds the same. Go to https://www.microsoft.com/en-us/download/details.aspx?id=52685 and click the red DOWNLOAD button. Click the 32-bit version (x86) -and 64-bit if you want, if its not installed - and then install the 32-bit version. Try running the bot again after it's installed. Regards Brandon

FIXED (INSTRUCTIONS WITHIN) After opening a debugger on the software a bit for myself, and seeing what libraries loaded and where dynamic calls were failing (because the DLLs were missing/incorrect versioned/etc), which I imagine the programmers/developers should've done , and found I was completely wrong on it being on the remote side. Instead, I found that the problem is that it needs the *32-bit* Microsoft Visual Studio (in particular "MSVCP140.dll", aka MSVC++ runtime library) redistributable libraries (DLLs etc) as apparently uBot is a 32-bit program. I discovered this by just watchin

Buddy, Thanks. Just trying to figure it out. I noticed the CEF browser log was complaining about not being able to find CEFSharp.Core.Dll but the DLL gets loaded (as confirmed by system call monitoring) and is present in the main install directory. I changed the config files to accept different versions of .Net hoping that would help, no dice. I saw it trying to load the MSVC++ .Net 2015 redistributable DLLs and installed that, and it loaded the DLL, but still same outcome in uBot Studio loading (exact same thing, sits at Verifying License). This was same case in 7, 10, server 2012, etc.

Tried it on a separate Windows 7 x64 and 32-bit machine, and on a Windows 2012 R2 Datacenter w/ GUI, fresh installs w/ .Net 4.5 and 4.7.2 etc, still did not work. Still stuck at "Validating License". Fucking hell people. Keep in mind this is a completely different server, running under VMware, on a different network, running different installs of the two OSes than the Windows 7 and Windows 10 my laptop were. Oh, and same goes for my VMware on my OS X box. Still didn't do shit. Can we entertain me for a minute and, for the love of God, somebody contact me on the phone or Skype or something

Okay, I kept insisting it was on server side but , if it's client side, why's it hanging waiting for a response? Very confused. I installed the two different uBot versions, 6 and 5.9, on both Windows 7 and Windows 10 *clean* installs, each trying .Net 4.5 and .Net 4.7. None worked. tcpview showed that connections to the license server (amongst others including Yahoo?) were being left open. Very confused as to what's happening then. EDIT: I'm launching some Windows 7 and Windows server VMs on my network and going to see if uBot works on any of these.

Any update? Haven't heard back from support.

I'm definitely thinking this is uBot's server-side; I just CLEAN installed Windows 10 Pro on the same laptop completely from scratch, deleting the partition and recreating it, doing a fresh Windows 10 Pro installation, and a fresh uBot 6.0.3 install does NOT work. Exact same situation as before. The problem has to be in your licensing scripts. If it's not, figure it out then. Someone for the love of God fix this damn thing. UPDATE: Grabbed 5.9.57 install MSI and proceeded to uninstall uBot 6.0.3 and install 5.9.57. It downloaded assets, I logged in, and it offered me the upgrade to 6.0.3.

Another small update- I notice if I don't upgrade to 6.0.3 and, upon the notification bar asking me if I wish to upgrade, selecting either Remind me later or Skip, the splash screen sits at 'Checking for updates' versus 'Verifying license'. Once I then kill the uBot processes and re-start it, it gets stuck at Validating license. I'll say this again - could this have something to do with unresponsive license validation function on the remote side. Have you uBot staff checked your web server logs? Because honestly I'm noticing that all the connections made aside from the Update ones are stayin