Kanjinghat wrote: it only reads .aspx files of an application if i copy an .aspx file from a web application and store it in a folder, which is set with web sharing for every one Not sure what you mean here. Are you trying to read the source of the aspx files? Or just the output? And are you requesting the files from an HTTP server (IIS) or trying to use file sharing? If you're trying to use HttpWebRequest to get the source of the files from a windows share you're using the wrong methods. If this is the case then you need to be using FileStream objects, not request or response objects. When you request files from a share over a network you don't use a web browser, you use windows explorer. Using the WebRequest objects is the equivelent of using your web browser. If you want the equivelent of windows explorer you use the FileStream objects. Also, this means you won't need to open up a security hole in your web application by exposing your config files publicly. Kanjinghat wrote: It will be very help ful for me if you let me the work around to be followed to read .config file. the default setting for .config files is in the httpHanlders section. It's defined as follows: In order to provide public access you'll need to change the handler for config files. I've never tried it, so I'm not positive which one. But my first guess would be System.Web.StaticFileHandler. If not you may have to roll your own handler which opens the files and spits out the contents to the response steam. But as a disclaimer, I want to say exposing your config files like this is a really bad idea. If you need programmatic access to the content of remote config files I would suggest using FTP instead. .Net doesn't have any built-in FTP libraries, but I've seen some free ones out on the web.
