Google Search API for .NET 0.2 beta and Google Translate API for .NET 0.2 beta released


No more default http referrer. User must set it as a parameter of constructor.

Delete old Translator and Searcher classes.

Updated comments for better document.


Change all API Using string parameter instead of enum parameter.

Add new Enumeration class and enumerations for API parameters.

The API changed a lot this time. Please let me know whether you like these changes or not.


All codes are refacted (StyleCop format).

Update the APIs to support latest Google APIs.

Now can customize referrer, accept language, API key and timeout times.


Update the supported language list for Google translate api.

Set “” as the default http referrer. (Now you cannot set your own http referrer)

No more v0.2, new features will come with v0.3.

Google APIs for .NET

Provides simple, unofficial, .NET Framework APIs for using Google Ajax RestFULL APIs (Search API, Language API etc.)

How LAZY I am. I should release nearly a month ago.

Indeed, 99+% of source have been finished when I release the Google Search API for .NET 0.1 and Google Translate API for .NET 0.1.1.

I just wait some bugs from the last versioin, so I can do some change.

I do fixed one bug, only one.

Ok, see what’s new.

The new versions are nearly no different for using, but the foundation is changed.

Replace Json.NET 2.0 by Microsoft official WCF.

And implement the HttpUtility, so not need the System.Web any more.

It now support .NET 3.5 sp1 Client Profile.

You can download here:

More in formations, please visit the project’s site:

Tags: , , , , , ,

10 Responses to “Google Search API for .NET 0.2 beta and Google Translate API for .NET 0.2 beta released”

  1. Klaw Says:

    Hi there,
    Any chance of releasing the .net 2.0 version of the dll? I tried compiling but the csproj files are not cooperating. (And I only have visual c# express)

    I think it’s a nice and simple tool that’s really useful 🙂

  2. iron9light Says:

    Hi Klaw,
    Not .Net 2.0, it’s 0.2 beta.
    I’ve changed the infrastructure base on WCF.
    More detail, please visit the project site.
    You need c# express 2008. and NUnit.

  3. Glenn Says:


    Thanks for the fantastic work. I found your stuff last night and created some simple PowerShell cmdlets to allow googling from powershell.

    Code is on this google project: glennsgooglepowershell

    Screenshots of some examples are on the Examples page.

  4. Raghav Says:

    Hi iron9light,

    I have been using the API for more than 2 months but yesterday my client notified me that the results from the Google seacrh API and the results on the same keyword from web broswer both doesn’t match.

    First few results are the same but later results are different. The later results returned by API sometime found on another page (say 2 or 3 page).

    Is it a problem from Google or some settings in API?

  5. derek Says:

    Google does something on their end to mix up the results a little. Probably to stop people from using this for unintended purposes.

  6. Terkel Says:

    Thanks a lot mate!
    Keep up the good work, I love the Translate API!

    Thanks a billion!

  7. dima Says:

    Great work 🙂
    but i have a question:
    why cant i translate a huge text?Are there restrictions in Api on number of characters or smth?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: