I'm evaluating the IT-Hit Webdav component. Their Delta-V server sample is my starting point. If I open a word document directly from a Sharepoint site, MS Office shows a button which enables me to check out the document if needed. While using the IT-Hit server doesn't provide this feature for MS Office. It is important for us, that our own WebDav sever created with IT-Hit provides the same features as Sharepoint does.
Am I doing something wrong, or is this just not possible?
Rgards
Microsoft SharePoint and Microsoft Office are using a bunch of proprietary SharePoint protocols for comunication, they are not using DeltaV. IT Hit WebDAV Server Engine does not implement that Microsoft protocols. Therefore you can not achieve the same functionality only implementing DeltaV or using DeltaV sample.
The only server that implements Microsoft SharePoint protocols as far as I know is Alfresco.
Related
I don't have any idea how to connect mvc application with outlook so if some know
How to Connect MVC .net project with Outlook Mail.
Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution. Read more about that in the Considerations for server-side Automation of Office article.
If you deal with Exchange accounts you may consider using EWS or Graph API. See Explore the EWS Managed API, EWS, and web services in Exchange for more information about EWS.
I have an ASP.NET application where I need to push data from the ASP.NET application into the client's Timberline Office database at the users request. I need to do this by connecting to the client's Pervasive ODBC Driver to insert data into the Timberline data structures.
I would like to build a component (ActiveX, or something like that) that would work in IE at a minimum, and also the Firefox and Chrome browsers if possible. I would like to build this component using VB.NET and Visual Studio 2008 if possible.
Can anyone provide any resources (web sites, code examples) to help me with this?
Thanks
I'm working on a project where we will be interacting with the ReportService2010 reporting web service under SQL Server 2008 R2. In the past, I've worked with the ReportService2005.asmx, and my problem here is, I can't find any reasonable examples on how to render a report with this new (2010) reporting web service.
When using the 2005 web service, there was a "Render" method that was provided when creating your proxy with the wsdl.exe utility. Is there an equivalent method (or set of methods), to accomplish the same thing using the ReportService2010 service? Or are there any decent examples of an end-to-end intialization and calling of the new proxy?
Even MSDN doesn't have much information, and in certain parts of the ReportService2010 API docs, there are old snippets of code that were only applicable to the 2005 web service.
UPDATE: A better question might be how have things changed between SSRS 2008 and SSRS 2008 R2 with regard to calling the report service(s) programmatically...I can see that even under SSRS 2008 R2, there still exists a ReportService2005.asmx, as well as a ReportExecution2005.asmx, but there is not a corresponding ReportExecution2010.asmx.
sigh
SOLUTION UPDATE:
After talking to someone at my company, I was informed of the following:
The 2006 web service was introduced to support sharepoint integration in 2008.
The ReportService2010 web service was introduced to merge all the functionality introduced by 2006 with the 2005 web service.
ReportService2005 web service will continue to be used for report execution. I don't know why, but something tells me it has to do with business decisions for backwards compatibility. My coworker said we are intended to continue to use ReportExecution2005 for rendering, and ReportService2010 for all other functionality (querying the SSRS server for reports, params, etc).
Unfortunately all the above information was culled from a variety of links, none of which concisely stated all of the above. It's the kind of thing that you would normally assume a vendor to explain to client developers.
SQL Report Server provides 3 different endpoints.
ReportService2010: Provides the APIs for managing a report server that is configured for either native or SharePoint integrated mode.
ReportExecution2005: Provides the APIs for running and navigating reports.
ReportServiceAuthentication: Provides the APIs for authenticating users against a report server when the SharePoint Web application is configured for Forms Authentication.
Thus, in order to render the report you must use this one ReportExecution2005.
Here it says what I have pasted above: http://www.blograndom.com/blog/2011/03/reportservice2010-asmx-is-not-the-only-end-point/
Here you can find an example (it has some errors though) to get started
http://blogs.msdn.com/b/christophputz/archive/2010/05/07/accessing-ms-reporting-services-with-java.aspx
Good luck!!
I want to build a custom document management web application that ties in with sharepoint for the actual document versioning and storage. I'm hoping for something like a sharepoint widget that I can plug into my web application that would allow me to tie in with sharepoint and download documents, make edits to them, and upload them back to sharepoint, with sharepoint handling all of the versioning and storage.
Basically I'm looking for a sharepoint API.
If WSS is the answer to this, are there licensing issues that I need to consider?
Thanks.
The best way forward is probably to use SharePoint's web services as that way your application can run on a server that doesn't have SharePoint installed.
Regarding Licensing, as long as you are licensed for Windows Server then WSS is free. However, depending on what database you use you may need to make sure that your users are licensed for SQL Server. Have a look at these links:
SharePoint Connections
Technet
Eggheadcafe
Wouldn't it be easier to do some development to customize SharePoint to your needs instead of just using it as a backend?
If it's SharePoint 2007 you're talking about, then on the server side you have the SharePoint API (Microsoft.SharePoint.dll) and on the client side, SP provides web services for manipulating lists, libraries, users and most other things you might need.
As Jeremy said, getting data to and from SharePoint through the Web Services, requires you to write CAML queries, but it's made easier by the help of tools such as this free CamlQueryBuilder
There's loads of documentation on both the API and the web services online.
If you're planning on using SharePoint 2010, all this will be quite easier, as more options are available for developers, e.g. API for the client side as well as the server side. Also new in 2010 is LINQ for SharePoint, which IMO really rocks!
Sharepoint is accessible with CAML Queries in that you can create, modify, and delete any object in Sharepoint with this.
You could create your own front end and just communicate to sharepoint.
As far as licensing, WSS comes with any Windows Server OS, so your client would just buy a license to the OS and be fine.
I'm installing Microsoft Search Server 2008 express with a view to indexing some content for an intranet application.
Having not used Search Server before, i am looking at ways of my asp.net app (.net 3.5) querying the search server.
I'm just starting to look into Search Community Toolkit to see if it is relevant to what i want to achieve. But was wondering if you guys can point me in the right direction (code, articles, etc).
Many Thanks.
Microsoft provides developer APIs. The assemblies are part of the Search Server 2008 SDK.
http://msdn.microsoft.com/en-us/library/bb931107.aspx
After a few google searches, came across this website which fits the bill pretty well.
http://labs.episerver.com/en/Blogs/Ted-Nyberg/Dates/2009/1/Using-EPiServer-and-Microsoft-Search-Server-2008/
Describes using the Search Server web service, which is quite a clean way to do it.