--
You received this message because you are subscribed to the Google Groups "Google Apps Domain Information and Management APIs" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-apps-mgmt-apis/-/iaWQqmDSbIYJ.
To post to this group, send email to google-app...@googlegroups.com.
To unsubscribe from this group, send email to google-apps-mgmt...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-apps-mgmt-apis?hl=en.
Thank you for the update, it’s very encouraging.
Although I think I may have mislead you when I mentioned version 1.1.3.0, and apologies if I did. I was merely saying that I have been using the Google Provisioning API’s since that version. Currently we are using version 1.9.0.0 of the .Net library for new applications and I still need to move some current applications to that version as they currently use 1.4.0.2.
So will these changes be included in the next version of the API? The issues are still applicable to the later versions are they not?
Thank you for all your work on this.
Regards,
David McMurray
Developer
Data Services, New College Nottingham
Thank you Claudio,
I’ll give that a try.
Hi,
I tried getting a read-only copy of the source from the link you gave using the following:
svn checkout http://google-gdata.googlecode.com/svn/trunk/ google-gdata-read-only
Both with and without a space after “trunk/” as I though that might have been a typo.
But I get the following error:
svn: E175013: Unable to connect to a repository at URL 'http://google-gdata.googlecode.com/svn/trunk'
svn: E175013: Access to 'http://google-gdata.googlecode.com/svn/trunk' forbidden
and the following without the space:
svn: E175013: Unable to connect to a repository at URL 'http://google-gdata.googlecode.com/svn/trunk/google-gdata-read-only'
svn: E175013: Access to 'http://google-gdata.googlecode.com/svn/trunk/google-gdata-read-only' forbidden
Any ideas?
Regards,
David McMurray
Developer
Data Services, New College Nottingham
Thank you for the confirmation of the correct command.
I found out this was a problem due to our NTLM proxy, I did wonder if that was going to be a problem, but since the error didn’t mention the failed authentication I thought it was an SVN issue. The source is downloading now.
Regards,
David McMurray
Developer
Data Services, New College Nottingham
http://www.ncn.ac.uk/content/email_disclaimer.aspx