asp.net application root folder issue

Question

0.00/5 (No votes)

See more:

I'm having a smaller problem...
The folder structure of my web app looks like this:
/ (contains main web app files)
/logs (contains logfiles)
/services (contains web services)

All parts of the app are using a common error log function. The error logger writes to files in the /logs directory. To get a hold of the log directory the log function uses logDir = HttpContext.Current.Server.MapPath(logDir); to get hold of the log direcory which is stored in the web.config under AppSettings. Nothing strange. This works fine as long as error logging is done from pages in the root folder. However, when an .asmx page logs the log function tries to log in /services/logs. I've been trying to put "logs", "~logs" and other stuff in the setting in AppSettings. How do I solve this?

//Thomas

Posted 3-Apr-11 10:36am

nordsluttning

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Keith Barrow · Answer 1 · 2011-04-03T12:41:00

It sounds like the ASMX service has a different root /sevices , and probably desirable.
You could parse the mappath to give the /logs directoy but, unless there is a specific requirement to log to there, IMO it is better to keep the logs seperate.

One further suggestion, you could look at Log4Net[^] it's free, open source and pretty robust to failure (the last point is difficult to achieve in a logger!). The one draw-back is that it isn't guarenteed that the log will be written to (i.e. if an exception is thrown while logging, the log entry might not be written - part of its fail-over nature). That said, I've used it lots and had very few problems. One further thing is that it allows you to log to different stores, such as SQL or Text ( or a combination, or a custom store!) it also auto-rolls up logs if you want, and you can define a retention policy. It can be a little difficult to configure, but there are lots of resources out there. I'm not connected to the log4net project BTW, I just think it is fantastic :-).