Jump to content

rsanford

uniGUI Subscriber
  • Posts

    136
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by rsanford

  1. Ok, not sure why C++ builder files were being called during build. My setup must have been corrupted.

     

    In summary, I have 2 PC's and both have XE2 and XE3 installed.

     

    PC1 - Uninstall unigui and reinstall unigui with only for XE2 32/64 bit. Rebuild in XE2, Success.

    PC2 - Uninstall unigui and reinstall unigui with only for XE3 32/64 bit. Rebuild in XE3, Success.

     

    I'll follow same when next build is delivered. For me, problem solved

     

    Thanks Farshad.

  2. Understood, I've checked the path's several times and they are correct. Not sure what is going on here. I have 2 pc's , both have XE2 , one has XE3.

     

    Next, new install of XE3 on my 2nd pc and tried to install build 975.

     

     

    Target PostBuildEvent:

    "\unigui\hpp_fix.exe" "C:\Users\Public\Documents\RAD Studio\10.0\hpp\ext.hpp"

     

    ext.hpp? Should I have this file?

     

    Thanks

  3. Hello, having installation problems. XE3 Update 1 and Build 975.

     

    1. Uninstalled Build 974 from XE3.

    2. Applied Update 1 to XE3

    3. Loaded Build 975 (uniGUI2013Group)

    4. Build all - terms at uniGUI17.bpl

     

    Compile error - [dcc32 Fatal Error] uniGUI17.dpk(133): F2048 Bad unit format: 'C:\Program Files (x86)\FMSoft\Framework\uniGUI\Dcu64\Delphi2013\uniGUIRTTI.dcu' - Expected version: 24.0, Windows Unicode(x86) Found version: 24.0, Windows Unicode(x64)

     

    Please assist,

    Thank you

     

    ps. Installed Build 975 in XE2, no issues.

  4. Hello,

    Here's the link to the documentation

     

     

    ISAPI setup on Abyss

     

     

    Basically:

     

    1. Compile your uniGUI application as an isapi dll

     

    Run Abyss WEb server console, under "Hosts", General option,

    2. Define the "Documents Path"

     

    Under "Hosts", "Scripting Parameters"

     

    3. enable scripts execution

    4. ISAPI parameters - define ISAPI Filename Extensions as "dll"

    5. Set script paths to where the dll is located. I set mine up as as subdirectory under the directory defined in "Documents Path".

  5. Excellent, thanks Farshad. I found an additional webserver - Abyss by Aprelium where I successfully tested ISAPI dll's on WIndows. There is a free and professional version, 32 and 64 bit versions and runs of Linux and Mac as well as Windows.

     

    Aprelium site

     

     

    Thanks

  6. I'm converting several windows desktop apps to uniGui. I'm investigating the options available. My apps will serve not more than 150 concurrent connections on an intranet. I'm considering the 64-bit standalone server deployment over Apache and IIS7 on Windows. What do you feel are pro and cons of using standalone? Is anyone using 64-bit standalone on Windows? I'm coming from the desktop app world so sorry for the naive questions :)

  7. Oscar, your application looks very well designed, congratulations! I'm converting several applications with Unigui and hope to have them completed by the end of this summer.

  8. Thanks, Zilav for the feedback. I can see how they both could counteract each other. I've got to find a way to enforce idle timeout/logout in order for my apps to be HIPAA compliant.

×
×
  • Create New...