Store Executables in Sharepoint: Why Not?

[smays]

From reading some posts in TechNet I see that it is possible to store executables in SharePoint. The question I have is why not store executables in SharePoint? One response to that question from TechNet was:

Just imagine if a user was to upload a .exe with a friendly name like "Skype.exe" but was really a virus - not good!

To me that is a weak argument. What is the difference between storing an executable in SharePoint and storing an executable on a file server?

Is there a *REAL* problem associated with storing executables?

Thanks,
Steve.

 

[ehaze]

from what i've read, everyone says it's a bad idea.
but, no one gives a firm example why...

maybe setup a VM, remove exe as blocked file type, and give it a shot.


let us know.

 

[smays]

I am talking to IT to see if they are willing to remove the restriction. I have not been given a yes or no yet. I will let you know if I can get the go ahead.

Steve.

 

[ehaze]

are you just wanting to store the .exe file in sharepoint, or execute it from sharepoint?

 

[smays]

Actually both. I do not know if it is possible.

One of the hats I wear as an engineer is a Win32 developer. As a general rule, my stand-alone executables lack dependencies. The only dependencies are related to test equipment installation, so running the executables directly from our file server works nicely and basically guarantees everyone is using the latest and greatest version without having to go through installations.

There is the basic problem of trying to update the copy residing on the network while people are running the program. Last but not least there are other distant design groups using my software who have VERY slow access to our file server. For the other design groups I copy and update all my software to their local file servers so they can access the software much faster.

I would like to store the official version of the software in SharePoint and then supply Windows Explorer friendly short cuts to the program so the program can be executed directly. I am thinking if someone is running the program, I could check out the program, update it, and check it back in. Whoever is running the program could then restart the program at the earliest convenience and use the latest and greatest version.

Steve.

 

[ehaze]

i've dealt with this sort of issue in the past.

ended up creating a new database table that the app would ping every X minutes. if the value in the table = true, the user would see a message box letting them know there was a pending update. then, after X minutes the users app would close. 99% of the time i would update after hours.


Managing file types:
SharePoint 2010

http://technet.microsoft.com/en-us/library/cc262496.aspx

2007

http://geekswithblogs.net/seanfao/archive/2007/11/12/116814.aspx

 

[SkipVought]

99% of the time i would update after hours.

1. after hours: after hours, when business is closed?

2. after hours: after hours of waiting?

Skip,
[sub]
Just traded in my old subtlety...
for a NUANCE![/sub]

 

[ehaze]

#1.

easier when dealing with small organizations (not global).