We Keep Coding

Querying through a list of documents and its contents with Sharepoint 2010 Services

I am currently developing an application using Sharepoint 2010 Web services to access data from a Sharepoint server. Im using ListData.svc to get items of a particular list of documents saved in the SP server, and my aim is to be able to search through this list, including its documents contents. I have been researching through options, and have seen stuff like asmx, enterprise search API, query services, etc., but I am not quite sure if this would really crawl through the file contents.
Can you enlighten me on what web service to use to be able to search through a particular list of files-- all its properties and file contents? Similar to the search option in an actual Sharepoint site?
Thanks!

Id expect a quick google on "Sharepoint 2010 search api" to yield up https://msdn.microsoft.com/en-us/library/office/websvcspsearch(v=office.14).aspx which says "Search in Microsoft SharePoint Foundation 2010 exposes its search functionalities through the Query Web service. This allows you to access SharePoint Foundation Search results from client applications and Web applications outside of the context of a SharePoint site."
I guess if you read those docs, the solution will be in there.

How to show mysql database from java web service using c#

I've created a web service using Java (Netbeans IDE). The web service is a web service with MySQL database. and now I want to create a client application using C# Windows Form (Visual Studio IDE). I've added a web reference (wsdl link) on a client project. but I am confused about how to display the records from my database on my C# Windows Form.
Need help pleaseee,,, thx before...

You should add a service for get a value in your web service.for example GetData and in c# call the service.
Every service returns a specific type for example List<> or a class like Person.

WPF application to communicate with Microsoft Project Server 2010

One of our future requirement at work is to be able to read and write from our WPF application into Microsoft Project Server 2010. We know the fact that Microsoft Project Server 2010 is built on top of Sharepoint(from http://msdn.microsoft.com/en-us/library/office/ms504195%28v=office.15%29) so we know that you could be able to do this using Sharepoint programming(please correct me if I am wrong).
Based from searching in StackOverFlow and online we could not able to find any resources on how to communicate with Project Server using our WPF application. Is this really the case for WPF app and Project Server? Or we could be missing something. We recently implemented Exchange Server communication with our WPF app and we thought it will be similar case in terms of Project Server 2010.
(More info: We are using TFS for team collaboration)

True: Project Server is built on top of Sharepoint
Partially Wrong: Data related to Project Server (except some configuration information) can be accessed using SharePoint API calls.
Project Server uses its' own API called PSI: Project Server Interface, (link).
The API includes web services (WCF or ASP.NET) to access different data related to project plans, resources, etc. Some information can be accessed through different services, but set of fields in the case could be different: Field A + Field B could be accessed through Web service A, but only Field B could be accessed through Web service B
PSI works according to Security setups on the Project Server and there are required permissions defined for every function of the API.
I said that it is partially wrong that Project Server data can be accessed using SharePoint API. The partial is because you can synchronize your projects with SharePoint lists and in this case the SharePoint lists can be accessed using SharePoint API.

getting list for documents from external sharepoint site

There is a external sharepoint site --> http://(Servername)/FrmsRep/Lists/Sagicor%20Forms%20Repository/AllItems.aspx
I need to get a list for documents from here to my C# webpart.
How would I do that? I've been trying to search but can't find anything :-( OR I do not know what to search.

For external sharepoint site you could use
SharePoint Client Object Model - it use SharePoint Web Services
SharePoint Web Services e.g. Lists Web Service
ADO.NET Data Services

My existing webparts won't work in SharePoint

I have a standard ASP.NET 2.0 website.
It has a webpage page.
I have a webpart in my Company.Web.dll that I display on my webpart page on my website.All is good!!!
I would like to use this same webpart in SharePoint 2007.
I have a "site definition" project in VS2008 using Extensions for SharePoint 1.2. I have tried various ways to add the webpart from an outside assembly to my site definition. I have been able to deploy the webpart (where it is added to the webpart list of a webpart page) but I have been unsuccessful at adding the it to a page.
My Glorious Failures:
Created a shell webpart to just display the existing web part, basically just using my part as a control.
Attempted to modify the X.webpart and X.xml files created by VS2008 when you create a new webpart.
Both result in the following error while adding the web part to the page:
Exception
Microsoft.SharePoint.WebPartPages.WebPartPageUserException:
Cannot import XXXX Web Part.
at Microsoft.SharePoint.WebPartPages.WebPartImporter.CreateWebPart(Boolean
clearConnections) at
Microsoft.SharePoint.WebPartPages.WebPartImporter.Import(SPWebPartManager
manager, XmlReader reader, Boolean
clearConnections, Uri webPartPageUri,
SPWeb spWeb) at
Microsoft.SharePoint.WebPartPages.WebPartImporter.Import(SPWebPartManager
manager, XmlReader reader, Boolean
clearConnections, SPWeb spWeb) at
Microsoft.SharePoint.WebPartPages.WebPartQuickAdd.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
eventArgument)
Is there a special way I need to add my existing webpart to my site definition?

This sounds like a problem resolving the GUID at deployment time, as you can read about in this SO question.

To find the details of why the web part won't import, check the ULS logs. These are typically located at %CommonProgramFiles%\Microsoft Shared\web server extensions\12\LOGS. An entry will be logged here at the time you attempt to add the web part to the page. This should give you more detail.
My guess is that it is a code access security issue. Your web part must be strongly signed and needs a SafeControl entry in the web.config of the SharePoint web application. Apart from these things you should be able to just add it to the Global Assembly Cache to test if it works (best practice is to write a CAS policy file). See Deploying Web Parts in Windows SharePoint Services for more details.
I would try these steps before trying to integrate it as part of a site definition. Then at least you know the web part will actually run.
Also, VSeWSS is really designed for developing your web part using it from the very start. If you have the original source, you could try creating a new web part with VSeWSS and then replace with your custom code and update the .webpart and feature XML files. Then it should behave a little better. If you haven't committed to VSeWSS, try WSPBuilder as it's less painful.

ASP.NET webparts and Sharepoint Webparts are NOT the same. You should be able to use a ASPNET webpart within Sharepoint. See the following table:
ASP.NET 2.0 Web Part
For most business needs.
To distribute your Web Part to sites that run ASP.NET 2.0 or SharePoint sites.
When you want to reuse one or more Web Parts created for ASP.NET 2.0 sites on SharePoint sites.
To use data or functionality provided by Windows SharePoint Services 3.0. For example, you are creating a a Web Part that works with site or list data.
SharePoint-based Web Part
When you want to migrate a set of Web Parts using the SharePoint-based Web Part infrastructure to Windows SharePoint Services 3.0.
To create cross page connections.
To create connections between Web Parts that are outside of a Web Part zone.
To work with client-side connections (Web Part Page Services Component).
To use a data-caching infrastructure that allows caching to the content database.
For a Sharepoint webpart to work in a standard ASPNET application you would need to recreate your webparts in Visual Studio (as an ASPNET webpart) without the Sharepoint 2007 references for it to work correctly.
One nifty tool which I have used in the past is the SmartPart Worth checking out:
This lets you create a ASP.NET usercontrol (visually) in Visual Studio and then host this in Sharepoint. The smartpart acts as a wrapper wepart for your user control. Think of it like the page viewer webpart in Sharepoint except instead of it being HTML pages its ASP.NET UserControls.

You would need WSS 3.0, SharePoint MOSS or 2007 to use ASP.NET 2.0 WebParts. SharePoint 2003 or below and WSS 2.0 or below do not support ASP.NET WebParts.