blocks|key|1794758|text|有几个属性可以附加到类型以获得更好的调试支持。也许其中一个就是你所看到的？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1794759|http://msdn.microsoft.com/en-us/library/ms228992.aspx|offset|length|1794760|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1H|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

There are several attributes that can be attached to a type for better debugging support. Perhaps one of these is what you're seeing?

<a href="http://msdn.microsoft.com/en-us/library/ms228992.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms228992.aspx</a>

blocks|key|1797326|text|我猜是因为这是你无权进入的受保护的或私有的财产。因此，您不能在代码中使用它，但可以在调试器中看到它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1797327|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I'm guessing it's because it's a protected or private property tht you don't have access to. You can't use it in code for that reason, but you can see it in the debugger.

blocks|key|1797340|text|调试器和intellisense在要显示的内容方面具有非常不同的目标。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1797341|Intellisense正在尝试提供可在对象上有效调用的成员集。本质上可访问的成员和扩展方法。这里的目标是帮助指导用户编写有效的代码。|1797342|调试器正在尝试提供对对象的运行时状态的检查。它不关心可访问性，而是将所有相关信息显示出来。它甚至允许通过用户扩展定制显示。这意味着您经常会看到对象上根本不存在的成员，或者用户代码无法访问的成员。|1797343|后者在您的场景中发挥作用。Page类型确实具有RelativeFilePath属性。但它是内部的，您的代码无法访问它，因此Intellisense不会显示它。调试器不考虑成员显示的可访问性，因此提供了该值。|offset|length|style|CODE|1797344|entityMap^0|0|0|0|D|4|N|G|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@$H|R|I|S|J|K]|$H|T|I|U|J|K]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

The debugger and intellisense have very different goals in terms of what they want to display.

Intellisense is trying to provide the set of members which can be validly invoked on the object. Essentially accessible members and extension methods. The goal here is to help guide the user to writing valid code.

The debugger is trying to provide inspection on the runtime state of an object. It cares little about accessibility and instead puts all relative information up for display. It even allows for customization of the display by user extensions. This means you will often see members which simply don't exist on the object or are inaccessible from user code.

The latter comes into play for your scenario. The <code>Page</code> type does indeed have a <code>RelativeFilePath</code> property. But it is internal which is inaccessible to your code and hence Intellisense doesn't display it. The debugger does not consider accessibility for member display and hence provides the value.

When I inspect an object in the debugger, I see a lot more properties in the debugger than what is available in Intellisense or code.

For example, the Page object in ASP.NET in the debugger shows a property RelativeFilePath which has a value. But when I try to use it in code, it doesn't exist. Why is that? 

I looked up the property RelativeFilePath in MSDN, it exists for mobile controls. Not sure why it shows up then in the debugger for a regular asp.net control.

Difference between properties of an object showing in debugger vs proprties in Intellisense

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

当我在调试器中检查对象时，我在调试器中看到的属性比在Intellisense或代码中可用的属性多得多。例如，调试器中ASP.NET中的Page对象显示了一个具有值的属性RelativeFilePath。但是当我尝试在代码中使用它时，它并不存在。为什么会这样呢？我在MSDN中查找了RelativeFilePath属性，它...

问调试器中显示的对象属性与Intellisense中显示的属性之间的差异
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问调试器中显示的对象属性与Intellisense中显示的属性之间的差异EN