首页> 外文期刊>MSDN Magazine >BUGSLAYER: Unhandled Exceptions and Tracing in the .NET Framework 2.0
【24h】

BUGSLAYER: Unhandled Exceptions and Tracing in the .NET Framework 2.0

机译:BUGSLAYER:.NET Framework 2.0中的未处理异常和跟踪

获取原文
获取原文并翻译 | 示例

摘要

By now, you've certainly heard about the big changes coming in Visual Studio~® 2005, but when it's time to move your code over it will be the small things that trip you up. In this column, I want to cover two of the many excellent changes that you could easily overlook as you make the move to the new runtime and development tools. Don't get me wrong. I don't mean to make the transition sound dangerous. The truth is, your ported code will probably work just great with nothing more than a recompile. But there are things you should know. When you finish reading, you should also check out the "What's New" sections in the documentation. The first change I'll talk about is how the common language runtime (CLR) in the Microsoft~® .NET Framework 2.0 now handles unhandled exceptions. Then I'll discuss some of the excellent enhancements to the tracing system so you can get the best information from the field.
机译:到现在为止,您当然已经听说过Visual Studio〜®2005中的重大变化,但是当需要将代码移到它上面时,将会使您绊倒。在本专栏中,我想介绍许多优秀的更改中的两个,当您转向新的运行时和开发工具时,这些更改很容易被忽略。不要误会我的意思。我并不是要使过渡听起来很危险。事实是,移植的代码仅需重新编译就可以很好地工作。但是有些事情你应该知道。阅读完之后,还应该查看文档中的“新增功能”部分。我要谈的第一个变化是Microsoft〜.NET Framework 2.0中的公共语言运行库(CLR)现在如何处理未处理的异常。然后,我将讨论跟踪系统的一些出色增强功能,以便您可以从现场获取最佳信息。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号