• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Access to Source code for PowerShell

J

John Vottero

#1
Microsoft recently announced that the source code for the .NET Framework
libraries would be made available so that developers can see and step into
the code. Scott Guthrie's blog post is here:

http://weblogs.asp.net/scottgu/arch...rce-code-for-the-net-framework-libraries.aspx

Part of that blog post says:

"We'll begin by offering the source code (with source file comments
included) for the .NET Base Class Libraries (System, System.IO,
System.Collections, System.Configuration, System.Threading, System.Net,
System.Security, System.Runtime, System.Text, etc), ASP.NET (System.Web),
Windows Forms (System.Windows.Forms), ADO.NET (System.Data), XML
(System.Xml), and WPF (System.Windows). We'll then be adding more libraries
in the months ahead (including WCF, Workflow, and LINQ). The source code
will be released under the Microsoft Reference License (MS-RL)."

Are the PowerShell libraries covered by the "etc"? I certainly hope so.
If not, how/who can we lobby to get the PowerShell libraries added to this
program?
 

My Computer

M

Marco Shaw [MVP]

#2

> Are the PowerShell libraries covered by the "etc"? I certainly hope
> so. If not, how/who can we lobby to get the PowerShell libraries added
> to this program?
>
Good question. Let's wait and see for the next few days/weeks to see if
anything is announced by the PSH team. Then try putting something up on
the connect site:
https://connect.microsoft.com/site/sitehome.aspx?SiteID=99

Marco

--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp

PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:
http://marcoshaw.blogspot.com
 

My Computer

K

Keith Hill [MVP]

#3
"John Vottero" <JVottero@xxxxxx> wrote in message
news:O$hU1X3BIHA.5328@xxxxxx

> Microsoft recently announced that the source code for the .NET Framework
> libraries would be made available so that developers can see and step into
> the code. Scott Guthrie's blog post is here:
>
> http://weblogs.asp.net/scottgu/arch...rce-code-for-the-net-framework-libraries.aspx
>
> Part of that blog post says:
>
> "We'll begin by offering the source code (with source file comments
> included) for the .NET Base Class Libraries (System, System.IO,
> System.Collections, System.Configuration, System.Threading, System.Net,
> System.Security, System.Runtime, System.Text, etc), ASP.NET (System.Web),
> Windows Forms (System.Windows.Forms), ADO.NET (System.Data), XML
> (System.Xml), and WPF (System.Windows). We'll then be adding more
> libraries in the months ahead (including WCF, Workflow, and LINQ). The
> source code will be released under the Microsoft Reference License
> (MS-RL)."
>
> Are the PowerShell libraries covered by the "etc"? I certainly hope so.
> If not, how/who can we lobby to get the PowerShell libraries added to this
> program?
>
Even if they aren't, Lutz Roeder's Reflector utility gives a pretty decent
view into the inner workings of most .NET assemblies including the
PowerShell assemblies.

http://www.aisto.com/roeder/DotNet/

--
Keith
 

My Computer

M

Marco Shaw [MVP]

#4
John Vottero wrote:

> Microsoft recently announced that the source code for the .NET Framework
> libraries would be made available so that developers can see and step
> into the code. Scott Guthrie's blog post is here:
>
> http://weblogs.asp.net/scottgu/arch...rce-code-for-the-net-framework-libraries.aspx
>
>
> Part of that blog post says:
>
> "We'll begin by offering the source code (with source file comments
> included) for the .NET Base Class Libraries (System, System.IO,
> System.Collections, System.Configuration, System.Threading, System.Net,
> System.Security, System.Runtime, System.Text, etc), ASP.NET
> (System.Web), Windows Forms (System.Windows.Forms), ADO.NET
> (System.Data), XML (System.Xml), and WPF (System.Windows). We'll then
> be adding more libraries in the months ahead (including WCF, Workflow,
> and LINQ). The source code will be released under the Microsoft
> Reference License (MS-RL)."
>
> Are the PowerShell libraries covered by the "etc"? I certainly hope
> so. If not, how/who can we lobby to get the PowerShell libraries added
> to this program?
>
Talked to the PowerShell team about this. Basically, releasing the
source would take resources away from the current development.

I'd much prefer to see updates to PowerShell over seeing the source.

It would be cool to see source for more cmdlets and providers though.

Marco

--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp

PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:
http://marcoshaw.blogspot.com
 

My Computer

Users Who Are Viewing This Thread (Users: 1, Guests: 0)