Chaning all table names of ASP.NET 2.0 PW Stater kit and moving it to Godaddy.com (2)

2008-04-29


I would like to put my own PWS into the sub folder on godaddy.com and I hope I can build multiple ASP.NET projects on the same godaddy ASP.NET account.

I even tried to create sub folders throught FTP tools on my godaddy hosting space, but after I finished to transfer my local files on that sub folder, I found it could not work. I thought it was not a simple operation like what I did. Then I posted my question on www.asp.net forums, a friend answered for ASP.NET project running in a sub folder, I have to ask goddaddy.com to provide me the relevant service.

Later I wrote an Email to support@godaddy.com, repidly I got their reply like the following:

Dear Sir/Madam,

Thank you for contacting Online Support.

You may specify permissions for your ASP hosting account with the following directions. Please note that the 'Directory Management' button will not be available if you have FrontPage extensions installed.

You can uninstall FrontPage Extensions from the 'Other Settings' page or modify your permissions through your website publishing software.

First, log into your customer account:

. Go to the Go Daddy Account Login Page. . Log in using your account username (which may be the same as your customer number) and password.

If you have trouble logging in, our password reset form may help you. You can find this form through the following link: Account Retrieval Page

Once logged in, follow these steps:

. Select 'Web Hosting & Databases' from the 'Hosting & Email' menu at the top of the page . Click the 'Open' link under the Control panel heading for the hosting account you wish to manage . Under 'Content' click on 'Directory Management' . Click the 'Create Directory' button . Enter the 'Directory / Subdirectory' name . Specify the permissions by checking the box under the appropriate column. (Read, Web, Browse, Write, Reset) . Click the 'Continue' button . Click 'Add' to confirm the update

You also have the option to remove existing folders from the list by using the reset option; this sets the folder to the correct permissions, and then removes the folder from the list.

Please let us know if we can help you in any other way.

Then I know I can get the implishment of my tasks. I created my customer directory and set on the permision to Read, Write, Web, Root Set (Application Root), I have waited for a while, about 10 minites, I saw the folder was created (I used FTP tool to watch).

Later I transfer my local asp.net website published files to this customer directory and modified web.config by giving correct connection string.

However, I still got error message when I tried to visit my PWS:

This application was precompiled with personalization turned off, but it appears to have been turned on after the precompilation, which is not supported.

I asked goddaddy.com again but they told me they don't troubleshoot or fix custom coding. So I have to resolve it by myself.

I noticed that I have build another asp.net project on the original root folder, then I created another customer directory and move the old files from the original root folder to the new customer folder, haha! I found It works, I can visit this project by click www.mydomain.com/mycustomerdirectory2/ ! And, I found the previous project I mentioned above works too by click www.mydomain.com/mycustomerdirectory1/ ! This is great!

So the reason maybe came from I put another asp.net project to the original root folder, then, for building multiple ASP.NET 2.0 projects, I should put them to different sub folders and don't put the original root folder? I am not sure, but I don't care, I just want to builder multiple asp.net projects on different sub folders, this is just what I want !

the following is my connctiStrings content in my web.config file:

<connectionStrings>

<add name="Personal" connectionString="server=whsql-v0XXX.prod.mesaXXXX.secureserver.net; database=DB_XXXX; uid=XXXX; pwd=XXXXXXXXXXX; Trusted_Connection=False" providerName="System.Data.SqlClient" />

<remove name="LocalSqlServer"/>

<add name="LocalSqlServer" connectionString="server=whsql-v0XXX.prod.mesaXXXX.secureserver.net; database=DB_XXXX; uid=XXXX; pwd=XXXXXXXXXXX; Trusted_Connection=False" providerName="System.Data.SqlClient" />

</connectionStrings>

(attention: XXX is hidden content)