We have a document library that is built inhouse. We are migrating to SharePoint 2010 Document Library, but this will be a time consuming process and many very old documents may not get moved to SharePoint at all. I would like to provide the same experience for our users when they open a document from SharePoint or our legacy system. The behavior I would like is like when you open a Workbook or Document that is rendered in the browser using the "Open In Excel" and "Open in Word" button that you get when you open a document stored in a Share Point Document Library.
I am not sure what this technology is called or where to start looking to configure this or integrate into an addin.
Any starting points are much appreciated.
I'm not exactly clear on what your question is, but perhaps you are looking to use the Office Web Apps. This allows you to use the Office applications within the browser.
Related
This seems real simple but Google is not very clear. I made a Vb.net app, works great on my desktop. I want to put it into SharePoint so others can download and use it. Will this work?
Yes, but not immediately. SharePoint blocks certain file types which you're going to have to allow. You can find more about that here (note: you can pick the version of SharePoint you have just under the heading for relevant documentation).
I am maintaining a set of process diagrams in visio 2007. For viewing I save the files as HTML and publish them on a web server.
It works great but its a real pain to maintain (a paintain ;-).
I am looking for a way to do this as some kind of batch job, currently the process is:
open each file
file>save as web page
in the save as web page dialogue:
select location
publish > open new dialogue
change title (i dont mind if i have to miss that step)
select web page to insert it into (my template)
done
The tools I have availiable are:
Visual studio 2010 express (i prefer c# but whatever)
Visio 2007(i have another laptop with visio 2010 which i can use too but the source files will be 2007 - that's not changing for the moment)
Ruby - may be easier if it doesn't require office integration.
(BTW I know about process repository in OSS 2010 and i have tested it with visio 2010 web diagrams - that works and would probably be a better option for anyone who has the choice, though its not perfect)
(batch file or command line would also be cool but i have not found a way of saving as web page from command line)
You can use Visio's COM interop API to do what you want (I think). I'd start by just recording a macro while manually doing the export, and then look at the VBA code that generates. You could then adapt that in C#, or VBScript/VB6 if you want something you can call with a command shell.
As Jon highlights, there's a whole API for using the SaveAsWeb functionality from code. I wrote a post about it a little while ago, which you can see here:
http://visualsignals.typepad.co.uk/vislog/2010/03/automating-visios-save-as-web-output.html
The post is VBA based but the .net version is very similar and there's also examples in the Visio 2010 SDK:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=12365
All my googling returned only information related to how to add additional right click features.
I swear somewhere I saw screenshots of MSS2010 being used where right clicking provided the menu to do various operations, versus having to use the ribbon, or worse that awful menu pictured here.
I was expecting this to all be drag drop... :(
I'm really disappointed with the lack of ajaxy-ness built into mss2010. I can't believe every save/apply reloads the whole page.
SharePoint is a massive product. Microsoft appears to be adding and improving as much functionality as it can in each release.
A high priority of Microsoft for SharePoint 2010 was to redo the HTML for the end user pages. And it is much improved. The poorly formed, table heavy HTML of SharePoint 2007 now has more divs and unordered lists. However, you have stated that you do not like their design choices of the ribbon and full page refreshes. And you also do not like that UI improvements did not extend to system pages in the layouts directory.
SharePoint 2010 was released almost a year ago. Functionality changed during the beta, but it is unlikely that big changes will be introduced at this point. Your two best bets for getting your desired functionality are:
Create a CodePlex project that provides the functionality you want. If the project becomes popular, Microsoft might include it in the next release.
Based on Sharepoint Feature Request, post your request to the SharePoint forums with a subject of "FEATURE REQUEST". If Microsoft agrees to your request, it could be included in the next release.
MacroView specializes in document management, email management and knowledge management solutions based on Microsoft Office and Microsoft SharePoint.
MacroView DMF and MacroView Message add a new pane to Outlook which displays all the areas of the SharePoint environment for which you have access permission. The new pane in Outlook provides:
Searching across the SharePoint DM store with results displayed in Outlook
Formatted previews of files in SharePoint, without the need to download and open
Extensive right-click menu for files and areas
Right-click to create new Libraries and Folders
One-click access to your Favorite document libraries and folders in SharePoint
Automatic creation of Favorites – e.g. for Projects for which you are a timekeeper
Drag & Drop from everywhere to anywhere to save emails or attachments to ANY area where you have permission
Go here for more information
I'm working with Visual Studio 2010 and Sharepoint 2010. I would like to know if there's a way to have a web part that crawls all the data within a SharePoint site so I can save it into a custom db.
You can certainly create a custom web part that will do this. I do not know of an out of the box web part that will work. I began writing something like this when I found SharePoint List Source and Destination. It's a CodePlex project for an SSIS SharePoint adapter. We did not need a user interface for the extract, so we used it successfully last year for transferring data between SQL Server and SharePoint.
Sounds like all you need to do is use the API, OOB web services, or the Client OM to write some code and access the lists directly. Which approach you take depends mostly on where the code will run.
Well I found this article - Document Library Tree View Web Part for SharePoint - it is a Web Part that shows all the info of any of the document libraries within a site. At least I know how to crawl that kind of library.
I am designing a shared add-in using VB.Net 2008 and VSTO that has to fire up when any MS Office App is started. It has to work for both 2002, 2003 and 2007 applications. I have managed to put together a working add-in that pops up a test message stating the version of Office and the Application name and tested this across all the apps ok.
The next part of the solution is to code the application specific code that needs to run for document auditing and corporate protective marking as well as, for example; in Excel checking that all the Add-Ins are linked to the Network Add-Ins folder.
My approach from now was going to be to late bind against the application object and set one of my typed (e.g. Excel) application object references which exist in the code to this object.
I'm still relativly new to VSTO so if I am doing something odd please can you let me know! :)
Ta.
I have completed this project and did it the way I specified using late bindig. It works lieka dream for all office apps both XP and 2007. :) I feel like I am announcing this to myself though as I didn't recieve a single answer or comment. Maybe you should have sexed up the title a bit Mas. Yeah maybe I should.