<?xml version="1.0" encoding="iso-8859-9"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: .NET Framework source code is now open to the public</title>
	<atom:link href="http://sunali.com/2008/01/18/net-framework-source-code-is-now-open-to-the-public/feed/" rel="self" type="application/rss+xml" />
	<link>http://sunali.com/2008/01/18/net-framework-source-code-is-now-open-to-the-public/</link>
	<description>Coşkun SUNALI</description>
	<pubDate>Fri, 29 Aug 2008 19:24:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Kerem Kusmezer</title>
		<link>http://sunali.com/2008/01/18/net-framework-source-code-is-now-open-to-the-public/#comment-1569</link>
		<dc:creator>Kerem Kusmezer</dc:creator>
		<pubDate>Wed, 06 Feb 2008 23:55:54 +0000</pubDate>
		<guid isPermaLink="false">http://sunali.com/2008/01/18/net-framework-source-code-is-now-open-to-the-public/#comment-1569</guid>
		<description>Just Grab Your Copy From:
http://www.codeplex.com/NetMassDownloader

.NET Mass Downloader 

Welcome to the .NET Mass Downloader project. While it&#8217;s great that Microsoft has released the .NET Reference Source Code, you can only get it one file at a time while you&#8217;re debugging. If you&#8217;d like to batch download it for reading or to populate the cache, you&#8217;d have to write a program that instantiated and called each method in the Framework Class Library. Fortunately, .NET Mass Downloader comes to the rescue!

Using .NET Mass Downloader 
Open a command or PowerShell prompt and navigate to where you extracted the current release. The tool itself is NetMassDownloader.exe and when run without parameters shows the following help screen:
.Net Mass Downloader 1.0.0.0 - (c) 2008 by Kerem Kusmezer, John Robbins
 
Batch download the Microsoft .NET Reference Source code.
 
Usage: NetMassDownloader [-file ]
                         [-directory &#60;directory]
                         [-output ]
                         [-vsver ]
                         [-force] [-nologo] [-verbose] [-?]
 
    -file      - Download an individual file's PDB and source code. You can
                 specify multiple file parameters. (Short -f).
    -directory - Download all the found PDB and source code for all files in
                 the specified directory. You can specify multiple
                 directory parameters (Short -d).
    -output    - The output directory for PDB and source files. The default
                 directory is the cache directory set in Visual Studio 2008.
                 By using the cache directory, you'll have the PDB and source
                 files available to Visual Studio 2008. However, to use the
                 .NET Reference Source Code with VS 2005, use the -output
                 switch and in the Options dialog, Debugging, Symbols property
                 page, add the specified output directory to the "Symbol file
                 (.pdb) locations." Also, add the directory to the Solution
                 Properties, Common Properties, Debug Source Files, Directories
                 containing source code location. The Visual Studio 2005
                 debugger will automatically load the source code. (Short -o)
    -vsver     - The Visual Studio version number to use for finding the cache
                 directory. The default is Visual Studio 2008,
                 but if you want to use the cache directory for Visual Studio
                 2005, you would pass '-vsver 8.0' (without quotes) (Short -vs)
    -force     - If specified, forces the downloading the PDB files into the
                 symbol server. When downloading to a symbol server if the PDB
                 exists, it's not downloaded. Using the -output switch will
                 always download and process the PDB. (Short -fo)
    -nologo    - Don't show the logo information. (Short -n)
    -verbose   - Do verbose output. May be worth turning on as the downloading
                 source code can take a long time. (Short -v)
    -?         - This help message.
The only required arguments are &#8211;file or &#8211;directory, both of which can be specified as many times as you&#8217;d like. When you specify a directory, only the .DLL and .EXE files from that directory will be processed. If you wanted to download all the source code from binaries in the .NET 2.0 32-bit and 64-bit directories, the command line you&#8217;d pass is: -d C:\Windows\Microsoft.NET\Framework\v2.0.50727 &#8211;d C:\Windows\Microsoft.NET\Framework64\v2.0.50727.

The main purpose of Net Mass Downloader is to populate the source code download cache for debugging, the default download location is the cache you specified to Visual Studio 2008. The &#8211;vsver switch to account for future Visual Studio versions so Mass Downloader could work with future CTPs and versions. 

While it&#8217;s great to see the .NET Reference Source Code in Visual Studio 2008, there are a lot of developers out there who can&#8217;t upgrade yet, but would love to be able to debug into the .NET Reference Source Code. If you specify the -output parameter, the PDB and .NET Reference Source Code will be written to the specified directory. In Visual Studio 2005, place that directory in the Options dialog, Debugging, Symbols property page. In the &#8220;Symbol file (.pdb) locations&#8221; list box as the first item. Also in the Options dialog, Debugging, General property page, uncheck "Require source files to exactly match the original version." Finally, in each Visual Studio 2005 project go into the solution property pages, Common Properties, Debugging Source Files, and in the "Directories containing source code" add the output directory to the top of the list. That's enough for Visual Studio 2005 to debug into the .NET Reference Source Code.

When you first run Net Mass Downloader, you will be prompted with the current EULA for accessing the source code. If you don&#8217;t agree with the Microsoft EULA, clicking the Decline button will not download the source code.

The code download includes a detailed documentation about the steps required to use it with VS2005 

If none of the files can be downloaded please download and install the RTM Version of the .NET Framework 3.5

According to the Shawn's blog the following DLLs are enabled for the .NET Reference Source Code:
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 

Net Mass Downloader will download any additional DLLs Microsoft configures to use with .NET Reference Source Code in the future, provided Microsoft doesn't change the download engine. 

The original .NET Reference Source Code announcement can be found here:
Shawns Announcement


Downloading .Net Framework 3.0 And 3.5 Libraries 

The framework v3.5 and v3.0 assemblies are located under c:\program files\reference assemblies\microsoft\framework\v3.0 and c:\program files\reference assemblies\microsoft\framework\v3.5

so to download them issue the following command pointing netmassdownloader to target folders:

netmassdownloader -d "C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5" 
-d "C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0" 

Check the discussion How to download v3.0 and v3.5 Source Codes about this.


Acknowledgements 
Thanks to the Developer Division at Microsoft. First they released the .NET Reference Source Code, and second for allowing a couple of developers to have some fun and provide a utility for the community. Thank you for using .NET Mass Downloader. We just ask that you log any bugs and features into the project Issue Tracker.


Contact Information 
You can reach us via the discussions or you can directly mail Kerem at keremskusmezer@gmail.com


Development Details 
If you have questions about particular pieces of the code, Kerem Kusmezer did the following parts: the PE (Portable Executable) Parser, the PDB Parser, the Webclient Class. and the SrcSrv class. John Robbins did the console driver, testing, and served as Kerem's code monkey.

Kerem Kusmezer and John Robbins</description>
		<content:encoded><![CDATA[<p>Just Grab Your Copy From:<br />
<a href="http://www.codeplex.com/NetMassDownloader" rel="nofollow">http://www.codeplex.com/NetMassDownloader</a></p>
<p>.NET Mass Downloader </p>
<p>Welcome to the .NET Mass Downloader project. While it&#8217;s great that Microsoft has released the .NET Reference Source Code, you can only get it one file at a time while you&#8217;re debugging. If you&#8217;d like to batch download it for reading or to populate the cache, you&#8217;d have to write a program that instantiated and called each method in the Framework Class Library. Fortunately, .NET Mass Downloader comes to the rescue!</p>
<p>Using .NET Mass Downloader<br />
Open a command or PowerShell prompt and navigate to where you extracted the current release. The tool itself is NetMassDownloader.exe and when run without parameters shows the following help screen:<br />
.Net Mass Downloader 1.0.0.0 - (c) 2008 by Kerem Kusmezer, John Robbins</p>
<p>Batch download the Microsoft .NET Reference Source code.</p>
<p>Usage: NetMassDownloader [-file ]<br />
                         [-directory &lt;directory]<br />
                         [-output ]<br />
                         [-vsver ]<br />
                         [-force] [-nologo] [-verbose] [-?]</p>
<p>    -file      - Download an individual file&#8217;s PDB and source code. You can<br />
                 specify multiple file parameters. (Short -f).<br />
    -directory - Download all the found PDB and source code for all files in<br />
                 the specified directory. You can specify multiple<br />
                 directory parameters (Short -d).<br />
    -output    - The output directory for PDB and source files. The default<br />
                 directory is the cache directory set in Visual Studio 2008.<br />
                 By using the cache directory, you&#8217;ll have the PDB and source<br />
                 files available to Visual Studio 2008. However, to use the<br />
                 .NET Reference Source Code with VS 2005, use the -output<br />
                 switch and in the Options dialog, Debugging, Symbols property<br />
                 page, add the specified output directory to the &#8220;Symbol file<br />
                 (.pdb) locations.&#8221; Also, add the directory to the Solution<br />
                 Properties, Common Properties, Debug Source Files, Directories<br />
                 containing source code location. The Visual Studio 2005<br />
                 debugger will automatically load the source code. (Short -o)<br />
    -vsver     - The Visual Studio version number to use for finding the cache<br />
                 directory. The default is Visual Studio 2008,<br />
                 but if you want to use the cache directory for Visual Studio<br />
                 2005, you would pass &#8216;-vsver 8.0&#8242; (without quotes) (Short -vs)<br />
    -force     - If specified, forces the downloading the PDB files into the<br />
                 symbol server. When downloading to a symbol server if the PDB<br />
                 exists, it&#8217;s not downloaded. Using the -output switch will<br />
                 always download and process the PDB. (Short -fo)<br />
    -nologo    - Don&#8217;t show the logo information. (Short -n)<br />
    -verbose   - Do verbose output. May be worth turning on as the downloading<br />
                 source code can take a long time. (Short -v)<br />
    -?         - This help message.<br />
The only required arguments are &#8211;file or &#8211;directory, both of which can be specified as many times as you&#8217;d like. When you specify a directory, only the .DLL and .EXE files from that directory will be processed. If you wanted to download all the source code from binaries in the .NET 2.0 32-bit and 64-bit directories, the command line you&#8217;d pass is: -d C:\Windows\Microsoft.NET\Framework\v2.0.50727 &#8211;d C:\Windows\Microsoft.NET\Framework64\v2.0.50727.</p>
<p>The main purpose of Net Mass Downloader is to populate the source code download cache for debugging, the default download location is the cache you specified to Visual Studio 2008. The &#8211;vsver switch to account for future Visual Studio versions so Mass Downloader could work with future CTPs and versions. </p>
<p>While it&#8217;s great to see the .NET Reference Source Code in Visual Studio 2008, there are a lot of developers out there who can&#8217;t upgrade yet, but would love to be able to debug into the .NET Reference Source Code. If you specify the -output parameter, the PDB and .NET Reference Source Code will be written to the specified directory. In Visual Studio 2005, place that directory in the Options dialog, Debugging, Symbols property page. In the &#8220;Symbol file (.pdb) locations&#8221; list box as the first item. Also in the Options dialog, Debugging, General property page, uncheck &#8220;Require source files to exactly match the original version.&#8221; Finally, in each Visual Studio 2005 project go into the solution property pages, Common Properties, Debugging Source Files, and in the &#8220;Directories containing source code&#8221; add the output directory to the top of the list. That&#8217;s enough for Visual Studio 2005 to debug into the .NET Reference Source Code.</p>
<p>When you first run Net Mass Downloader, you will be prompted with the current EULA for accessing the source code. If you don&#8217;t agree with the Microsoft EULA, clicking the Decline button will not download the source code.</p>
<p>The code download includes a detailed documentation about the steps required to use it with VS2005 </p>
<p>If none of the files can be downloaded please download and install the RTM Version of the .NET Framework 3.5</p>
<p>According to the Shawn&#8217;s blog the following DLLs are enabled for the .NET Reference Source Code:<br />
Mscorlib.DLL<br />
System.DLL<br />
System.Data.DLL<br />
System.Drawing.DLL<br />
System.Web.DLL<br />
System.Web.Extensions.DLL<br />
System.Windows.Forms.DLL<br />
System.XML.DLL<br />
WPF (UIAutomation.DLL, System.Windows.DLL, System.Printing.DLL, System.Speech.DLL, WindowsBase.DLL, WindowsFormsIntegration.DLL, Presentation.DLL, some others)<br />
Microsoft.VisualBasic.DLL </p>
<p>Net Mass Downloader will download any additional DLLs Microsoft configures to use with .NET Reference Source Code in the future, provided Microsoft doesn&#8217;t change the download engine. </p>
<p>The original .NET Reference Source Code announcement can be found here:<br />
Shawns Announcement</p>
<p>Downloading .Net Framework 3.0 And 3.5 Libraries </p>
<p>The framework v3.5 and v3.0 assemblies are located under c:\program files\reference assemblies\microsoft\framework\v3.0 and c:\program files\reference assemblies\microsoft\framework\v3.5</p>
<p>so to download them issue the following command pointing netmassdownloader to target folders:</p>
<p>netmassdownloader -d &#8220;C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5&#8243;<br />
-d &#8220;C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0&#8243; </p>
<p>Check the discussion How to download v3.0 and v3.5 Source Codes about this.</p>
<p>Acknowledgements<br />
Thanks to the Developer Division at Microsoft. First they released the .NET Reference Source Code, and second for allowing a couple of developers to have some fun and provide a utility for the community. Thank you for using .NET Mass Downloader. We just ask that you log any bugs and features into the project Issue Tracker.</p>
<p>Contact Information<br />
You can reach us via the discussions or you can directly mail Kerem at <a href="mailto:keremskusmezer@gmail.com">keremskusmezer@gmail.com</a></p>
<p>Development Details<br />
If you have questions about particular pieces of the code, Kerem Kusmezer did the following parts: the PE (Portable Executable) Parser, the PDB Parser, the Webclient Class. and the SrcSrv class. John Robbins did the console driver, testing, and served as Kerem&#8217;s code monkey.</p>
<p>Kerem Kusmezer and John Robbins</p>
]]></content:encoded>
	</item>
</channel>
</rss>
