Hi fellows,

I wanted to test my application(built after the book), and I compiled it with -p and -v options. Everything got encrypted except the web.config. What should I do to web.config encrypted too? It's kind of scary senario to put the config-file uncrypted in a shared hosting environment.

Thanks in advance!

Hi everybody,

I find the answer(s) to my problem and I want to share that with you.
First of all, I wanted to confess my misunderstanding about the part of the book about deploying and compiling the solution. I expected that after pre-compiling with -p and -v switches then I'll get all files compiled except text, images, html, and xml files.
I was pretty sure that I read somewhere in the book that one of the reasons we want to pre-compile our applications was to hide our code and configurations from the prying eyes. Therefor I got worry when I saw the web.config stil in its xml format.

However, after a few hour searching the Internet and right asked questions!!! I found two solutions for my problem.

1. ProtectedConfigurationProvider Class
   which is the most adequate solution if we want to deploy our application on a shared webserver(outside of our company)
   
2. Encrypt Configuration Sections in ASP.NET 2.0 Using DPAPI
   Which is a OS-level data protection service which demands access to the OS.

Kindly regards from Sweden