Ambiguous structure name

[GoogleCodeExporter]

When importing both:

Google.API.Search and
Google.API.Translate

The enum Google.API.Language is ambiguous and can hardly be disambiguated. 
(unless using only full references which is a drag)

Original issue reported on code.google.com by atre...@gmail.com on 18 Feb 2009 at 10:56

[GoogleCodeExporter]

I think most of people will use one of the two only.

If you wanna both, you can compile the source by yourself.

It's not hard.

You even do not need to change one line code.

Original comment by iron9li...@gmail.com on 1 Mar 2009 at 7:33

• Changed state: Done

[GoogleCodeExporter]

Would you consider addressing this?
1) I would prefer no to create a private build.
2) I mainly dev in vs2005 and its a little more work to port everything :)
3) They really should be different as I am sure I will not be the last to use 
both 
in the same project.

(I am writting an app for a POS DB that goes and looks up the name of an item, 
then 
translating it into an alternative langueage, and then uses the picture search 
to 
look up an item to tie it to the item.)

No biggie if you don't but I would just like to make sure someone doesn't 
update 
(either on purpose or because another app uses) the libraries and then breaks 
the 
App. Even though it may be easy enough to mod the source and create a private 
build, 
I would then want to make sure the name of the dll was different to prevent the 
before mentioned update.  That doesn't do you or anyone else justice for all 
the 
hard work you have done.

Thanks

Original comment by w...@mywordsonapage.com on 6 Jul 2009 at 6:57

[GoogleCodeExporter]

A new project (or even a new solution) to put them all together, is that what 
you want?
Or three separated projects (Core, Translate and Search)?
I think I should provide both.

Original comment by iron9li...@gmail.com on 6 Jul 2009 at 7:28

• Changed state: Accepted

[GoogleCodeExporter]

Saw the new all inclusive build, works for me!!!  Sorry, I haven't replied 
sooner, 
was working on my multitasking skills.  

The translation phase of my project is done, now for the PIC search phase :)  
just 
need(ed) the all inclusive lib.

I don't necessarily think you had to come up with a single solution/dll.  Just 
need 
to be able to avoid the ambiguous reference when pulling in multiple lib 
references 
into a project.  

Regardless thanks for the time and effort.  I am sure I won't be the last to 
thank 
you.

Original comment by w...@mywordsonapage.com on 13 Jul 2009 at 6:39

[GoogleCodeExporter]

There is a new all-in-one solution for it.
Anyone want it should compile from svn by itself.

Original comment by iron9li...@gmail.com on 22 Jul 2009 at 7:31

• Changed state: Fixed