There’s been close to 25 000 downloads of the buggy bits lab set, YAY!!! :) but now I think it’s time to expand it a bit with some new labs.
I have a few different issues in mind but I wanted to check in and see if there is something specific you want to see in the new lab set.
I know that the first request I’ll probably get is to include something about COM debugging or debugging RCW/CCW leaks and I might do that, but I just want to say that I am struggling a bit with this. Just for fun I installed VB 6.0 the other day to create some nasty COM component, but it has just been so long that I’ve forgotten how to write code without the VS.NET intellisense :) you don’t really realize how good it is to have something until you don’t have it anymore…
Looking at the old labs, my main goal there was to include the basic scenarios and to make sure that the labs could be installed in a few short steps without having to register this and that. They do require IIS though, but I wanted to see what your thoughts are on some items before I start planning the new lab set
1. Are you interested in Winforms debugging, Silverlight debugging, WPF debugging? It’s all essentially the same since the techniques are the same no matter what “shell” you use, but still… 2. Does it matter if you need IIS installed on the machine? 3. Do you want to see debug diag examples?
1. Are you interested in Winforms debugging, Silverlight debugging, WPF debugging? It’s all essentially the same since the techniques are the same no matter what “shell” you use, but still…
2. Does it matter if you need IIS installed on the machine?
3. Do you want to see debug diag examples?
Debug diag would be interesting, particularly since I can't get it to play nice w/ Win 2k3 x64 (seems to require a reboot every time I change rules).
I would like to see the ability to specify the number of cores my application can take advantage of. It would be nice to see how my multi-core changes affect a single core, ( or any number less than what my dev machine has ), users.
It would be interesting to see some really tough asp.net problems. For example, we're seeing a problem recently where our production site shows a high amount of memory fragmentation and this prevents some 3rd party unmanaged components from loading (They need a certain amount of contigous memory to load). It would be nice to see how you would go about troubleshooting and reproducing a problem like that.
Yes, please focus on ASP.NET stuff since it's probably most researched area of debugging
.NET Redirecting without the exceptions So, what’s new in the CLR 4.0 GC? Source Control for Visual
.NET debugging only.
Would love to see some of these labs turn into Video sessions.
I have no problems requiring IIS to be installed. Anything ASP.NET, WCF or WF related i'd love to see.
hehe, you nailed with COM RCW/CCW bugs, but I have written those in .NET, overall I don't think there are a lot of people using (having issues debugging) these technologies
I would like to see more focus maybe on web technologies like Silverlight/ajax, etc
Silverlight debugging would be a godsend
about locks,deadlocks and load of examples
I would love to see how to monitor handle leaks in .NET process (not necessarily ASP.NET). and also, Advanced use of windbg.
Great ideas, I like all of them.
Russ, about your comment "I would like to see the ability to specify the number of cores my application can take advantage of. It would be nice to see how my multi-core changes affect a single core, ( or any number less than what my dev machine has ), users." can you expand on this a little bit...
You can set processor affinity (through a windows API, i believe it is called something like SetProcessorAffinitiyMask but you will want to be very careful with that since it can get you into deep trouble if you run with the server version of the GC) Why do you want to specify the number of cores? is it just to test your application on a single core box, or for some other reason?
Hi Tess, 90% of our apps are desktop apps (native C++ mixed with .Net Winforms). So I'd like to see samples without the IIS. We also have often a lot of trouble with COM DLLs and mixed DLLs written in C++ or C#, but not in VB6 anymore :-) . So any sample in this area would be welcome.
1. Don't care much about UI-s.
3. Yes, please :).
com interaction would be very interesting, mixed mode, and also cases where we would make more debugging in native stacks , get to frames, unassembly to get values, understanding FPO and different call conventions....
not asking to much am i ? :)
It will including the multithreading?