Problem Publishing to the Web

After completing my application I used VB 2005 to "Publish" to the web and supplied a website address. After the publish I copied the published files to the correct directory on my website but whenever folks access the publish.htm page all they get on their screen is a dump of XML code.

Any idea what I'm doing wrong. The install works just fine on my PC (with Visual Studio 2005 installed) but doesn't work on anyone else's computer wihout VS 2005 installed.

Help!

Thanks, Doug


Answer this question

Problem Publishing to the Web

  • Scott ODonnell

    Doug,

    Thanks for the prompt reply.

    I have tried your suggestion and everything seems to work fine except I still get all the XML text in the browser. Looking at the web server shows that all the files were published in the correct folders.

    I also looked at the "mime" thing - seems that FP extensions are installed on the server so I can't edit "MIME" settings as a result. I tried un-installing the FP extentions, then setting the MIME extensions with no luck. (I tried it 2 ways - once leaving the FP off and once after re-installing FP).

    My last resort is to talk to my ISP directly to verify the MIME settings - after that, if it doesn't work, I'm stuck.

    Thanks again for your help.

    Jerry


  • Johannes Hansen

    Any takers This continues to happen. When friends access the publish.htm file on my website and click the "Install" button they then get a screen full of XML code. But when I go to the same website from my computer and run the install, everything runs perfectly.

    Any ideas

    Thanks, Doug

  • Esprit

    Hi Jerry,

    Yes, I was unclear. There are two ways that work. On the Publish tab of the application's Properties page (right-click the application name in the Solution Explorer and select Properties) you can simply enter the FTP address for your website as the Publishing Location and then the HTTP address for the application as the Installatuion URL. You then simply hit the Publish Now button. If your website requires a login you'll shortly be prompted for the username and password. After furnishing those the application is published to the website.

    The other way is to use the Publish Wizard. With the wizard you first enter the FTP address on the first wizard step. On the next step you select "From a Web site:" enter the HTTP address for the application on your website. Follow the remaining steps and the application will install to your website. Again, if your website requires a username and password you'll be prompted.

    Hope this helps,

    Doug


  • Meeper

    Doug,

    I'm glad you figured it out. I'm having the same problem - however, I can't tell from your post just what you did to fix the problem.

    In the "Publishing Location" I am using my web URL:
    http://www.website.com/newfolder

    In the "Installation URL" - I am leaving it blank (I have also trie various URL)

    I know I'm doing something wrong but I'm too tired to carry on.

    Hope you can tell what I'm doing wrong

    Jerry


  • Yoni Raziel

    Thanks everyone for the replys. I did finally figure it out and it's an embarrasing mistake :)

    One of the first links you are requested to enter is the link to the "Publish" folder. I was entering the location as the "publish" directory inside the applications folder on my local computer. Later on whern asked to enter the location to search for updates I was entering my website. Once it dawned on me what I was doing, I corrected the silly mistake and now all is well. We live and learn :)

    Doug


  • paschott

    I think it is due to .application file association at their PC is incorrectly mapped.

  • spree

    Doug,

    There are two things to check.

    1. Make sure the server MIME types are correct. They are described in the first section of http://msdn2.microsoft.com/en-us/library/ms229001.aspx.
    2. Verify that your end users and the .NET FX installed on their computer. The publish.htm created by Visual Studio will automatic point to setup.exe (aka the bootstrapper) instead of the .application file if it detects the .NET FX 2.0 are not installed.

    Regards,

    Elizabeth Maher

    Visual Basic Team



  • Problem Publishing to the Web