.NET Framework 3.5 Is Shared Source(weblogs.asp.net)

submitted by benrickbenrick(1020) 4 years, 7 months ago

Microsoft's .NET Framework 3.5 is going to be released open source.

26 comments |category: |Views: 152

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
Comments:

posted by gavinjoycegavinjoyce(25.7k) 4 years, 7 months ago 0

Not quite open source, more like shared source. A great move nonetheless.

Reply

posted by gavinjoycegavinjoyce(25.7k) 4 years, 7 months ago 0

Debugging is going to be fantastic, what a nice journey it will be navigating the depths of the .NET framework while debugging.

Reply

posted by atifazizatifaziz(1000) 4 years, 7 months ago 0

Great move, indeed, that it deserves a kick of a lifetime!

Reply

posted by benrickbenrick(1020) 4 years, 7 months ago 0

Yeah it isn't quite open source, but it is close enough. I wouldn't expect any more than this.

Reply

posted by jamesewelchjamesewelch(2275) 4 years, 7 months ago 0

Nice...

Need to allow users to do a double drop kick on a story once a day :)

Reply

posted by gavinjoycegavinjoyce(25.7k) 4 years, 7 months ago 0

Published to the homepage in 13 minutes - a record.

Reply

posted by jamesewelchjamesewelch(2275) 4 years, 7 months ago 0

I thought about adding that category to the Zeitgeist - Quickest articles to be published. Easy to do, just subtract the CreatedOn from the PublishedOn. Didn't think it would be very useful other than bragging rights :) I think the DNK articles would mostly be in that top 10 list, those get published pretty fast too.

Reply

posted by MichaelDotNetMichaelDotNet(450) 4 years, 7 months ago 0

What happens when developers begin coding around implementation details though? That's my only concern, still very cool though.

Reply

posted by yesthatmcgurkyesthatmcgurk(4063) 4 years, 7 months ago 0

Hell, when has it not been open source? Reflector is such an awesome tool. "I wonder what this control does in this particular situation?" *reflectors* "Aaah"

Reply

posted by yesthatmcgurkyesthatmcgurk(4063) 4 years, 7 months ago 0

Comments, too!! Now THAT is awesome.

Reply

posted by gavinjoycegavinjoyce(25.7k) 4 years, 7 months ago 0

"What happens when developers begin coding around implementation details though?"

As yesthatmcgurk says, they can already do that with reflector. It is also their problem to deal with.

"Hell, when has it not been open source?"

We can now see the code as it was written. It also indicates (to me anyway) that someone in MS is pushing the open source model internally. I hope to see a fully open source .NET framework in the future sometime (.NET 5 perhaps?).

Reply

posted by MichaelDotNetMichaelDotNet(450) 4 years, 7 months ago 0

@gavinjoyce,

It's true that they CAN do that will reflector. Not many do I wager. The difference now is that this code is going to be in every developer's face via VS2008 debugging.

Reply

posted by yesthatmcgurkyesthatmcgurk(4063) 4 years, 7 months ago 0

Somebody go over to /. and see if they're freaking out.

Wait, strike that, how BAD they're freaking out.

Reply

posted by gavinjoycegavinjoyce(25.7k) 4 years, 7 months ago 0

If they link to Scott's post, I wonder will our little 'kick it' button hold up. Does it count as a slashdotting if it doesn't? ;)

Reply

posted by jamesewelchjamesewelch(2275) 4 years, 7 months ago 0

Yeah, I agree. It's always been easy to use Reflector, but I'm still amazed at how many technologists or developers think that .NET assemblies are compiled and can't be just "opened" and looked at.

I really don't think this will have a major impact on .NET in the short term, but hopefully its a small step in a better direction for future .NET products/frameworks.

Reply

posted by jamesewelchjamesewelch(2275) 4 years, 7 months ago 0

@gavinjoyce,
>If they link to Scott's post, I wonder will our little 'kick it' button hold up. Does it count as a slashdotting if it doesn't?

Might be a good time to add that image caching code to the image gen...

Reply

posted by gavinjoycegavinjoyce(25.7k) 4 years, 7 months ago 0

@james

I'm just about to leave here so I won't be able to get it done. I think it should be OK, it is loaded via javascript on Scott's blog so it won't slow his post down anyway.

Reply

posted by aquinasaquinas(20) 4 years, 7 months ago 0

*blink*

Reply

posted by AarononthewebAaronontheweb(1140) 4 years, 7 months ago 0

I honestly don't understand the degree of benefit this will provide to the average .NET developer.

However I am enjoying watching the idiots at ReadWriteWeb and Slashdot clown themselves over this announcement.

Reply

posted by jamesewelchjamesewelch(2275) 4 years, 7 months ago 0

I don't think that there won't be any benefit for the average developer.

And the above average developer already uses Reflector for some of this (as others pointed out above).

Reply

posted by AarononthewebAaronontheweb(1140) 4 years, 7 months ago 0

That's what I thought and wrote as much on AjaxNinja. Thanks, James.

Maybe one day after I get a few more years of experience under my belt in a professional .NET development environment (interviewed for a position today!) I'll be adept enough to appreciate this release.

Reply

posted by crpietschmanncrpietschmann(11.3k) 4 years, 7 months ago 0

"We can now see the code as it was written. It also indicates (to me anyway) that someone in MS is pushing the open source model internally. I hope to see a fully open source .NET framework in the future sometime (.NET 5 perhaps?)." - gavinjoyce

We already have an Open Source .NET Framework; it's called the Mono Project (http://mono-project.com). I know it's not the same as Microsoft releasing the .NET Framework itself as full Open Source, but we don't want to forget about such a cool project.

Reply

posted by JudahGabrielJudahGabriel(814) 4 years, 7 months ago 0

James and Aaron, this benefits developers in 3 ways beyond what Reflector gives us:

First, the source comments are intact, which means it becomes easier to understand .NET library source code.

Second, the code structure and local variable names are preserved.

Third, we can use the debugger to step in to .NET libraries and use the threads, locals, watch, etc. windows.

Reply

posted by cdjacocdjaco(5) 4 years, 7 months ago 0

Wow.

Reply

posted by marco.ragognamarco.ragogna(0) 4 years, 7 months ago 0

You can use Reflector to disassemble the code but with comments included is for sure more readable =)

Reply

information Login or create an account to comment on this story