Configuring Visual Studio to Debug .NET Framework Source Code


It’s finally here – the launch of the .NET Reference Source project.  This post (hopefully!) contains everything you need to know.  Over the past few weeks, we ran a pilot of this feature and collected lots of great data that helped us work through some issues and understand where people were likely to have problems. 


First, though, if you have any problems, please make sure you’ve followed all of the steps exactly as described.  If you’re still having problems, please check the FAQ/Troubleshooting section at the bottom.  If that doesn’t work, post a comment below and I’ll look into it.


BASIC SETUP


Note this functionality is not available on the Express versions of the Visual Studio 2008 products.


1) Install the Visual Studio 2008 QFE.  This Hotfix just updates a DLL that’s part of the Visual Studio debugger that fetches the source files, more details on the download page.


 UPDATE:  If you get an error installing the Hotfix , try inserting your VS 2008 DVD and then running the Hotfix EXE again.  We’re looking into the root cause – it’s related to having a prior version of VS 2008 (e.g. Beta 2) installed on the machine.  But this workaround should allow the Hotfix to install properly.


 UPDATE (1/18): There were some problems with the QFE link above that have been addressed, sorry for the inconvenience, it’s fixed now.


2) Start Visual Studio 2008 and bring up Tools > Options > Debugging > General.  If you are running under the Visual Basic Profile, you will need to check the box on the lower left of the Options Dialog marked “Show All Settings” before continuing (other profiles won’t have this option).


Set the following two settings:



  • Turn OFF the “Enable Just My Code” setting

  • Turn ON the “Enable Source Server Support” setting

Your settings should be as below:


image


3) Next, bring up the “Symbols” Page and set the symbols download URL and a cache location.  Specifically, set the three settings below:




    • Set the symbol file location to be: http://referencesource.microsoft.com/symbols

    • Set a cache location.  Make sure this is a location that your account has read/write access to.  A good option for this is to place this path somewhere under your user hive (e.g. c:\users\sburke\symbols)

    • Enable the “Search the above locations only when symbols are loaded manually” option.

When you’re finished, the settings should look like the image below:


image


Setup is done!  That’s it, really!


DEBUGGING INTO FRAMEWORK SOURCE


For this simple example, we’ll start with a blank C# Windows Application project, but it will work the same with a VB, Web, or WPF project.  To walk through this, go ahead and create that project.


Set a breakpoint in Form_Load:


image 


Now run your project to hit that breakpoint and go to your Call Stack window (CTRL+ALT+C).  In the Call Stack, right click a frame that starts with System.Windows.Forms.dll, and choose “Load Symbols“.  This will load the symbols for the System.Windows.Forms assembly, which are about 10 megabytes, so the speed of the download will vary according to your connection speed.  Note that Visual Studio may be unresponsive during this time.   However, this download is a one-time cost for each assembly.  The symbols (PDB) file will be cached on your machine, in the directory specified in the steps above. 


Loading Symbols Manually


This will load the symbols for the DLL from the server, and you’ll see some information in the status bar to reflect this.  Note that when this completes, the call frames will turn black and line numbers will be available.  Note you’ll need to do the Right Click -> Load Symbols step each time you launch a debugging session (but, again, the symbols will now be cached locally so they won’t have to download).  For more information on this, see the ADVANCED USERS section below.


image


You have now loaded the symbols for the Windows Forms DLL and can begin viewing the code.  You can view code in any way that you normally would in a debugging session.  In this case you can either Step In to the line of code above, or you can double-click one of the frames in the Call Stack Window.   For this case, we’ll step in (F11).


The first time you step into code, we’ll be presented with the EULA for accessing the source code.  Please take the time to read this EULA.  If you agree to the terms of the EULA, hit ACCEPT, and the source will then be downloaded.


That’s it! You’re now debugging .NET Framework Source!


Debugging Form.cs in Windows Forms


Now, for each assembly that you’d like to debug into just repeat the steps above (note you’ll only see the EULA once, not for each file).


There are times when the Assembly you’d like to debug into isn’t on the call stack, for example in the code below:


image


Before you step in to Graphics.DrawRectangle, you need to get the symbols for System.Drawing.Dll loaded.  To do this, we use the Modules Window (CTRL+ALT+U).  This lists all of the modules (DLLs) loaded by the debuggee.  Just find System.Drawing.DLL in this list, right click, and choose Load Symbols.


Load via Modules Window


Note that once a symbol file is loaded, the path to the symbol file shows up in the “Symbol File” column.


You can now step into the Graphics.DrawRectangle code above using F11!  In this case, note, you’ll have to step through the PaintEventArgs.Graphics property code first.


ADVANCED USERS


Normally, each time you launch a debugging session, Visual Studio attempt to download symbols for each DLL that loads into the debuggee process.  As part of this process, it asks each path specified in the Debugging Symbols dialog for the corresponding PDB.  Some projects load a LOT of DLLs which won’t have symbols available, so this process can significantly impact debugger startup time as this probing occurs.  It is mainly for this reason we’ve recommended manual symbol loading in the steps above; we don’t want using this feature to degrade the debugging experience across-the-board.


There is, however, a way to allow automatic symbol loading (which avoids the “Load Symbols” step) in a way that minimizes performance impact.   This is for more advanced users because it requires regular trips back to this Debugging Symbols Dialog.  Note you can quickly get to this dialog by choosing the “Symbol Settings…” item on the right click menus pictured in steps above form the Call Stack or Modules windows.


The key is to get all of the symbols for a given project type downloaded and cached locally, then turn off the automatic symbol downloads.  This will prevent the pings at debugger startup as well.


To do this, configure your setup as above with the following difference: Uncheck theSearch from the above locations…” item on the dialog.


Now, launch your project in the debugger.  This will cause all of the symbols available for the DLLs in your process to be downloaded at on-demand as the DLLs are loaded into the process.  Depending on your connection speed, this could take a while (it’s generally about 50MB of symbols), so it’s a good idea to hit F5 then go do something else for a while.  Again, these symbols are cached so this is a one-time cost.  Visual Studio will likely be unresponsive during this download process.


image


Once that process has completed, stop the debugger, and UNCHECK the the Reference Source Server symbol location, and hit OK:


image


Now when you launch the debugger, symbols will load automatically and you’ll be be able to step in and through call stacks normally.  Note if you switch to a different project type (that has different assemblies), or have assemblies that are loaded later by your project, you can just repeat these steps to get any assemblies you don’t have cached locally). 


FAQ/TROUBLESHOOTING


1) Which assemblies are currently available for symbol/source loading:


  • Mscorlib.DLL

  • System.DLL

  • System.Data.DLL

  • System.Drawing.DLL

  • System.Web.DLL

  • System.Web.Extensions.DLL

  • System.Windows.Forms.DLL

  • System.XML.DLL

  • WPF (UIAutomation*.dll, System.Windows.DLL, System.Printing.DLL, System.Speech.DLL, WindowsBase.DLL, WindowsFormsIntegration.DLL, Presentation*.dll, some others)

  • Microsoft.VisualBasic.DLL

2) When I choose “Load Symbols” I get an Open File dialog asking for the PDB.

This can be caused by one of four situations:



  • You didn’t configure the symbol location URL properly from basic setup above.  Ensure it’s http://referencesource.microsoft.com/symbols.

  • You chose a cache symbols directory that your user account doesn’t have write permissions for.

  • You attempted to Load Symbols for a DLL that’s not available in the list above

  • You have a different version of the .NET Framework on your machine – this can happen, for example, if you’re running a Windows Server 2008 Beta.  To check this, go to the Modules Window in Visual Studio (CTRL+ALT+U) and ensure that the version number of your mscorlib.dll is 2.0.50727.1433, as below.  If not, make sure you install the RTM Version of the .NET Framework 3.5.



  • Check your “C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE” (or wherever you installed VS) for a file called symsrv.no.  If that file exists, rename it to symsrv.yes, and restart Visual Studio. 

3) When I try to open or step into a source code file, I get a dialog that says “Source is not available for this location” or I get an Open File dialog for the file.

First, see FAQ item (2) above to ensure the symbols for the DLL were loaded successfully.  You can verify this by looking in the Modules Window under the “Symbols Status” column.


If the Symbols Status is “Symbols loaded.”, check the following.



  • If you have configured Microsoft Symbol Server in the past, you may have already downloaded symbols for this DLL that don’t contain source information.  Try specifying a different cache path or deleting your existing cache path, and then repeating the Load Symbols command.   See FAQ #4 for more information on this.

  • Ensure you have checked the “Enable Source Server” item on the Tools -> Options -> Debugging -> General page

  • Ensure that your account has read/write access to your cache path

  • If you have _NT_SYMBOL_PATH set, it will override these settings.  Details here.

4) I also use Microsoft Symbol Server to download symbols.  What’s the difference? Can these two programs co-exist?

Microsoft Symbol Server provides symbols without any source information in them.  That information has been removed (sometimes referred to as “stripped”) before publishing.  The symbols provided on the Reference Source Server are full symbols with debugging information.


The key to using both is to have your Reference Source path above the Symbol Server Path so that those symbols are searched/found first.  As described in the ADVANCED USERS section above, you’ll likely want to launch your debugger once with this configuration to get all the symbols downloaded, then uncheck both of these paths to avoid debugging launch slowdowns in the future.  Also note that this may conflict in the future as more DLLs are added to the Reference Source Project.  Meaning, if you’ve already downloaded the Symbol Server symbol, you’ll need to delete that or change your cache path to get the Reference Source one (Visual Studio has no way of knowing which is which).


image


One final note here, if you have the Microsoft Symbol Server configured via _NT_SYMBOL_PATH, you’ll need to add the Reference Source path above to that path as well – _NT_SYMBOL_PATH overrides the above settings.


5) Does this work with 64-bit?

Yes, we’ve also provided 64-bit versions of the PDBs.  Note some DLLs work on multiple architectures, so not all of them need a separate 64-bit PDB.


6) How do I set breakpoints in Framework code?

Visual Studio requires the code to exactly match what is expected by the PDB.  The source publishing process, however, makes some small updates to the code, such as pushing a standard copyright banner to the end of the source file.  This changes the signature (CRC) of the code file.  However, it’s still easy to set a breakpoint. 


Just set your breakpoint as normal (you’ll see it fails with a little warning icon), then right click the breakpoint and choose “Location…”


image


Then check the “Allow Source to be Different” box, hit OK.


image


Now the breakpoint will set successfully.


If you find yourself doing this often, you can also disable source matching in general by disabling Tools->Options->Debugging: “Require source files to exactly match the original version.”


7) Why don’t some features like “Go To Definition” work?

Browse database information is separate from symbol (PDB) information within the debugger, so that information is maintained by the project system when a project is compiled and is not present within the symbol files.  So, unfortunately, that ability is not available here.


8) Why are some member or local variables unavailable?  Why can’t I step into certain functions or lines of code?

The .NET Framework bits that you have installed on your machine are “retail” bits, which means they are optimized for size and performance.  Part of this optimization process removes certain information from the process when it is no longer needed.  Debugging retail assemblies reflects this.  However, most debugging information is still present in the session, and setting breakpoints earlier in a function often allows it to be visible.   Another aspect of retail builds is that some small methods may be “inlined” which means you will not be able to step into them or set breakpoints in them.  But for the most part you can step and debug as normal.


9) Why does it take so long to download some source files?

Some source files are very large – nearly 1MB – and unfortunately many of these are the common ones to download.  However, most are significantly smaller and download quickly.  Source files must be downloaded each time you restart Visual Studio.  They are not persistently cached like symbols are.


10) Can I just download all of the code at once?

Not currently, but we are currently working on enabling this functionality in the future.


11) When I debug into VB code, for example in Microsoft.VisualBasic.dll, there is a C# style comment at the bottom, is this a bug?

Not really – we do run a post processing step when publishing the code and it adds a standard copyright banner at the bottom.  The processor, at this time, isn’t able to support multiple comment formats.  Having it in a non-VB format doesn’t affect the debugging functionality in any way.


12) I got to a source file and all that downloaded was a blank file?

This is something we’ve seen intermittently but have not been able to diagnose.  If you see this, usually the workaround is to just restart VS, which will force the file to reload.  If you observe this behavior, please use the “Email” link on the left to email me the name of the file that failed and about what time the failure occurred.


13) What happens if I download a Hotfix or a Service Pack?  Will I be able to get source for that?

We’ve built a system that allows us to publish any number of versions of source and symbols for a given product.  We haven’t made any firm decisions on how often we’ll publish source and are open to customer feedback on those issues.  For example, it’s clear that publishing source for each Service Pack makes sense, but it’s unclear if we’ll be able to do so for each Hotfix.  Again, we’re looking forward to feedback here.


In the meantime, also note that symbol files may no longer match a module if a framework DLL has been updated via a Hotfix. In those cases, the modules window will indicate that the symbols could not be downloaded for that module. Assuming a new symbol file was published, it can be downloaded and cached using “Load Symbols”.


14) Can I point a web browser at the symbols URL and download the symbols directly?

No, you’ll get an HTTP 400 (Bad Request) response.


SUPPORT

If you have any other questions, please visit our new MSDN Forum on the topic: Reference Source Server Discussion.


Thanks!

Comments (329)

  1. In what I honestly believe is a stunning announcement, Scott Guthrie blogged moments ago that we have

  2. Si vous ne vous en souvenez pas, Scott Guthrie avait annoncé, il y a quelque temps , que Microsoft ferait

  3. Qualche tempo fa Scott Guthrie aveva annunciato che con Visual Studio 2008 la Microsoft avrebbe reso

  4. Scott Guthrie has just posted the excellent news that everything is now in place for people to access

  5. In what I honestly believe is a stunning announcement, Scott Guthrie blogged moments ago that we have

  6. Daniel Moth says:

    Video on debugging into the .NET source code

  7. GenoMind says:

    期待N久的.NET Framework源码终于出来了!

  8. Stefan Falz says:

    Wie bereits hier geschrieben, wollte Microsoft den Sourccode der .NET Framework Bibliotheken veröffentlichen.

  9. Todos los fuentes del framework de .net se han publicado hace algunos minutos, están disponibles en un

  10. Todos los fuentes del framework de .net se han publicado hace algunos minutos, están disponibles en un

  11. Scott Guthrie has just posted the excellent news that everything is now in place for people to access

  12. ASPInsiders says:

    It’s live and you can give it a try now! Ten minutes ago Shawn and Scott released the hounds. If you’d

  13. L’annonce avait été faite par Scott Guthrie il y a un peu plus de deux mois maintenant, et relayée ici

  14. .NET Framework Library Source Code now available

  15. A few minutes ago Scott Guthrie , Shawn Burke and Scott Hanselman announced the availability of .NET

  16. .NET Framework Library Source Code now available (ScottGu’s Blog)より まってました。Visual Studio 2008 のでバック中に CLR 内にステップ実行を可能とするシンボルサーバと設定方法が公開されています。

  17. 青松阳光 says:

    .NET框架源码终于可以看到了,大家可以到ScottGu

  18. ScottGu’s Blog と Shawn Burke’s Blog からです。 .NET Framework Library Source Code now available (Scott さんの投稿)

  19. bwaring says:

    When installing the QFE I received a fatal error. The following was detailed in the QFE log file:

    "An installation package for the product [2] cannot be found. Try the installation again using a valid copy of the installation package"

    I inserted the VS2008 installation DVD into my computer and re-ran the QFE, this time, it installed successfully.

  20. f9inux says:

    .NET Framework终于开源了!

  21. sburke says:

    Yes, we’ve seen other reports of this and had considered that work around – thanks so much for reporting back!

    Thanks,

    Shawn

  22. L'annonce avait été faite par Scott Guthrie il y a un peu plus de deux mois maintenant, et relayée

  23. In case you missed it, a couple of months back we announced that we’d be making the source for .NET (among

  24. 孟宪会 says:

    .NET Framework Library 正式开源

  25. B# .NET Blog says:

    That's right – we've published the .NET Framework Library Source Code to the public. Scott Guthrie

  26. These are the web’s most talked about URLs on Thu 17th Jan 2008. The current winner is ..

  27. .NET Frameworkのライブラリのソースコードが公開になったそうな!!!!

  28. .Live says:

    Scott发布了消息,.net源代码码已经可以在vs2008中调试 地址 下面的地址是详细的vs2008设置步骤 详细配置

  29. In case you missed it, a couple of months back we announced that we'd be making the source for .NET

  30. WiredPrairie says:

    You’ll need to install a hot fix first … once you sign in using your Windows Live account, (and possibly updating your profile like I had to), you’ll run the install. Don’t bother with the File Transfer Manager. It’s definitely…

  31. 横刀天笑 says:

    看到.net框架代码发布了,兴奋了一下,把在Visual Studio 2008上配置的内容翻译了一下,只翻译了原文的基本步骤,高级用户篇和QA没有翻译。要欣赏原文请点击这里

  32. Denny.NET says:

    .NET Framework Source Released

  33. Last October, ScottGu blogged about releasing the source code to the .NET Framework libraries , and enable

  34. .NET Frameworkのライブラリのソースコード公開

  35. .NET Frameworkのライブラリのソースコード公開

  36. eqiang says:

    .NET Framework Library 正式开源

  37. Last October, ScottGu blogged about releasing the source code to the .NET Framework libraries , and enable

  38. Im Oktober hatten wir ja bereits angekündigt, den .NET Framework Source Code aus einer Visual Studio

  39. asheng says:

    Wednesday,January16,20082:50PM(2008,1.16),ScottGu在博客上公布了:微软在MS-RL协议下终于公开了.NETFramework源代码。我们可…

  40. With the big announcement today, everyone’s looking at the Framework sources like mad. Make sure you

  41. wsliu says:

    期待已久的.NET Framework终于在本周开源了,微软在MS-RL协议下终于公开了.NET Framework源代码,我们只可以自由查看,不允许直接进行修改。 第一批开放的源代码包括: .NET基本类库

  42. re: .NET Frameworkのライブラリのソースコード公開

  43. שחר.נט says:

    וכל מילה נוספת מיותרת .

  44. Guys ……. Check this out Written by Shawn Burke of Microsoft… It's finally here – the launch

  45. Как мне не хватало возможности во время отладки пройтись по коду FCL. Приходилось брать рефлектор или

  46. Endlich scheinen die Tage des Wartens auf die Quellcodeunterstützung (BCL) im Debugger vorbei zu sein…Hier die erste Anleitung wie man dieses Feature nachinstallieren kann

  47. 正如 先前 所 许诺 的,.NET Framework源代码已经对开发者开放,现在可以在Visual Studio 2008中直接对.NET Framework 进行源码调试 。

  48. nigo@bk.ru says:

    Ночью пришло письмо от Shawn Burke с благодарностью за участие в тестировании .NET Reference Source project, а самое главное с информацией о том, что исходники .Net для отладки доступны в публичном доступе.

  49. Several months ago Scott Guthrie mentioned that developers will be able to debug the .NET Source Code.

  50. conannb says:

    That’s cool ~

  51. Qingping says:

    看到.net框架代码发布了,兴奋了一下,把在VisualStudio2008上配置的内容翻译了一下,只翻译了原文的基本步骤,高级用户篇和QA没有翻译。要欣赏原文请点击这里 基本步骤

    注意,…

  52. 正如 先前 所 许诺 的,.NET Framework源代码已经对开发者开放,现在可以在Visual Studio 2008中直接对.NET Framework 进行源码调试 。

  53. Scott Guthrie has announced the release of source code for some of the .NET framework libraries . This

  54. .NET Framework Source Now Available

  55. As stated on ScottGu's blog in his latest post , the .NET Framework Library Source Code is now available

  56. tonypujals says:

    Very, very nice — thanks!

  57. Redwerb says:

    Scott Guthrie announced the release of the .Net framework code today (comments and all!). Now you can

  58. dpwebs says:

    in my case this issue with hotfix is not necessarily related to having beta2 previously installed.

  59. Nisus says:

    Наконец-то опубликованы исходные коды .Net Framework в виде, пригодном для их от

  60. Microsoft hat nun, wie angekündigt, den .Net Sourcecode veröffentlicht. Wie man dies nun in Visual Studio aktiviert, ist unter folgendem Link zu finden: http://blogs.msdn.com/sburke/[…]source-code.aspx Dazu ist es nötig einen kleinen

  61. greatbag says:

    .net framework开源啦

  62. Murat YILMAZ says:

    .NET Framework Library Source Code now available

  63. I sorgenti del .NET Framework 3.5 sono stati rilasciati!!!

  64. 笑缘 says:

    期待已久的.NETFramework终于在本周开源了,微软在MS-RL协议下终于公开了.NETFramework源代码,我们只可以自由查看,不允许直接进行修改。

    第一批开放的源代码包括: …

  65. .Net开源了,配置链接

  66. gsuttie says:

    Shawn getting an unknown publisher when the active x contorl loads so I cant get the hotfix to begin with.

  67. Sean Burke has all the details

  68. dario-g says:

    Jak można się dowiedzieć już z niejednego źródła  można już podczas debugowania aplikacji

  69. 昨年末から首を長くして待っていました。 設定方法はこちら Shawn Burke’s Blog : Configuring Visual Studio to Debug .NET Framework Source Code QFE(修正モジュール)のインストールで失敗。以下のメッセージ。 このソフトウェア更新の対象製品はこのコンピュータにイ

  70. It was announced with the release of Visual Studio 2008, now it’s here – follow this thorough step-by-step

  71. Microsoft has released the source code for .NET Framework. Personally I regard this decision and find

  72. You probably already noticed that Microsoft has enabled access to the source code of parts of the .NET

  73. Great news. Microsoft finally released a part of .NET Framework Source Code for debugging purposes. A

  74. VBandi says:

    Ígérték, vártuk, itt van. Én ugyan még nem próbáltam, de ScottGu

  75. El Bruno says:

    Buenas este tipo de noticia se reproduce como un politono de los malos. Anoche a altas horas de la madrugada

  76. El Bruno says:

    Buenas este tipo de noticia se reproduce como un politono de los malos. Anoche a altas horas de la madrugada,

  77. El Bruno says:

    Buenas este tipo de noticia se reproduce como un politono de los malos. Anoche a altas horas de la madrugada

  78. For at good blog posting describing HowTo, go here: Configuring Visual Studio to Debug .NET Framework

  79. Debug into the .NET Framework. It’s here .  Here’s how you configure VS to use it for debugging

  80. Oh happy day. I'm stepping into the .NET Framework source using the VS 2008 debugger. Shawn Burke

  81. I had my head down yesterday recording a few screencasts and missed this announcement – the .NET Reference

  82. I had my head down yesterday recording a few screencasts and missed this announcement – the .NET Reference

  83. Microsoft avait annoncé il y a quelque temps que le code source de .NET serait disponible pour aider

  84. I've been waiting for this day for a very long time. Starting today you can view or debug the source

  85. jkolonko says:

    Microsoft udostępnił źródła platformy .NET Framework w ramach projektu Microsoft Reference Source. Dzięki

  86. As you may have heard, Microsoft has released the .Net framework source to the world.  No, you cannot

  87. Shawn Burke has a nice article which explains how to enable Visual Studio to download the symbol files

  88. .NET Framework 3.5 – Código Fonte Com o lançamento do Visual Studio 2008 e do .NET Framework 3.5 a Microsoft

  89. ccatto says:

    Hey Now Shawn,

    This is really great to see.

    Thx 4 the info,

    Catto

  90. 桦林 says:

    期待已久的.NETFramework终于在本周开源了,微软在MS-RL协议下终于公开了.NETFramework源代码,我们只可以自由查看,不允许直接进行修改。

    第一批开放的源代码包括: …

  91. filipf says:

    I was just wondering – do these instructions also work with Visual Studio 2005?

  92. Warren Tang says:

    NETFrameworkLibrarySourceCodenowavailable ConfiguringVisualStudiotoDebug.NETFramewor…

  93. Holy Shepherd and Wingo, Batman!  .Net Internals at last!

  94. Finally. Follow Shawn’s steps. 

  95. mcp111 says:

    Does this also work with VS2005? The configuration options you mentioned are present in VS2005 also.

  96. vincent says:

    期待已久的.NET Framework终于在本周开源了,微软在MS-RL协议下终于公开了.NET Framework源代码,我们只可以自由查看,不允许直接进行修改。第一批开放的源代码包括:

    .NET基本类库:System,System.CodeDom,System.Collections,System.ComponentModel, System.Diagnostics, System.Drawing, System.Globalization, System.IO, System.Net, System.Reflection,..

  97. 為了提供 debug 的需要,  .NET 的大部份原始碼可以經由Visual Studio 2008設定, 直接在 debug 時, 自動進 .NET 的原始碼內容。目前已經開放的原始碼有:

  98. Nu finns det som utlovades tidigare, nämligen möjligheten att debugga källkoden till .NET Framework med

  99. Da jeg jo egentligt bruger stort set hele min arbejdstid og store dele af min fritid med .NET applikations udvikling, er det vel en nyhed der skal i min blog I praksis betyder det at man kan debuge ind i .NET’s kode, se hvordan den er bygget op, og even

  100. mcp111 says:

    if you want to know what the chinese guys said, here’s a handy translation link

    http://www.google.com/translate_t?langpair=zh|en

  101. sburke says:

    @ gsuttie

    >>Shawn getting an unknown publisher when the

    >> active x contorl loads so I cant get the

    >> hotfix to begin with.

    Note sure what you’re seeing – haven’t heard of this before.  Is it the Windows Live ID process you’re having problems with or downloading the Hotfix itself?

  102. Nu finns det som utlovades tidigare, nämligen möjligheten att debugga källkoden till .NET Framework med

  103. 為了提供 debug 的需要,  .NET 的大部份原始碼可以經由Visual Studio 2008設定, 直接在 debug 時, 自動進 .NET 的原始碼內容。目前已經開放的原始碼有

  104. Oh yes. Following up from his earlier announcement , Scott Guthrie has just announced the broad availability

  105. De source code van een gedeelte van het .NET framework is beschikbaar. OP dit moment is de code beschikbaar

  106. Oh yes. Following up from his earlier announcement , Scott Guthrie has just announced the broad availability

  107. Διαθέσιμος είναι απο χθές ο κώδικας του .ΝΕΤ Framework σύμφωνα με ένα Blog Post του Scott Guthrie. Ο

  108. Miguel Saez says:

    Ha sido liberado el código fuente del framework .NET. Este es un anuncio muy esperado por toda la

  109. Creepy Gnome says:

    When I try to use the link posted to get the Hot Fix it doesn’t work, I usually get "Internet Explorer cannot display the webpage" IE is hiding the error code, so I do not know why it is saying this.  If I refresh the link for a while I will eventually get a "Windows Live ID is unavailable" error that looks like this:

    ———————————————–

    Windows Live ID is unavailable from this site for one of the following reasons:  

    -This site may be experiencing a problem.

    -The site may not be a member of Windows Live ID

    You can:

    -You can sign in or sign up at other Windows Live ID sites and services, or try again later at this site.

    ———————————————–

    I have a valid Live ID and have been to connect.microsoft.com many times before with out problems.  However, i cannot get to any part of the site right now either.  I get the same errors either an generic IE error, or the Windows Live ID error.

  110. stuart.carnie says:

    Shawn, is it possible to set up our own source server internally?  This would be useful for internal / external parties outside of development.

    Cheers,

    Stuart

  111. Na ja, fast. Open Source ist das noch nicht ganz, aber immer hin darf man jetzt als Entwickler auch mal einen Blick unter die Haube werfen und sich ein paar Sachen abschauen. Und vor allem Kommentare lesen, hehe :-). Alle Infos hier und hier.

  112. Annunciata la disponibilità di una parte dei sorgenti delle librerie del .NET Framework. Le librerie

  113. Ha sido liberado el código fuente del framework .NET. Este es un anuncio muy esperado por toda la

  114. sburke says:

    @ Creepy Gnome

    Can you access other sites like Live.com?  Not sure why accessing the Hotfix would be different than other parts of connect.  What happens if you log out and back into Windows Live?

    @ Stuart

    You mean for your own code inside your company?  Generally yes – meaning there isn’t a special hardcoding of our servers or anything.  But it’ll take some work to do – there have been a few questions on this, maybe shoot me an email with what you’d like to enable…

  115. James Kovacs says:

    As promised, Microsoft has made the source for the .NET Framework available for debugging purposes. You'll

  116. Creepy Gnome says:

    Yeah I can use my Live account all over the place. I can get to my MSDN account, I can get into my Live Messager, etc.

    As for log out and log in it doesn’t give me any of these options. I get an error message, and the choice to sign up thats it.  Its strange.

  117. Creepy Gnome says:

    Shawn it is working now.  I did something like what you said, there was a link (in small print) to access my account from the error page. I did that, and I logged in and then out and then in again. Then I when back to the link you give and it works great.

    Thanks for the help!

  118. sburke says:

    @Gnome – okay great!

  119. sburke says:

    @Gnome – okay great!

  120. Erics Blog says:

    Finally it is possible to debug the .NET Framework Source Code, and Shawn Burke has all the details on

  121. Διαθέσιμος είναι απο χθές ο κώδικας του .ΝΕΤ Framework σύμφωνα με ένα Blog Post του Scott Guthrie. Ο

  122. Τον Οκτώβριο είχε γίνει γνωστή η απόφαση της Microsoft να κάνει διαθέσιμο τον πηγαίο κώδικα του .NET

  123. .NET Framework Library Source Code now available

  124. … non ha prezzo !!! Per chi non ha voglia di leggersi l’esauriente post di Shawn Burke, questo è un

  125. .NET Frameworkのライブラリのソースコードが公開になったそうな!!!!

  126. Por fin lo que fue anunciado hace algunos meses por Scott Guthrie hoy es realidad: Podemos cargar los

  127. Configuring Visual Studio to Debug .NET Framework Source Code

  128. davidparslow says:

    Great!!! A couple of days ago I was trying to "google" any news about the release of the source code, because the last news I could find (one of your posts) said that it would be available a couple of weeks after the launch of VS 2008. Also, I believe that in previous posts it was mentioned that the source code release only covers framework 3.5 and not 2.0/3.0 and only applies to Visual Studio 2008 (not VS 2005) for debugging

  129. Tergiver says:

    When I click on the QFE link I get:

    Page Not Found

    The content that you requested cannot be found or you do not have permission to view it.

    Do you have to have more then "Visual Studio Registration Benefits Portal" Participation to get it?

  130. Bolik says:

    期待已久的.NETFramework终于在本周开源了,微软在MS-RL协议下终于公开了.NETFramework源代码,我们只可以自由查看,不允许直接进行修改。第一批开放的源代码包括:.NET基…

  131. tzh1080 says:

    搞的不错。但是我不能打开Visual Studio 2008 QFE,不知道是怎么回事。

    未找到网页

    无法找到您请求的内容或您无权查看该内容。

    如果您确信进入了错误的页面,请单击页面底部的“联系我们”链接,在电子邮件中报告此问题并提供此错误 ID: 03a50cc8-1829-4941-a6b1-fb248ec64f47

  132. [via ScottGu ] Available source code for now: NET Base Class Libraries (including System, System.CodeDom,

  133. crosspost from http://blogs.msdn.com/rextang [via ScottGu ] Available source code for now: NET Base Class

  134. [via ScottGu ] Available source code for now: NET Base Class Libraries (including System, System.CodeDom

  135. .NET Framework Library Source Code now available – ScottGu’s Blog 이전에 예고 된대로 라이브러리의 소스 코드가 공개되었습니다. 공개된

  136. .NET Framework Library Source Code now available – ScottGu's Blog 이전에 예고 된대로 라이브러리의 소스 코드가 공개되었습니다

  137. phphot says:

    Microsoft.NET Framework 全面开源

  138. Zqin says:

    配置Visual Studio 以调试.net framework的源代码

  139. yangyibang says:

    .NET Framework Library Source Code now available

  140. Tatis says:

    Tal y como se había anunciado, el código fuente de las librerías Base (System, System.CodeDom,

  141. gabriel.lozano-moran says:

    Same problem here, I get a "Page Not Found"  when I try to download the QFE.

  142. ImWhistler says:

    Unfortunately, Page Not Found 🙁

  143. Hatte gerade mit Mario über ein Debug Problem gesprochen, wie man .Net Framework Source Code debugged,

  144. Hatte gerade mit Mario über ein Debug Problem gesprochen, wie man .Net Framework Source Code debugged

  145. Blue Blip says:

    As announced earlier by Scott Gu , the source code for most of the namespaces in the .NET framework is

  146. Tal como o ScottGu anunciou em Outubro de 2007 , a Microsoft disponibilizou o código fonte da plataforma

  147. CallMeJake says:

    When I try to download the QFE I get:

    Page Not Found

    The content that you requested cannot be found or you do not have permission to view it.

    If you believe you have reached this page in error, click the Contact Us link at the bottom of the page to report the issue and include this ID in your e-mail: 41b12c86-7b45-4ed3-8918-6e9520c9c11b

    🙁

  148. Here are some pieces of information about stepping into base class libraries of .NET Framework while

  149. Is someone of my beloved readers lost an heart bit by seeing this splash image? For me, it all began

  150. Here are some pieces of information about stepping into base class libraries of .NET Framework while

  151. You’ve been kicked (a good thing) – Trackback from DotNetKicks.com

  152. ttoni says:

    Same problem as "CallMeJake", but with different ID of course:

    b0199964-af08-414d-84c2-a7e9630ffef0

  153. yangwuhan says:

    NET Framework Library Source Code

  154. OPC Diary says:

    Shawn Burke’s Blog : Configuring Visual …

  155. Source code til .net framework frigivet

  156. sburke says:

    RE: QFE Downloads

    The download page was down for a while, but it’s back up now at the link at the top of the post.  Sorry for the inconvenience.

  157. So I just set up debugging of the .NET framework source code as per the instructions on Shawn Burke’s

  158. So I just set up debugging of the .NET framework source code as per the instructions on Shawn Burke’s

  159. El Bruno says:

    Buenas este tipo de noticia se reproduce como un politono de los malos. Anoche a altas horas de la madrugada,…

  160. So I just set up debugging of the .NET framework source code as per the instructions on Shawn Burke's

  161. ImWhistler says:

    Thanks a lot 🙂

  162. Mike Almond says:

    I found that you have to restart VS 2008 after the initial symbol server configuration configuration (at the Debugging Into Framework Source title in the article).  Until I did so, the "Load Symbols" did not show up on the context menu.

  163. Debug del codice .Net con VS2008

  164. jemiller says:

    Why do you have to manually load the symbols for each debugging session? It seems like a hassle. It seems like they should be remembered for as long as the given project is open.

  165. 转贴http://news.csdn.net/n/20080117/112839.html

    期待已久的.NETFramework终于在本周开源了,微软在MS-RL协议下终于公开了.NETFram…

  166. sburke says:

    @jemiller

    I know, that’s just the way the debugger works unfortunately.  Please see the "ADVANCED USERS" section, it may be a better method for you.

  167. 罗布林克 says:

    期待已久的.NET Framework终于在本周开源了,微软在MS-RL协议下终于公开了.NET Framework源代码,我们只可以自由查看,不允许直接进行修改。

  168. KidYang says:

    期待已久的.NETFramework终于在本周开源了,微软在MS-RL协议下终于公开了.NETFramework源代码,我们只可以自由查看,不允许直接进行修改。

    第一批开放的源代码包括: …

  169. 张彤 says:

    Configuring Visual Studio to Debug .NET Framework Source Code

  170. Debuggare i sorgenti del framework da VS2008

  171. Maor David says:

    It's here and you can give it a try now! To step through .NET Framework Source code, here's what

  172. DevCorner says:

    Always wanted to know, how some functionality implemented in .Net framework? Want to debug into framework

  173. VS 2008 e .NET Framework Source Code

  174. Microsoft.NET Framework 全面开源

  175. bindsang says:

    今天终于有时间下载VS2008team suite版了 里面的js脚本编辑器,号称是全面支持智能感知和函数描述,参数说明,按帮助给的方式试了一下,觉得还不错,连ajax写的希奇古怪的js脚本都可以正常提示出来 顺便搭配使用一下DOTNET Framework的开源代码

  176. One of the things we have been working on recently is publishing sources of VisualBasic runtime library.

  177. One of the things we have been working on recently was publishing sources of VisualBasic runtime library

  178. yuantao says:

    期待已久的.NETFramework终于在本周开源了,微软在MS-RL协议下终于公开了.NETFramework源代码,我们只可以自由查看,不允许直接进行修改。

    第一批开放的源代码包括: …

  179. figo says:

    Microsoft.NET Framework 全面开源

  180. User-Unhandled Exception missing from Visual Studio

  181. jackch88 says:

    微软.NET Framework总经理Scott Guthrie上周宣布微软正式释出.NET Framework链接库。 Scott Guthrie在去年10月就发表了此一计划,当时指出开发人员透过这些开放浏览的源码可更了解.NET架构程序如何被应用,以调校所开发的应用程序以及进行.NET架构除错。

  182. Welcome to the XXXIX issue of Community Convergence. The big news this week is that Microsoft has begun

  183. Welcome to the XXXIX issue of Community Convergence. The big news this week is that Microsoft has begun

  184. karthik_try@hotmail.com says:

    Hi Shawn,

    Could you please explain how to create our own Internet symbol server like the one microsoft has ?

  185. karthik_try@hotmail.com says:

    Hi Shawn,

    Could you please explain how to create our own Internet symbol server like the one microsoft has ?

    Thanks,

    Arun

  186. karthik_try@hotmail.com says:

    Hi Shawn,

    Could you please explain how to create our own Internet symbol server like the one microsoft has ?

    Thanks,

    Karthik

  187. Tim Long says:

    I'm not implying that the Framework needs to be debugged – but now, if you need to understand what

  188. NicolBlog says:

    Shawn have done a great job describing how to configure the development environment to go into .NET source

  189. Shawn have done a great job describing how to configure the development environment to go into .NET source

  190. 如果想要知道 .NET Framework 的程式是如何寫的,現在使用 VS 2008 就可以直接做這件事。 詳細設定的方式: http://blogs.msdn.com/sburke/archive/2008/01/16/configuring-visual-studio-to-debug-net-framework-source-code.aspx

  191. 如果想要知道 .NET Framework 的程式是如何寫的,現在使用 VS 2008 就可以直接做這件事。 詳細設定的方式: http://blogs.msdn.com/sburke/archive

  192. vedala says:

    @Arun, @Karthik_try

    Buy this book: Advanced Windows Debugging by Mario and Daniel. Whole chapter is dedicated to setting up symbol server with IIS.

  193. In my continued resolution to make PowerShell my full time command line interface, I’ve been porting

  194. karthik_try@hotmail.com says:

    Hi vedala,

    Thanks for your information.

    Karthik

  195. jey-j says:

    .Net Frameworkライブラリのソースコード公開

  196. TerryLee says:

    概述1.FiveAjaxControlToolkitTabThemescreatedfromDynamicDrive.com

  197. Other people have told me they're now successfully debugging into .NET Framework source code although

  198. Jacky_Xu says:

    本期共有9篇文章

    1.FiveAjaxControlToolkitTabThemescreatedfromDynamicDrive.com

  199. sharplife says:

    部分.netframeworksourcecode已开源,设置vs2008可进行framework的源码级调试,http://www.infoq.com/news/2008/01/DotNet-

  200. SocialITy says:

    Silverlight nie chce mnie opuścić – to naprawdę gorący temat. W październiku pisałem o otwarciu kodu

  201. Microsoft.NET Framework 全面开源

  202. At last my prayers have been answered! Microsoft has recently released the source code for .NET Framework

  203. At last my prayers have been answered! Microsoft has recently released the source code for .NET Framework

  204. This past week Microsoft released a portion of the .NET Framework library to enable debugging support

  205. Eric Yih says:

    微软在MS-RL协议下终于有“条件”的公开了.NetFramework源代码,具体来说,现在可以查看和调试下面的.NetFramework的源代码:.NET基类库(包括System,Sys…

  206. magicmat says:

    This doesn’t appear to work. The linked version of .Net 3.5 is 2.0.50727.1434 (rather than .1433) and, thus, the symbol server is useless until it gets updated. I’m running Vista SP1 RC, if that makes a difference.

    PS: PingBacks are the most useless form of user-consented spam ever, and I’ll never, ever understand why Microsoft keeps coding them in to their blogs. Do the 300 entries rephrasing the original post really make the community more vibrant, or information easier to find? No, they do the exact opposite.

  207. ytchua says:

    Hi, FYI, I’m currently running on Visual Studio Team System 2008 Team Suite Beta 2. I was not able to install the hotfix with below message:

    None of the products that are addressed by this software update are installed on this computer. Click Cancel to exit setup.

    Any idea how could I get this to be installed?

    Thanks.

    ytchua.

  208. ytchua says:

    Dear Shawn Burke,

    The hotfix that I mentioned is Visual Studio 2008 QFE KB944899.

    Yet, I’m not able to access to http://support.microsoft.com/kb/944899.

    ytchua.

  209. sburke says:

    @magicmat

    Correct, the 1434 (Vista SP1) symbols aren’t currently up there.  We’re working on getting them deployed.

  210. sburke says:

    @ytchua

    The hotfix can only be installed on the final RTM version of VS2008.  Hope that helps!

  211. 猿頁 says:

    注意:本エントリは、後で自分でやろうと思って収集した情報をまとめたものです。実際に私はまだ作業を行…

  212. Przy pisaniu swojej wersji Wiki-pajączka uwziąłem się, aby znów wrócić do tematu nazwijmy to

  213. Przy pisaniu swojej wersji Wiki-pajączka uwziąłem się, aby znów wrócić do tematu nazwijmy to

  214. 猿頁 says:

    前エントリで.NET Frameworkライブラリソースの参照のしかたがわかりました。 せっかくで…

  215. Test2007 says:

    I got following info when clicking on the Symbol Load Infomation:

    D:WINDOWSassemblyGAC_MSILSystem.Windows.Forms2.0.0.0__b77a5c561934e089System.Windows.Forms.pdb: Cannot find or open the PDB file.

    d:Program FilesMicrosoft Visual Studio 9.0Common7IDESystem.Windows.Forms.pdb: Cannot find or open the PDB file.

    D:WINDOWSsymbolsdllSystem.Windows.Forms.pdb: Cannot find or open the PDB file.

    D:WINDOWSdllSystem.Windows.Forms.pdb: Cannot find or open the PDB file.

    D:WINDOWSSystem.Windows.Forms.pdb: Cannot find or open the PDB file.

    I have no idea on this, please help me take a look. Thanks in advance!

  216. 张子阳. says:

    本文首先讨论了C#中的两种类型–值类型和引用类型,随后简要回顾了 装箱/拆箱 操作。接着,详细讨论了C#中的对象判等。最后,我们讨论了浅度复制 和深度复制,并比较了它们之间不同。

  217. Jon Galloway says:

    I’ve had a policy against posting on big news that’s likely to be common knowledge in the Microsoft development

  218. sasah says:

    Source code automatically loaded completely.

  219. Microsoft has really helped out the development community by making the .NET Reference Source Code available

  220. It was announced with the release of Visual Studio 2008, now it's here – follow this thorough step

  221. MihaM says:

    Great news. Microsoft finally released a part of .NET Framework Source Code for debugging purposes. A

  222. Zunanji viri says:

    Great news. Microsoft finally released a part of .NET Framework Source Code for debugging purposes. A

  223. Zunanji viri says:

    Another piece of good news that . NET Framework Library source code is now available in Visual Studio

  224. Coding4Fun says:

    On 1/16/08, Microsoft announced the ability to download some of the .NET Framework source code for debugging

  225. The Thinker says:

    Over the weekend I had a play with the new .NET framework source code release which now allows you to debug into framework classes as part of your standard debugging. The source gives a good insight i …

  226. On 1/16/08, Microsoft announced the ability to download some of the .NET Framework source code for debugging

  227. Shawn Burke’s blog has full instructions on how to make the .NET reference source code available in your

  228. Shawn Burke's blog has full instructions on how to make the .NET reference source code available

  229. Hi, Microsoft has released .Net reference source code, which enable you to debug straight into .net framework

  230. 曹振华 says:

    ASP.NETMVC框架路线图更新

    【原文地址】ASP.NETMVCFrameworkRoad-MapUpdate

    【原文发表日期】Tuesday,February12,200…

  231. thanks a lot for this feature.

    I lost 3 days on a binding problem which was resolved in five minutes by this way

  232. wzwind says:

    NET Framework Library Source Code now available

  233. As I’ve been preparing more things to talk about I realized that it would be beneficial to have a list

  234. As I’ve been preparing more things to talk about I realized that it would be beneficial to have a list

  235. 首先要感谢微软公司在VS2008中引入了部分开源的协议使大家不必再通过Reflector等工具进行反编译,着实让大家感受到了不少便利。不过微软的VS2008中的开源方式存在若干不足,最重要的不足之处…

  236. As Developer Division starts to ship patches for the Visual Studio 2008 , some users are being prompted

  237. As Developer Division starts to ship patches for the Visual Studio 2008 , some users are being prompted

  238. Mainz says:

    .net Framework 开源了,不过没有现成的代码包下载,只有debug的时候每次能获得一个文件,还好热心人写了个软件全部debug所有方法从而得到源代码.1. 如何下载源代码 2. 如何在Visual Studio 2008中进行配置

  239. I first blogged on this back in January but based on all my meetings in Feb, very few ISVs seem to know

  240. gOODiDEA says:

    Other: BuildingACity-PartII

    TheFiveBrowserShortcutsEveryoneShouldKnow

    Flex快速上手:入门指…

  241. barrkel says:

    One major problem with this is that VS still round-trips to the reference source server every time code is stepped through. This makes stepping through a bunch of code quite painful!

  242. margiex says:

    1..netframeworksource已经可以在vs2008中使用

    ref:

  243. bobolink_lu says:

    本文之初的目的是讲述设计模式中的 Prototype(原型)模式,但是如果想较清楚地弄明白这个模式,需要了解对象克隆(Object Clone),Clone其实也就是对象复制。复制又分为了浅度复制(Shallow Copy)和深度复制(Deep Copy),浅度复制 和 深度复制又是以 如何复制引用类型成员来划分的。由此又引出了 引用类型和 值类型,以及相关的对象判等、装箱、拆箱等基础知识。

  244. Erics Blog says:

    I run into an issue with grids not showing newly added objects in one of my projects a couple of days

  245. Debug del codice .Net con VS2008

  246. There are many new features they put inside Visual Studio 2008. Basically VS 2008 uses .NET Framework 3.5. Application developed in this version can be targeted to any of previous versions of .NET Fra …

  247. wsnell says:

    When will we have the same ability to see and debug down in the .NET Compact Framework code?

  248. 鱼跃于渊 says:

    引言

    本文之初的目的是讲述设计模式中的Prototype(原型)模式,但是如果想较清楚地弄明白这个模式,需要了解对象克隆(ObjectClone),Clone其实也就是对象复制。复制又分为了浅度…

  249. Code source Framework .NET disponible !

  250. 不慕 says:

    配置VisualStudio以调试.netframework的源代码

    看到.net框架代码发布了,兴奋了一下,把在VisualStudio2008上配置的内容翻译了一下,只翻译了原文的基…

  251. aa.loedeman says:

    Hi Shawn,

    Nice feature! Microsoft going some kind of open-source 😉 – I could not think of it, some years ago.

    I have one question about this feature: does it download source code over port 80 or is another port needed to be configured for this feature. The reason I ask, is that my current client works with a very heavily secured network, only allowing port 80 to be used for outside communication (and other ports whenever there is a very good reason for it).

    I would be glad if you could be of any help! Thanks a lot in advance!

    Regards, Bert Loedeman

  252. Earlier I posted a link to the announcement on ScottGu’s blog about the framework source availiability

  253. I needed a "deep debug" (including the managed code) and found a great step by step guide by

  254. I am not sure how many people are familiar with the .NET Reference Source project, but if you do a lot

  255. The Microsoft-supported .NET Reference Source project enables developers to dig into the .NET Source

  256. Jerome Laban says:

    This post is also available in english here . J’ai récemment cherché un moyen de passer automatiquement

  257. Code source Framework .NET disponible !

  258. rkpatrick says:

    One additional possibility as to the inability to load symbols (found this after all my version stuff seemed OK, but was still getting error messages): your network has a proxy server that requires login before web browsing.

    I didn’t notice this until actually looking at the PDB to see why the versions weren’t matching, and instead of PDB symbols, I had a web page from Symantec’s web proxy with a user/password entry form.

    I wouldn’t say this is a MS bug or anything, but it’s just a weird error that some folks may get when they are in a corporate network.

  259. 私たちのチームは Visual Basic ランタイム ライブラリのソースの公開に向けた作業を続けていましたが、ついにその公開が実現し、 Microsoft.VisualBasic.dll を皆 さん

  260. Stepping into .NET source code

  261. Marius Bancila says:

    I followed your steps and it doesn’t work. When I try to step into a function (for instance String.Substring) nothing happens. When I double click on a method from the call stack I get this dialog saying "There is no source code available for the current location." Any tips please?

  262. smwikipedia says:

    部分.netframeworksourcecode已开源,设置vs2008可进行framework的源码级调试,

    http://www.infoq.com/news/2008/01/DotNe

  263. Tip of the Day #2 – (Debugging into the .NET source code)

  264. Debugging Into .NET Source Code

  265. Debugging Into .NET Source Code

  266. WPF DotNet says:

    Since the dotnet source code are avaible now, including WPF, it’s a good chance for us to read the code

  267. Didrex without a prescription. Order didrex. Didrex no rx. Buy didrex. Didrex buy didrex didrex diet pills. Didrex script online.

  268. 冷血 says:

    引言

    本文之初的目的是讲述设计模式中的Prototype(原型)模式,但是如果想较清楚地弄明白这个模式,需要了解对象克隆(ObjectClone),Clone其实也就是对象复制。复制又分为了浅度…

  269. 王孟军! says:

    无论你是菜鸟或是大师,调试是每个开发者,都必须学会的技巧,在我用vs2003的时候,我没办法去调试.net的源代码文件,微软迟迟不肯开源,没办法,有些原理,有些机制,只能翻翻MSDN,或者瞎猜,给我们带来诸多的不便…

  270. As the world knows, Visual Studio 2008 SP1 is out so start your download engines. I’ve installed it on

  271. Come configurare Visual Studio per il debug del codice sorgente del .NET Framework.

  272. olag_2@hotmail.com says:

    Step in framework-code worked before sp1. now it appears always the message "There is no source code available for the current location."

    Loading the Symbols work, but i cant step in…

  273. In mid January the first release of the .NET Framework 3.5 reference sources occurred. In mid February

  274. 在8月28号的时候就看到 源代码参考团队博客上 有 消息说.NET 3.5 SP1 Source发布了, [ From 源代码参考团队博客上 ]我们刚刚公布了下列组件所提到的源代码中心( rscc )服务器

  275. Debugging into .net source code is pretty easy now

  276. Debug del codice .Net con VS2008

  277. daveblack says:

    I have a bug with VS2008 SP1 that I discovered yesterday when trying to debug an application with 7 projects.  It has to do with the new Debugging feature of "Enable .NET Framework source stepping" under Tools | Optons.

    VS2008 SP1 will crash if I have this solution open, check ‘Enable .NET Framework source stepping’, and then click OK.  The result of the bug generates:

    Event Type: Error

    Event Source: .NET Runtime

    Event Category: None

    Event ID: 1023

    Date: 9/9/2008

    Time: 4:49:20 PM

    User: N/A

    Computer: VIRTUAL-DEV

    Description:

    .NET Runtime version 2.0.50727.3053 – Fatal Execution Engine Error (7A2E0F92) (0)

    I’m going to open a bug on MS Connect once I try to narrow the problem down.  Here are some things I’ve noticed so far:

    1. It doesn’t occur with some other projects I’ve tried so far.

    2. I believe it has to do with using Symbol Servers

    3. I have only http://referencesource.microsoft.com/symbols listed and have deleted all of the cached symbols that the SymbolServer previously used.

    4. I think it has to do with a particular project type – but rooted in the .NET references it requires and uses.

    More to come as I narrow it down and will post a link to the MS Connect Bug ID…

  278. daveblack says:

    I’ve found the way to reliably repro the issue and have opened a bug on MS Connect:

    https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=367121

  279. I just debugged through the .NET Framework assembly source code like the way I used to do MFC source

  280. Ganesh says:

    Hi…

    This is Ganesh and i have a doubt to be clarified. I am using Visual Studio 2008 and i want to write a Std VB6 application, without .Net support. So this VB6 exe should work in all the system without .Net framework. Can i achieve this. Please help me

    Yours Loving

    Ganesh

  281. Pessoal, Conforme demonstrado no nosso webcast, o link para configurar o Visual Studio 2008 é: http:

  282. Neal says:

    I’m having huge trouble getting this to work in VS 2008 SP1 (Vista x64 Ultimte). After I load the symblols and couble clicj on an item in the call stack a message box pops up saying "There is not source code for the current location"

    The Symbol Load Information shows this

    C:WindowsassemblyGAC_MSILSystem.Windows.Forms2.0.0.0__b77a5c561934e089System.Windows.Forms.pdb: Cannot find or open the PDB file.

    C:Windowssystem32System.Windows.Forms.pdb: Cannot find or open the PDB file.

    E:DotNetSymbolCacheMicrosoftPublicSymbolsSystem.Windows.Forms.pdb8BA08E6865274799AD03B4A86FBAEF7C1System.Windows.Forms.pdb: Symbols loaded.

    Anyone known why it’s not working?

  283. 期待已久的.NETFramework终于在本周开源了,微软在MS-RL协议下终于公开了.NETFramework源代码,我们只可以自由查看,不允许直接进行修改。 第一批开放的源代码包括:

  284. Guy kolbis says:

    Earlier this year, Microsoft announced that it would make the .NET Framework source code available to

  285. 陈希章 says:

    之前安装VS2008的SP1之后有些莫名其妙的问题,例如智能感知全部变成了英文的,还有源代码调试也有问题。我为此专门找了微软的技术支持。 今天得到回复,微软新近推出了一个更新补丁,安装之后就可以解决了

  286. One application had a memory issue, it just consume too much resources. The application performed well,

  287. On Tuesday I got a call up from a developer that was dealing with an unusual ASP.NET problem and was

  288. While I have been working with Visual Studio .NET since the first version (2002), some years ago I started

  289. ASP.NET Error Handling Resources – C#

  290. Some tidbits of VS2008 goodness.

  291. I found this blog post from Shawn Burke to be very useful. Comes in handy if you have to step through

  292. Share Mind says:

    .NET Framework Source Code In VS

  293. TableHeaderScope.Column and HTML standards compliance

  294. small_mountain says:

    No workie.  Looks like same behavior Neal complained about.  When I right-click in the call stack, first of all, it doesn’t just say "Load Symbols" by itself.  What I have is a "Load Symbols From" submenu with choices Symbol Path and Microsoft Symbol Servers.  Symbol Path doesn’t work at all, so I use Microsoft Symbol Servers.  The symbols load, and the line in the call stack turns black, but there is no line number, just an offset (+ 0x59 bytes).  Right-click -> Go To Source Code is grayed.  I looked for a definition of _NT_SYMBOL_PATH.  I deleted my old symbol cache plus changed the path to something new.  No go, joe.

    Eric

  295. Last night I presented for the first time at the Google Open Source Jam at our offices in London. The

  296. RonitPatel says:

    Is it possible to debug the code in PresentationFramework.dll. I am trying to debug one of the method in VirtualizingStackPanel. This control is located in the System.Windows.Controls namespace.

  297. Naresh says:

    You really helped me knowing the debugging… Thanks :)….

  298. Vampal says:

    how can prevent debug into disassembly?

  299. Satpal says:

    Those of us programming on the .NET framework have come to realize the power and increased productivity that comes with it, says Dr. Venkat Submramaniam. Like any development, however, there are things that one should pay attention to while programming on .NET. Are there things in .NET that, if we do not pay attention to, may result in more trouble than it is worth? Learn all there is to know in a FREE video workshop conducted by Dr. Venkat Subramaniam. In the workshop recorded at Saltmarch Media’s Great Indian Developer Summit, Venkat presents Gotchas that a developer needs to know to be productive in the .NET framework. The issues addressed include framework, language, language interoperability, COM interoperability. Most Gotchas are language independent while a few are C# or VB.NET specific. To view the workshop, visit devmarch.com/video.html

  300. What about System.web (Framework 4) says:

    With Visual Studio 2010 I can step in some assemblies but I cannot step into system.web (Framework 4). Has someone been able to step in this assembly?

    Thank you for the help.

  301. Does not work for me in VS 2008. My mscorlib is 2.0.50727.5456, which of course is different from the version it was "supposed" to be back in 2008, 2.0.50727.1433. I tried downloading the symbols from scratch with referencesource.microsoft.com/symbols as the only URL in the "Symbol file locations" list, but it didn't help. Symbol Status for the DLL I want to debug is "Cannot find or open the PDB file". So what can I do?