Forget file formats. The battle is Sharepoint
People are agog that Microsoft has announced support for Open Document Format (ODF), but I'm not sure why. This was a foregone conclusion once Microsoft figured out how to move lock-in above the file level to the content network.
In other words, to Sharepoint.
Microsoft has been hell-bent on getting enterprises to dump content into its proprietary Sharepoint repository, calling it the next Windows operating system. I call it the future of Microsoft lock-in.
Microsoft doesn't need to zealously guard file formats anymore. It already owns the next few decades of lock-in, and many enterprises are willy-nilly dumping their content into Microsoft's proprietary repository at a pace and in a manner that is as potentially destructive for those enterprises as it is beneficial to Microsoft's income.
Microsoft has done well in creating a comparatively easy to use and deploy front-end for Sharepoint, which is far better than the antiquated systems from Documentum, FileNet, Interwoven, etc. But if Microsoft really wants to do its customers a favor, it will open up its repository to make it as easy to get content out of the repository as it is to get it into the repository.
That's what would help customers. Is Microsoft interested?
Disclosure: I work for Alfresco, an open-source alternative to Microsoft Sharepoint.
Matt Asay is general manager of the Americas and vice president of business development at Alfresco, and has nearly a decade of operational experience with commercial open source and regularly speaks and publishes on open-source business strategy. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure.
- Topics:
-
Microsoft,
-
Industry news
- Tags:
-
Microsoft,
-
Sharepoint,
-
file formats,
-
Alfresco
- Bookmark:
- Digg
- Del.icio.us
3) Create a linked table with Access (no code solution, might be more applicable to List based data than binary attachments). So based on this, this whole post looks like typical FUD from someone who doesn't know what they are talking about.
Please fix the lwn.net and infoworld.com links.
1. Refer the Sharepoint object model library in a project ,
2. Write a console application and replace siteURL string with your SharePoint site url
3. At the end of execution of third line you will get the document at byte array
SPWeb web = new SPSite(siteURL).OpenWeb();
SPDocumentLibrary dox = web.Lists["Documents"] as SPDocumentLibrary;
byte[] fileBytes = dox.Items[0].File.OpenBinary();
Above lines may be too technical for a user but it's really an easy job to recover.