Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

How to protect desktop code/program logic and compile

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    How to protect desktop code/program logic and compile

    Hello All,

    First let me apologise. I know this questions might already be answered in the forum, but I am a bit nervous and need to know this soon. I have spent quite some time developing a desktop app and cannot figure out two things
    1. How to protect my desktop code
    2. Best way to code runtime license in application, want run time to be installed with the application
    3. How to best package it in a installer
    I will keep looking in forums, but please if someone know this and can advise it would be appreciated.

    Thanks
    Ed

    #2
    Re: How to protect desktop code/program logic and compile

    Use a commercial installer - I use astrum installer(free)

    compile your code into an aex file with encryption, but be sure you keep a backup where it is not compiled in case you later need to change stuff.

    Use the alpha security and you can encrypt tables and forms.

    suggest your Installer place runtime in a folder and then the app in a folder underneath that.

    Those should get you started.
    Dave Mason
    [email protected]
    Skype is dave.mason46

    Comment


      #3
      Re: How to protect desktop code/program logic and compile

      Originally posted by DaveM View Post
      Use a commercial installer - I use astrum installer(free)

      compile your code into an aex file with encryption, but be sure you keep a backup where it is not compiled in case you later need to change stuff.

      Use the alpha security and you can encrypt tables and forms.

      suggest your Installer place runtime in a folder and then the app in a folder underneath that.

      Those should get you started.
      Thanks Dave, will give it a go today. Appreciate your quick reply.

      Comment


        #4
        Re: How to protect desktop code/program logic and compile

        Hi Dave, I compiled the code into an AEX file using Ron Anusiewicz utility that deletes the code of control panel ( i did took backup), but i am not sure how to hide the forms from control panel.

        My application mostly used UX components within the desktop env. I notice while I can compile code in AEX, I cannot figure out how to encrypt UX component. I am not too concerned with someone copying source, just want to understand this. I notice Dialog2 can be created of UX but it physically needs the UX to be in Webproject folder, I can't encrypt or hide that.

        Thanks Again
        Ed.
        Last edited by wahedq; 06-12-2016, 09:35 AM.

        Comment


          #5
          Re: How to protect desktop code/program logic and compile

          i am not sure how to hide the forms from control panel.
          You don't. You hide the control panel after creating a password protected button or a button on a password protected form which reveals the control panel when necessary. A runtime user should have no access or need for access.
          There can be only one.

          Comment


            #6
            Re: How to protect desktop code/program logic and compile

            You can turn off the control panel so users cannot see it unless you let them. Like Stan said, they do not need to ever see the control panel. I use a hidden and/or password protected button to be able to see the workspace for your own use. This is done right on the main menu(form) in my apps. Watch out for other ways to access the workspace that may be lurking.
            Dave Mason
            [email protected]
            Skype is dave.mason46

            Comment


              #7
              Re: How to protect desktop code/program logic and compile

              Originally posted by DaveM View Post
              You can turn off the control panel so users cannot see it unless you let them. Like Stan said, they do not need to ever see the control panel. I use a hidden and/or password protected button to be able to see the workspace for your own use. This is done right on the main menu(form) in my apps. Watch out for other ways to access the workspace that may be lurking.


              Got it Dave. Was able to hide the Control Panel, that helps. However the Web UX component that I use still is available in the Webproject folder. I was able to import it into a new workspace and rework. Is there a way to encrypt UX or password protect it?

              Comment


                #8
                Re: How to protect desktop code/program logic and compile

                Others may be able to help, but I have no experience with UX components.
                Never had a reason to use it.
                I use forms all the time.
                They can be locked from editing real easy.
                Dave Mason
                [email protected]
                Skype is dave.mason46

                Comment


                  #9
                  Re: How to protect desktop code/program logic and compile

                  Originally posted by DaveM View Post
                  Others may be able to help, but I have no experience with UX components.
                  Never had a reason to use it.
                  I use forms all the time.
                  They can be locked from editing real easy.
                  Thanks Dave, your feedback is much appreciated. I will wait for replies back from other members if they have any input of securing UX. Else I will need to move them to forms which will be significant work. So basically UX based GUI's are more like open source with Alpha, I may be wrong though.

                  Comment


                    #10
                    Re: How to protect desktop code/program logic and compile

                    Even if a runtime user does access the controlpanel, he cannot edit forms or scripts. He would need a developer license for that.
                    Robin

                    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                    Comment


                      #11
                      Re: How to protect desktop code/program logic and compile

                      If they have a developers license, you can block them out based on reg code and/or version number
                      Dave Mason
                      [email protected]
                      Skype is dave.mason46

                      Comment


                        #12
                        Re: How to protect desktop code/program logic and compile

                        Hi Dave, Can you please explain what you mean by blocking based on reg code? if you give me some leads on this it would be great.
                        Thanks

                        Comment


                          #13
                          Re: How to protect desktop code/program logic and compile

                          When alpha installs a dev, it creates a spot in the registry for the number. Your dev would have a different number.
                          alpha can read the registry entry when opened using the autoexec or other form
                          if yours and the other one don't match, shut alpha.
                          I don't use this, but do use a alpha version number check on a couple of apps I distribute. Like v12 won't allow dev in v11 or other.

                          Be sure to close the back door of the app as well.
                          Dave Mason
                          [email protected]
                          Skype is dave.mason46

                          Comment


                            #14
                            Re: How to protect desktop code/program logic and compile

                            Originally posted by DaveM View Post
                            When alpha installs a dev, it creates a spot in the registry for the number. Your dev would have a different number.
                            alpha can read the registry entry when opened using the autoexec or other form
                            if yours and the other one don't match, shut alpha.
                            I don't use this, but do use a alpha version number check on a couple of apps I distribute. Like v12 won't allow dev in v11 or other.

                            Be sure to close the back door of the app as well.
                            do we have any documentation around it or if you can advise what xbasic command should I be using. Also can you please explain what you mean by closing the back door. Sorry I am not a developer and ask silly questions.

                            thanks for your help

                            Comment


                              #15
                              Re: How to protect desktop code/program logic and compile

                              One can start an app with dev and holding down on ctrl+shift(I think) have the options to skip startup form, autoexec and etc. There is the option there to no longer make that available. Closes the back door!

                              Use your desktop help file searching version, registry, etc to decide how you wish to proceed.
                              Dave Mason
                              [email protected]
                              Skype is dave.mason46

                              Comment

                              Working...
                              X