4.2 RC - System.Log may not be a good idea.

Just installed 4.2 RC and nearly every single class is giving an error.

as "using System;" is in each class then System.Log is visible in each class. Which conflicts with the logger I currently use.

Perhaps the Log class could go in a Dataobjects package.

This thread was imported from our support forum. The original discussion may contain more detailed answer.

DataObjects.Net

asked Feb 20 '10 at 02:43

Tony
53●26●26●28

One Answer:

oldest newest most voted

To be fixed ASAP - today we've already been discussing the issues related to logging, and two decisions were made: 1) Log classes will be turned into internal. The fact that they're public is actually a mistake. 2) By default we'll log nothing (otherwise Debug Output gets flooded with our messages).

answered Feb 20 '10 at 04:04

Alex Yakunin
2971●4●4●12

Both issues are resolved, changes will be @ Google Code in few minutes.

RC will be updated today in the evening.

(Feb 20 '10 at 04:04) Alex Yakunin

Your answer

Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!

toggle preview

community wiki

Subscription:

Once you sign in you will be able to subscribe for any updates here

Tags:

DataObjects.Net ×574

Asked: Feb 20 '10 at 02:43

Seen: 2,874 times

Last updated: Feb 20 '10 at 02:43

Subscription:

Related questions