Shawn Burke : Discussing the Release of .NET Source Code
- Posted: Oct 03, 2007 at 9:18 PM
- 18,516 Views
- 15 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- MP3 (Audio only)
- Mid Quality WMV (Lo-band, Mobile)
- WMV (WMV Video)
Matt Winkler and David Tesar catch up with
Shawn Burke to talk about
the announcement today that the source for the .NET Framework will be made available.
In this video we find out about how this is all going to work and see it in action as Shawn steps into the Windows Forms code from Visual Studio. Shawn also talks about how this has been something he has been working on for a long time in order to bring a really deep debugging experience for .NET developers.
Lots of excitement about this today for sure.
In this video we find out about how this is all going to work and see it in action as Shawn steps into the Windows Forms code from Visual Studio. Shawn also talks about how this has been something he has been working on for a long time in order to bring a really deep debugging experience for .NET developers.
Lots of excitement about this today for sure.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
This is slightly cool. But why do you have to load symbols for each assembly manually. Cant you just load the whole thing for us who have enough ram?
I would however hope you can enable it always loading with the download version that is going to come out.
I think he meant that (last part of the interview questions). The download of the source code (whichever way they package it) will allow offline use of this as well (the "airplane" example).
Can't wait to use it (more than that, just looking at the .NET code and learning from that)
I have two questions:
1. Will this work with the Compact Framework too? I really hope it will.
2. Will we get the source to InternalCall functions? I'm guessing no, but it would be cool if we did.
Will we see the C#/VB.net compiler opensourced at some point?
Can you have a symbol proxy?
Want to make the killer RSS ag app? Add a Delete all post with ___ URL option .
Visual Studio can load symbols in two modes:
1) Load them for every binary in the process, or
2) Load them manually.
You can put it into (1) mode above by not checking the "Load symbols manually" option in Tools > Options > Debugging > Symbols.
I don't think you'll want to do this when using the Reference Source stuff, and it's purely for reasons relating to the performance of your F5-experience.
Problem number 1: There may be lots of symbols out there and they tend to be large. If you're on a slower connection, it could take a fair amount of time to launch your first debugging session. You could easily be looking at 50 megs of symbols. Fortunately, these do get cached locally.
Problem number 2: And this is the big one. VS doesn't really have any way of remembering which symbols it found and which ones it didn't between debugging sessions. Since you've added an external server for lookup, it's going to go out and ping for every symbol that it doesn't find locally/cached. It doesn't know that the symbols for user32 or ntdll aren't on that server, so it's going to ask EVERY time.
Again, depending on how fast your internet connection is, this may or may not be an issue. But ASP.NET loads something like 18 DLLs into it's process space, and in my quick testing it made the F5 time go from ~2 seconds to 5-or-6, which just isn't acceptable. By doing the manual load, you avoid this problem altogether.
I have been talking with the VS debugger guys about ways to make this smarter/more effiecient but we haven't found a robust solution quite yet, but we'll keep working on it.
Hope that helps,
Shawn
I saw your video, even i feel good now that source is available to us & becomes easy to debug & find out the internals working & loopholes
My question is whether we can get symbols for the existing visual studio 2005 once orcas is released.
You'll need Orcas to view the code. In order to install Orcas, you'll need to install the .NET Framework 3.5 which includes updates to the .NET Framework 2.0 binaries (referred to as Redbits), for which symbols will be available. So we won't be releasing source/symbols for binaries that shipped with VS 2005 because you could never actually debug them - once you've got Orcas on the machine to do the debugging, you can no longer have the VS 2005 binaries.
Remove this comment
Remove this thread
close