So uh, I'm new to this.

[tscontractors]

I just uploaded my first ASP.NET website via VS's native publish website feature, and I wiped out all the default files by accident (yeah, even with the warning I figured it wouldn't be a problem), such as the database folder. So...

Issue#1:
Did I lose anything important, and if so is there a way to restore the important file(s)?


Issue#2:
How can I get my default page, which is Home.aspx, and in the folder 'Sub' to show up when a client views my website? I have amaster pagewhich applies to thefolder 'Sub' in the web.config,and that's why I setup starting page in that folder, but I read on another post in these forums that you have to have the starting aspx page in the '/' folder. Is there a work around?Also, does it have to be called 'default.aspx'?



Post Edited (AdamRTurner) : 8/16/2008 5:43:02 AM GMT

[tscontractors]

http://www.tscontractors.com/Sub/Home.aspx

That should be my home page, but I get a configuration error "The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty.
". Was I suppose to hook the website up to the database provided by default? If I was, I sort of deleted it accidentally using the publish feature of VS. Is there any way I can get it back?

[wisemx]

Hi,
You may be somewhat confused here. Don't fret, we can get you through this.
The Express DB is not supported, but if you have added a SQL Server to your account you can trick the Express conn.
Did you add SQL Server or are you only working with Express right now?
Salute,
Mark

[wisemx]

Hi,
Keep backups. http://community.discountasp.net/emoticons/wink.gif
Microsoft's SyncToy 2 is great for this, just click to backup your projects.

Use the Copy Website feature instead of publishing your application live.
This way you can still work with local applications and your remote applications will be treated as folders.

I don't see any reason you need a default page in the site root if you aren't using it.
I've created many sites that only use classic ASP in the root and ASP.NET in site folders.
Maybe a link to the problem someone pointed out?
Salute,
Mark