Star MS To Release Source Code to .NET Framework Libraries
Linked by Thom Holwerda on Wed 3rd Oct 2007 19:39 UTC, submitted by gonzo
.NET (dotGNU too) "One of the things my team has been working to enable has been the ability for .NET developers to download and browse the source code of the .NET Framework libraries, and to easily enable debugging support in them. Today I'm excited to announce that we'll be providing this with the .NET 3.5 and VS 2008 release later this year. We'll begin by offering the source code (with source file comments included) for the .NET Base Class Libraries, ASP.NET, Windows Forms, ADO.NET, XML, and WPF. 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."
E-mail Print r 0   121 Comment(s) http://osne.ws/efy
Thread beginning with comment 275989
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Microsoft Reference License
by wirespot on Wed 3rd Oct 2007 22:00 UTC in reply to "Microsoft Reference License"
wirespot
Member since:
2006-06-21

Lawsuit time. Evidence shows that you looked at our code. MS kills mono or [insert_app_here].


So what if you look at the code? In most parts of the world the only problem is copyright, and it's not an issue unless you copy and paste the code. Or, to make absolutely sure, you use "clean room" development, where one developer looks at the original code, tells another what it does and the second developer writes new code from scratch, with the same functionality.

Software patents or reverse engineering are an issue only in some countries.

Reply Parent Bookmark Score: 2

Kroc Member since:
2005-11-10

Yes, but all Microsoft have to do is make the allegations. They don't have to back them up, or prove them conclusively. Microsoft can claim that such and such app is breaking the licence, and it's up to the app writers to prove otherwise, not Microsoft. MS fires off some cease and desists to the ISP, and before you know it, Microsoft have spun an allegation into an anti-open source, anti non MS-vendor bit of PR.

There's only so many ways you can make a simple function return an answer. Making other programmers have to tip toe around Microsoft's specific implementation will slow down development and increase administration. Just look at the audit that had to be done on ReactOS because of Microsoft allegations.

Reply Parent Bookmark Score: 7

navaraf Member since:
2005-07-08

Just look at the audit that had to be done on ReactOS because of Microsoft allegations.


At least spread correct information please. The audit wasn't done because of MS allegations, but because of allegations of people from inside the project and from related projects. MS never ever approached ReactOS about it.

Reply Parent Bookmark Score: 2

wirespot Member since:
2006-06-21

Yes, but all Microsoft have to do is make the allegations. They don't have to back them up, or prove them conclusively.


Yes they do. If you bring charges of copyright infringement you have to back them up. Of course you do.

I don't see what ISP's have to do with this. If you meant hosting companies, they usually check around. They don't boot their paying customers for allegations alone.

Reply Parent Bookmark Score: 2