Is it Possible to publish a website without web.config

I have database path mentioned in this file, along with the location so anybody can go and mess with the database, that is the reason i want to secure this file along with other code.

No, it's not that "anybody can go and mess with the database" unless they have FTP or otherwise exclusive access to your location. The web.config is non-downloadable. It is specially protected and there's no way someone can see it (try it out,you'll get a 404 on that address).

just users who have direct access to your web directory can see the contents of there , so they should be admin.
if you want to hide those information from users who access to your web directory, you can encrypt them by using two way encryption, I mean you can put encrypted password there and decrypt it when you want to use it.
http://www.codeproject.com/KB/security/encryption_decryption.aspx

Also if you use .net framework 2.0 or higher version, it encrypt everything except web.config, that you can use the way I mentioned in previous post to hide the password or secure info from other users who access directly to the web directory.
Users who just browse your web can never access there!

thank you for the wonderfull comments, im my case how can i do this, i have webapplication running on IIS so the user will know the location and can see the web.config file so i want to protect the web,config file from the users who are accessing them.

> IIS so the user will know the location and can see the web.config file so i want to protect the web,config

Sorry, but I'm afraid I don't really follow. What do you mean with "the user"? Nobody can see the web.config file, unless they sit behind the computer or have remote desktop access to the computer running your IIS. But if that's the case, you should use regular Vista / XP user management to prevent access to that location. Better yet: simply don't allow others to sit behind your computer.

PS: what would you want to do about someone deleting your other files (aspx)? And what about someone adding an aspx. file that does nothing more then reading your web.config and dumping its contents (in case you encrypt it, there's still little security as long as people can simply access your files: all security in existence have one thing in common, don't give them the same access you have, otherwise security is not possible).