Amazon.com Widgets

.NET Framework 3.5 SP1 Allows managed code to be launched from a network share!

This has got to be one of the most consistently asked for "features" of .NET from the start!     Download .NET Framework 3.5 Service Pack 1

Run off a network share with local permissions - You have voted and we have listened!  We have brought managed executables in line with native code executables in how they behave when run off a network share.  Yea!   

Vance has the full scoop.. If you want to send someone flowers for getting this done, it is Vance... he designed, coded, tested, cajoled, prodded, persisted and advocated strongly for the fix.

Download .NET Framework 3.5 Service Pack 1

Published 13 August 08 11:18 by BradA
Filed under:

Comments

# Brad Abrams : Poll: Allowing .NET EXEs to run off a network share said on August 14, 2008 2:48 AM:

PingBack from http://blogs.msdn.com/brada/archive/2007/10/26/adhoc-poll-allowing-net-exes-to-run-off-a-network-share.aspx

# Dirk said on August 14, 2008 5:48 AM:

Couldn't this be done using CAS before?

# sambo said on August 14, 2008 6:17 AM:

I heard a lot of featured in .NET 3.5 SP1.

# netsam said on August 14, 2008 8:25 AM:

windows has enough problem with its owm. Now it adds more security venerability.

# John said on August 14, 2008 8:32 AM:

".NET Framework 3.5 SP1 Allows managed code to be launched from a network share!"

You make this sound like some great new feature.  It isn't.  It's a bug fix.  Yeah, I'm glad Microsoft fixed this, but it isn't something you should be proud of.  Fixing this in 2008 doesn't diminish your guilt for allowing this bug to exist for 5+ years.  How much pain has this caused your customers over that time?  Do we get some compensation for our aggravation?  This was not some technically difficult problem.  It was simply a bad design choice, which you persisted in and defended long after it was apparent to everybody else that it was wrong.

# Francois Ward said on August 14, 2008 9:14 AM:

I'm not sure I get it. This was always possible via CAS for those who wanted it. You could even push it as a policy via a domain, so you wouldn't need to do it computer by computer...

So I always thought it was a great design choice originally, since it is in line with the "secure by default, unlock the risks you want on your own" mindset which works quite well in the Unix world.

So why exactly was the default changed? Or is this something more?

# Scott Bruno said on August 14, 2008 9:21 AM:

Yay, thank you Vance. In lieu of flowers please accept this beer []?

For those of you wondering why this is a good idea, let me just say if this hasn't been a problem for you then just be happy for the rest of us.

# Tester Bob said on August 14, 2008 9:27 AM:

If this "bug" wasn't fixed before, then the world was not ready for it to be so.  Now it is.  We would not exist without Microsoft so show some respect.

# Jimmy Bergmark - JTB World said on August 14, 2008 10:31 AM:

Does this work with existing applications or is a recompile needed?

# Andrew Robinson said on August 14, 2008 11:48 AM:

Followup to Jimmy's questions, does this require an app target the 3.5 framework or will any old 2.0 app work?

# BradA said on August 14, 2008 12:14 PM:

Jimmy\Andrew -- No, an existing application does not have to be recompiled or changed in any way to take advantage of this.   Your current 2.0 Applications will just work, you don't have to target anything new in 3.5..

# Vincent said on August 14, 2008 4:01 PM:

Quoting Vance Morrison: "The problem is that failing to run managed code WHILE STILL ALLOWING UNMANAGED EXE's to run, does not provide any security (because hackers will simply use unmanaged code)"

Thanks god! And what's next? CHM help files? If you follow the same logic I believe CHM files on a network share are not that much of a security problem...

# Gerry said on August 15, 2008 3:57 AM:

Installed  .NET Framework 3.5 Service Pack 1; NBC OLYMPICS site no longer played Silverlight video; then uninstalled SP1 and then OK again. (Playing Silverlight 2 Beta 2).

# Jimmy Bergmark - JTB World said on August 15, 2008 9:02 AM:

Thanks for the confirmation. This makes the news even better!

# OPC Diary said on August 15, 2008 9:07 PM:

Brad Abrams : .NET Framework 3.5 SP1 All...

# BradA said on August 15, 2008 9:52 PM:

Gerry - I am sorry you have run into this issue... I personally have the same configuration and my machine works great.    One theory is that your user agent string might have gotten corrupted.  Type this into the browser address bar and send me the results (brada@microsoft.com).

javascript:document.write("<br/>userAgent string:"+navigator.userAgent+"<br/>");

# Gerald Dorman said on September 5, 2008 1:23 PM:

On 8/15/2008, I sent you this message:

Installed  .NET Framework 3.5 Service Pack 1; NBC OLYMPICS site no longer played Silverlight video; then uninstalled SP1 and then OK again. (Playing Silverlight 2 Beta 2).

You responded with your suggestion that User Agent string was the problem.

Finally, I received notice that IE does have a bug. You can see the response at Microsft Connect, Bug ID 362923.

Thanks for you great help.

# Joycode@Ab110.com said on September 7, 2008 11:38 AM:

【原文地址】 .NET Framework 3.5 SP1 Allows managed code to be launched from a network share! 【原文发表日期】 13 August

# Seth said on October 31, 2008 9:05 AM:

@netsam:

You just made my day: "... security venerability"

ROTFL

I hope that was an intended typo, in which case you get the full bonus points!

New Comments to this post are disabled

Search

This Blog



These postings are provided "AS IS" with no warranties, and confer no rights.



Ads by Lake Quincy Media

Syndication

Page view tracker