How can we help you today? How can we help you today?
Willem.van.Rumpt

Activity overview

Latest activity by Willem.van.Rumpt

Ants Performance Profiler 7 & Windows Phone
Hi, Last year, the roadmap indicated that the profiler that the v7 release (then slated for Q4 2011) would allow profiling WP7 applications. Is this still planned for the upcoming release? Kind Reg...
3 followers 3 comments 0 votes
What's the difference between the two forums?
Hi, My apologies for the quite vague subject line, but can someone tell me what the difference is between the "Help us shape future versions of ANTS Performance Profiler" (http://antsperformancepro...
2 followers 2 comments 0 votes
Line-level timings in Silverlight
Hi, I know that line-level timings in Silverlight are currently not supported, but are there plans to support them in future releases? Kind regards, Willem van Rumpt
3 followers 5 comments 0 votes
Hi Alex, I'm not sure how to reproduce the problem with inherited method taking you to the top of the source file. Could you give an example where it happens? I have a hard time tracking down what might be causing the trouble. I encountered it when navigating to base.OnInit() in the Control class in the System.Web assembly. I made an isolated test project to rule out as much as possible and found the following weird behaviour: * navigating to base.ResolveUrl(), base.CreateChildControls(), base.LoadControlState() and base.SaveControlState() work as expected * navigating to base.OnInit(), base.OnLoad(), base.AddedControl() and base.Render() brings me to the top of the file I tried several other inherited members, some work, some don't. The last feeling I got was that it has something to do with the types of parameters. Methods with parameters of type System.EventArgs and types in the same namespace as the assembly were failing. The ones with no parameters, or parameters of type Object and String seem to work. If I find more, I'll let you know. I understand about it opening reflector instead of decompiled code in VS in some circumstances. Unfortunately we just have to fix these case-by-case, so I'd appreciate you letting me know any examples you find. I'll let you know when I encounter them. Sometimes it gets a bit confusing and I'm not sure anymore if I was expecting it to popup or not, since I was focussing on something else. We are thinking about making opening reflector optional, would you like it enabled by default (assuming we fix it all the time when you've already decompiled the assembly)? Optional is always good [image] I think my preferences would go to disabled. I think I would extend the option to "off / only in absence of source / always". I don't like windows popping up or stealing focus. I consider Reflector to be (or rather: I use it as) an external tool window of the IDE, replacing the build-in classbrowser, and personally, I'm not that fond of toolwindows floating around. The ideal situation for me would be to (be able to) integrate (dock) Reflector in the IDE. The next best thing would be Reflector as it is now, but with the option of displaying the disassembly in the VS IDE. Regards, Willem / comments
Hi Alex, I'm not sure how to reproduce the problem with inherited method taking you to the top of the source file. Could you give an example where it happens? I have a hard time tracking down wh...
0 votes