Re: What will many cores mean to future Windows releases?
- From: "Kyle A. Miller" <kyleNO@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 06 Jun 2007 11:28:14 -0500
Chris Burrows wrote:
However, out of the box, without any 3rd paty addons etc. .NET is much more capable of giving sufficient detailed information for the end user to feed back to the developer to identify precisely where the error occured (module, line no etc.). For example:
Out of the box, .NET does nothing on its own. It's just DLLs sitting on a drive. It takes a developer coding a solution to utilize it. If a developer has to code a solution, the developer might as well add good exception log and reporting, like madExcept. In the case of madExcept, it does more than the standard .NET error reporting, things beneficial to the user.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
That's nice of .NET, but it's still gibberish to the user. The error message might as well said "Something bad happened" or "AV Error at XXXX." All the user wants to know is "How can I fix this?" How does using .NET make this situation any better for the user? It doesn't. A blocking error is a blocking error. There are .NET features to improve the developer experience in debugging the problem, but there are Win32 solutions to do the same.
.
- Follow-Ups:
- Re: What will many cores mean to future Windows releases?
- From: Andre Kaufmann
- Re: What will many cores mean to future Windows releases?
- References:
- What will many cores mean to future Windows releases?
- From: Esteban Pacheco
- Re: What will many cores mean to future Windows releases?
- From: Paul Nichols [TeamB]
- Re: What will many cores mean to future Windows releases?
- From: m. Th.
- Re: What will many cores mean to future Windows releases?
- From: Paul Nichols [TeamB]
- Re: What will many cores mean to future Windows releases?
- From: Farshad
- Re: What will many cores mean to future Windows releases?
- From: Arthur Hoornweg
- Re: What will many cores mean to future Windows releases?
- From: Farshad
- Re: What will many cores mean to future Windows releases?
- From: Arthur Hoornweg
- Re: What will many cores mean to future Windows releases?
- From: Kyle A. Miller
- What will many cores mean to future Windows releases?
- Prev by Date: Re: Delphi win 32 & broken Webservices
- Next by Date: Re: future of codegear / delphi why not just c# dot net
- Previous by thread: Re: What will many cores mean to future Windows releases?
- Next by thread: Re: What will many cores mean to future Windows releases?
- Index(es):
Relevant Pages
|