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

possible to manually move files to IIS?

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

    possible to manually move files to IIS?

    Is there a way to manually publish to IIS? like having the application "publish" to a local folder and just copy those files to the website files on IIS. As i always seem to have an error when publishing directly and would prefer not to have to constantly troubleshoot IIS with every new app, especially when changing servers.

    Sadly i only have build 5028.

    #2
    Re: possible to manually move files to IIS?

    You can FTP files to IIS. I use FileZilla. What kind of errors are you getting?

    Comment


      #3
      Re: possible to manually move files to IIS?

      Had a few issues with web deploy, and the previous server kept having issues with new apps. Even when settings were copied it would always fail to publish to an existing site and error out when creating a new one, the new server seems to be fine, for some reason web-deploy didn't install properly (somehow the package installer was missing and it didn't install anything but the name). I tried moving the files from a local publish to IIS folder but it would always have an error regarding opening a a5w ext but that was fixed with a reinstall of AA IIS server.

      Some how my antivirus decided parts of the Web Deploy 4.0 and AA IIS were malicious so they didn't get to install properly. Got it working tho, thanks to Terry Smith for helping me see what i was checking incorrectly.

      Comment


        #4
        Re: possible to manually move files to IIS?

        but I'm curious on this too, Edgar--in talking to Terry did he offer a way to copy files manually? I'm working on some servers geographically a long way away and for the sake of time, I'd usually love to just copy the key files that I've changed instead of all the support files, much less the whole checking AA versions, creating an app pool that's long-existed...

        Comment


          #5
          Re: possible to manually move files to IIS?

          Sadly he mentioned that there is no supported way to just transfer files on to the IIS. Now that the issues with my server are fixed, ill try it out, but from the time i tried it i was getting errors were IIS for some reason did not know how to open a5w files, it might be another setting. Maybe on the application pool, ill look into it and post what i find ^.^

          Comment


            #6
            Re: possible to manually move files to IIS?

            I tried it, and it seems to make more files for a local publish than it does for an IIS publish. It adds security settings files, and does not create webconfig. It might be that for local it created the files needed for the Application Server and not for the IIS server.

            Those extra files seem to be security settings and database connection strings, that might mean that the other files just use references to these connection strings and in IIS they are handled differently. I tried placing the local publish file on to an IIS site folder and copied webconfig over also copying the application settings in IIS, sadly it only gave me assembly errors, it seems that without particular instructions from publish it does not know what to do with the AA files.

            I hope they add manual publish or something similar for IIS as a feature in the future (even tho i might not get to use it, it would be nice for some users).

            Comment


              #7
              Re: possible to manually move files to IIS?

              Hey Edgar, thanks for your responses, tests, and sharing here. I hadn't yet found a way to do it either, and also hope for another option in the future. To be fair, the default option seems really clean and straightforward, just takes a good bit longer than I'd prefer.

              Comment


                #8
                Re: possible to manually move files to IIS?

                There are specific instructions for that Terry has provided that allow you to transfer using regular FTP. It's a cumbersom process but does work. The quote below is from Terry:

                "You may be able to accomplish what you need on your own (not Alpha supported).
                Follow the instructions in the 'How to build an IIS deployment package document' to get the application's initial publish and configuration.
                Get the physical path to the application's deployed folder.
                Setup FTP to that folder.
                Now, to publish a new version of the application
                Use a Publish Profile for publishing to IIS that publishes to localhost. This is important because only publish to IIS will generate a web.config file and this is where page security authorization rules are stored.
                Use an FTP tool to FTP the files from the application's published folder on localhost to the application's folder on the server setup in step 3. This is a separate FTP tool and not an Alpha FTP Publish Profile because of the web.config requirements stated in the previous step."

                Comment

                Working...
                X