First thing to know when working with Godaddy is that they use SQL express instead of SQL as would be expected in a hosting enviroment.

<!--So without thinking about it much I posted code in my last post.  I guess there must be a "safe" way to do that but I just dropped it in and didn't think about it.  Now my previous post isn't working properly.  Here is what I have done so far:

OK,  I'm going to work through my dnn install process to see if I can get mine working and make my discoveries available to all of us who enjoy the cheap price of godaddy hosting!

Here is what I've done so far to get things running.

I uploaded the install packet as a zip via ftp to the server.

Then I created the folder I wanted to store my DNN in.  Some people are worried about it showing in the root but I think in the web config you can change a setting that will alter the url that shows so it doesn't show that it isn't the root directory.  This also means that you can avoid some of the problems related to root directory installation as godaddy informed me that they won't make the root accessable to asp.net.

add key="HostHeader" value="" / Host Header to remove from URL so "www.mydomain.com/johndoe/Default.aspx" is treated as "www.mydomain.com/Default.aspx"

using the file manager click the box in front of your directory and choose permissions.  then set it to be able to read and write.  I don't know how safe this is I'm just trying to get it running. 

I then used the archive button to unpack the zip file to the new directory I created.

Next I created the database.  I used a SQL database not a mySQL database.  then if you click on the pencil the database and view the settings (press the configuration button on the toolbar) I think you can use the information from the ODBC.  you can see the connection string the database and user (should be the same) and you hopefully wrote down your database when you created it.  I installed the ASP but not the DSN since I don't think it's normally used in DNN and may even cause connection problems to use it in some cases.

Then I download the web.config file and make the following changes listed in mitchelsellers blog about setting up dnn.  this includes altering the connection settings in two places making sure that you comment out the SQL express and use the SQL connection string.  Make sure you change the {local} to the database string.  changed the object qualifier and changed the autoupgrade and useinstall wizard to false.  saved it and uploaded it over the web.config I had on the server.

Then I talked with tech support and they told me my account for my database was dbo, that I couldn't be told what driver my asp.net was using (I wanted 2.0.50727) and that I was able to configure all the permissions I needed to give my asp.net worker process full file permissions in my install directory. soooooooo,  I gave all the folders full permissions and told all the child folders to inherit the full permissions I had given to my install directory.  also you may want to change line 130 from <customErrors mode="RemoteOnly" . If you want to get useful errors, you need to change this parameter to "Off", like this: <customErrors mode="Off" 
 

Now,  I think that gives us most of steps.  Now I was confused and dazed and unable to figure out why the heck the silly thing didn't work!  So I fooled around a bit and was able to find in the iis setting that you can choose two types of communication classic (good) and integrated (yoursite doesn't work).  So I toggled it to the good setting and......

Oh yes, make sure you didn't install frontpage extensions they screw things up.  (how's that for professional?)

And I'm just about to give it another Go.  Good luck guys!