Flailing around for a solution, I just ran Warewolf Test Agent.exe out of the Binaries folder (although it seems to exist everywhere) - after a very long delay, both the Server and Studio started, giving compile dates as per usual. Both died right away; I assume this is the Test Agent killing them. Maybe. I'll look at logs. Or maybe not.

I have just now manually restarted the "Warewolf Server" service, and I'll see if Studio runs.

There are now 34 different instances of "Werewolf Studio.exe" in the repository after building everything. This seems like overkill to me.

I just changed "Werewolf Studio.exe" to run as Admin, and Studio started. I can now manually start and stop the Werewolf Server, I suppose, which seems like a more sane approach than keeping the CMD window open to be able to stop it.

For tough builds, this is right up there! If I run into more snags related to installation, I'll post. If you wouldn't mind, which of the directories can I now delete? I'm assuming I don't need 34 copies of Werewolf Studio.exe :)

Regards,

burque505

Postscriptum (this forum won't even let me write "p.s" at the beginning of a line): Apparently removing the version related attributes for IronPython.Modules in Dev2.Server.csproj as stated above didn't hammer anything that I can immediately detect. No examples in this build, apparently, at least not how I built it.

Edit: No real joy here. Saving a microservice kills the Studio. Oh well . . . better luck next time. Back to the drawing board.

What's the chmod +x command in there for? Windows bash?

Compiling Web.sln:

Deleted everything, changed the above to <Reference Include="IronPython.Modules"> in Dev2.Server.csproj to see if there's any joy. Recompiling AcceptanceTesting.sln now.

No luck.

The code formatting is broken, I can't paste in any code, so I'll have to type this in - line 181 in Dev2.Server.csproj:

<Reference Include="IronPython.Modules, Version=2.7.0.40, Culture=neutral, PublicKeyToken=7f709c5b713576e1, processorArchitecture=MSIL">

But the supplied DLLs are all 2.7.3.100.

In Dev2.Server.bin.Debug, IronPython.dll properties:

And then IronPython.Modules.dll:

Regards,

burque505

Ashley, thanks for responding. I appreciate it. I'll post my results piecemeal, as my Win7 development box is old and slow (kind of like its owner).

• VS 2019 Community Edition, v16.2.3, .NET framework 4.8.03761.
• This time around, I have compiled Dev2.Development.Languages firs to make sure IronPython wasn't getting left out. It compiled, although with 308 warnings (not surprising), and the IronPython modules are in the correct place. I think I can rule that out. I cleaned it, and will now compile AcceptanceTesting.
• I will come back to this in about 15 minutes, which is what it takes to compile on this old machine. That should give me a server to start.

(As a side note here, after compiling AcceptanceTesting I have 4 instances of "Warewolf Server.exe".)

• I will now run cmd /k "%~dp0Dev\Dev2.Server\bin\Debug\Warewolf Server.exe" from the command line:
• "System cannot find the path specified."
• Now running C:\Warewolf>cmd /k "Dev\Dev2.Server\bin\Debug\Warewolf Server.exe".
• Exits without any messages.
• Server log, however, is more informative.

2019-07-22 22:17:11,544 ERROR - [Warewolf Error] - Error Starting Server
System.IO.FileLoadException: Could not load file or assembly 'IronPython, Version=2.7.5.0, Culture=neutral, PublicKeyToken=7f709c5b713576e1' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'IronPython, Version=2.7.5.0, Culture=neutral, PublicKeyToken=7f709c5b713576e1' ---> System.IO.FileLoadException: Could not load file or assembly 'IronPython, Version=2.7.0.40, Culture=neutral, PublicKeyToken=7f709c5b713576e1' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'IronPython, Version=2.7.0.40, Culture=neutral, PublicKeyToken=7f709c5b713576e1'

Any suggestions? I am going to muck around a little to see if I can fix it.

Regards,

burque505

Running "Werewolf Test Agent.exe" gets the server to start, but doesn't allow a Studio start (Win7 attempt here).

Uninstalling completely. As following the instructions provided on the Warewolf website doesn't result in a working installation (although it did before the last update, as described above, albeit with some workarounds), I'll revisit this when and if someone responds to it.

Thanks.

burque505

Same results with Win7 compile.

I got rid of the 'FSharp.Core' warning by manually adding a reference. The 'Oracle.ManagedDataAccess' warnings do not got away, even though the DLLs are present in the folders where they should be and the references above were manually added.

The server, however, will not start. I get no error messages, it simply exits.

As you might rightly imagine, trying to run studio without the server running yields this:

No IronPython error messages on this build, but then again, no error messages at all. I tried installing IronPython to see if that might do the trick, but, well, no.

Regards,

burque505

I needed to install .NET Framework 4.8 before installing. Duh . . . Now working on Win10 build 1903, VS Studio is - I don't know, the latest as of August 31, 2019.

So far, I built Warewolf.Language.Parser first just to be safe, then everything in Server.sln built fine,

Only got these warnings: