GWSV12Helpers Work Item Rss Feed

Commented Issue: Update for Groove 2010 [28564]

jchristman3 — Sat, 14 Aug 2010 01:37:13 GMT

Changes with Groove 14 (2010) broke release 8.. I think the changes are small to fix this..
Comments: ** Comment from web user: jchristman3 **

See my comments in this discussion:
http://gwsv12helpers.codeplex.com/Thread/View.aspx?ThreadId=223545

Created Issue: Update for Groove 2010 [28564]

jchristman3 — Sat, 14 Aug 2010 01:36:33 GMT

Changes with Groove 14 (2010) broke release 8.. I think the changes are small to fix this..

Commented Issue: Exception throw : Unable to find HKLM_GrooveRegKey [14997]

jchristman3 — Sat, 14 Aug 2010 01:34:51 GMT

I've just download the "GrooveWebServicesV12HelpersProjects_Binaries.zip" archive from the "Release 8".
I've launched "GrooveWebServicesv12HelpersTestHarness.exe" and it throw a "Unable to find HKLM_GrooveRegKey" (see the attachement file).

- Windows Vista 64Bits build 6.0.6000
- Microsoft Office Professional 2007 SP1 installed
- Microsoft Office Groove 2007 installed (4.2.0.2623) SP1 MSO (12.0.6213.1000)

I've checked your source and see that you read the HKLM\Software\Microsoft\Office\12.0\Groove key, but there's nothing there in my registry.
(Line 199 of context.cs) :
// Look for Groove 12 client registry key first
Microsoft.Win32.RegistryKey HKLM_GrooveRegKey = Microsoft.Win32.Registry.LocalMachine.OpenSubKey(GrooveWebServicesV12Helpers.Shared.GROOVE_12_REG_KEY);

Is there a workaround or a fix ?
Comments: ** Comment from web user: jchristman3 **

I fixed this by pairing the Versions with the keys higher in code, and removing the code you are looking at:

// Look for Groove 14 client registry key first
Microsoft.Win32.RegistryKey HKCU_GrooveWebServicesRegKey = i_RealHKCU.OpenSubKey(GrooveWebServicesV12Helpers.Shared.GROOVE_14_WEB_SERVICES_REG_KEY);
if (HKCU_GrooveWebServicesRegKey != null)
{
CurrentVersion = "14.0";
}
else // Look for Groove 12 client registry key second
{
HKCU_GrooveWebServicesRegKey = i_RealHKCU.OpenSubKey(GrooveWebServicesV12Helpers.Shared.GROOVE_12_WEB_SERVICES_REG_KEY);
if (HKCU_GrooveWebServicesRegKey != null)
CurrentVersion = "12.0";
}

Commented Issue: Exception throw : Unable to find HKLM_GrooveRegKey

rebelzoo — Wed, 22 Apr 2009 14:38:15 GMT

I had this same problem with Vista 64. It seems to be failing in determining the version of Groove. Since I am just using this for myself, and always with Groove 2007, I just changed the code to assume 12.0 on this failure. I am sure there is a better way, but this worked for my needs. Hope this helps:

HKLM_GrooveRegKey = Microsoft.Win32.Registry.LocalMachine.OpenSubKey(GrooveWebServicesV12Helpers.Shared.GROOVE_REG_KEY);

if (HKLM_GrooveRegKey == null)
{
//throw new System.Exception("Unable to locate registry key HKLM_GrooveRegKey!");
// on failure Assume 12.0
CurrentVersion = "12.0";
}
else
CurrentVersion = (string)HKLM_GrooveRegKey.GetValue(GrooveWebServicesV12Helpers.Shared.GROOVE_CURRENT_VERSION_REG_KEY_NAME);

Created Issue: Groove-Import files in Issue Tracking Tool

vibhutipatel — Thu, 12 Mar 2009 06:57:37 GMT

hello,
I have to develop a dot net application which can import a files in Issue Tracking Tool of Groove.
I have downloaded Groove Web Services Development Kit from below link.
http://www.groove.net/solutions/develop/downloads.cfm and I have seen that there is no API available for importing a file in Issue Tracking tool .
So will it be possible to develop a dot net application which can import a files in Issue Tracking Tool of Groove?
Thanks In Advance !

Reagrds,
Vibhuti

Created Issue: Tool: Time tracker - Need SDK or similar doc. or Code Snippet

rishigirdhar — Wed, 30 Jul 2008 13:04:15 GMT

Hi,
There is a requirement for a dot net application to read and write data to/from Groove Time tracker tool. The Groove SDK neither has any API's or code to do the same nor I get code from google search.

I am looking for directions to go ahead.

Thanks and regards,
Rishi

CREATED ISSUE: How do I connect my Issue Tracker to automatically update a calendar in Groove?

mf0978 — Tue, 06 May 2008 17:46:23 GMT

I want to be able to create a field in the issue tracker that will automatically link it to a calendar and have it update the calendar with that date and what the appointment or due date is without doing anything other than entering in a date in the issue tracker? I am having a hard time finding this information. Any info would be greatly appreciated. Thank you.

CREATED ISSUE: Exception throw : Unable to find HKLM_GrooveRegKey

Blu3dr4g0n — Fri, 01 Feb 2008 21:54:11 GMT

CREATED ISSUE: Common interface for Forms Tool

pcibraro — Fri, 23 Nov 2007 20:33:07 GMT

The namespaces GrooveWebServicesV12Helpers.Forms and GrooveWebServicesV12Helpers.Forms2 contain classes with similar interfaces, for instance, RecordDataSet. It would be great to have a interface for the members and methods that both classes have in common. In that way, there is not need to detect or cast classes all the time depending on the namespace.

For example, IRecordDataSet (This is just an example, there are other classes where the same thing can be done), which can contains the following members:

XmlNode[] Data;
XmlNode[] Schema;
string SchemaID;
DataSet ToDataSet();

CLOSED ISSUE: Bad Forms2Tool Event namespace

BobNovas — Fri, 10 Aug 2007 12:22:24 GMT

There's a bug in Forms2Tool.cs in IncrementFormsToolSubscriptionCount in the call to AddEventListener. The code uses the wrong event class. The call to AddEventListener should be:

m_FormsSubscriptionID = GrooveWebServicesV12Helpers.EventManager.AddEventListener
(
m_Context,
this.IdentityURL,
GrooveWebServicesV12Helpers.Shared.GROOVE_WEB_SERVICES_FORMS2_EVENT_CLASS,
this.Data,
GrooveWebServicesV12Helpers.EventManager.s_EventURI,
this
);

I'll fix this in the next release.

COMMENTED ISSUE: Bad Forms2Tool Event namespace

psuthar — Tue, 05 Jun 2007 15:36:40 GMT

There's a bug in Forms2Tool.cs in IncrementFormsToolSubscriptionCount in the call to AddEventListener. The code uses the wrong event class. The call to AddEventListener should be: m_FormsSubscriptionID = GrooveWebServicesV12Helpers.EventManager.AddEventListener ( m_Context, this.IdentityURL, GrooveWebServicesV12Helpers.Shared.GROOVE_WEB_SERVICES_FORMS2_EVENT_CLASS, this.Data, GrooveWebServicesV12Helpers.EventManager.s_EventURI, this ); I'll fix this in the next release. Comments: ** Comment from web user: psuthar **

Bumping impact to high as this issue can cause data loss (i.e. missing events).

CREATED ISSUE: Bad Forms2Tool Event namespace

BobNovas — Fri, 11 May 2007 15:15:51 GMT

There's a bug in Forms2Tool.cs in IncrementFormsToolSubscriptionCount in the call to AddEventListener. The code uses the wrong event class. The call to AddEventListener should be: m_FormsSubscriptionID = GrooveWebServicesV12Helpers.EventManager.AddEventListener ( m_Context, this.IdentityURL, GrooveWebServicesV12Helpers.Shared.GROOVE_WEB_SERVICES_FORMS2_EVENT_CLASS, this.Data, GrooveWebServicesV12Helpers.EventManager.s_EventURI, this ); I'll fix this in the next release.

CLOSED ISSUE: FormFileAttachment(2) throws if no content

BobNovas — Fri, 20 Apr 2007 23:56:50 GMT

if you read records without setting the optional argument i_IncludeFileAttachmentContent true, like this: GrooveWebServicesV12Helpers.Forms.RecordDataSet records = formsTool.GetFormRecords(form.URI, true); and then try to getFormFileAttachments, like this: GrooveWebServicesV12Helpers.Forms.FormFileAttachment[] attachments = GrooveWebServicesV12Helpers.Forms.FormFileAttachment.GetFormFileAttachments(row); Then, FormFileAttachment.cs will throw at line 54 - System.Data.DataRow ChildContentsDataRow = m_FileAttachmentDataRow.GetChildRows("FileAttachment_Contents")[0]; Probably should check to see if there are any child rows before dereferencing them.

CLOSED ISSUE: File.Update fails with SOAP exception

BobNovas — Fri, 20 Apr 2007 23:55:29 GMT

Fix for File Update – in FilesTool\FileFolderBase.cs private void int_Update(System.Byte[] i_FileContents) { // Get initialized reference to web service GrooveFilesWebService.GrooveFilesBase64 FilesWebService = GrooveWebServicesV12Helpers.Files.FilesTool.CreateInitializedFilesWebService ( m_IdentityURL, this.URI, m_Context );

CLOSED ISSUE: EventManagerThreadProc deletes wrong number of Events

BobNovas — Fri, 20 Apr 2007 23:55:27 GMT

EventManagerThreadProc (EMTP) calls Event.ReadExtended passing false for the Delete Events argument. Then it delivers the events it read to the application. Finally, it calls Event.Delete to delete the events it read from Groove's event queue. It does this so that if the application should crash trying to handle an event (or the box be powered off) the event will still be persisted on Groove's event queue. The problem was that EMTP passes ExtendedEventData.EventQueueSummary.Sequence to Event.Delete, but needs to pass ExtendedEventData.EventQueueSummary.Sequence - 1 to correctly delete the events it's read. You can prove this by comparing the count of events deleted returned by Event.Delete to the count of events read by Event.ExtendedRead. With the original code, these two values occasionally compare inequal - especially if the application processing an event invokes a web service that will generate another event - this event gets lost.

CLOSED ISSUE: Problem in locales where "," is the decimal indicator

BobNovas — Fri, 20 Apr 2007 23:55:25 GMT

Exception thrown in Context.cs file at line 193 when a "," is the decimal separator (e.g., locale = france).

CLOSED ISSUE: ContactDirectory.cs throws exception

BobNovas — Fri, 20 Apr 2007 23:55:24 GMT

If, as can happen, a ContactDirectory search returns no matches, in Groove 2007, the ContactDirectory.cs code throws an null reference exception. An if clause testing for null saves the day. fragment from ContactDirectory.cs: case GrooveWebServicesV12Helpers.Shared.GROOVE_CONTACT_DIRECTORY_SEARCH_RESULTS_EVENT_TYPE: { System.Collections.ArrayList ContactSummaryArrayList = new System.Collections.ArrayList(); GrooveEventsWebService.GrooveContactSearchResultsEventData ContactSearchResultsEventData = (GrooveEventsWebService.GrooveContactSearchResultsEventData)i_Event.EventData; if (ContactSearchResultsEventData.ContactSummaryList != null) { // Populate array list of ContactSummaries foreach (GrooveEventsWebService.ContactSummary ContactSummary in ContactSearchResultsEventData.ContactSummaryList) { GrooveWebServicesV12Helpers.ContactSummary NewContactSummary = new GrooveWebServicesV12Helpers.ContactSummary(ContactSummary); ContactSummaryArrayList.Add(NewContactSummary); } } // Create array from array list if (ContactSummaryArrayList.Count > 0) m_SearchedContactSummaries = (GrooveWebServicesV12Helpers.ContactSummary[])ContactSummaryArrayList.ToArray(typeof(GrooveWebServicesV12Helpers.ContactSummary)); break; }

CLOSED ISSUE: member.Enter/ExitSpace(), .Enter/ExitTool()

BobNovas — Fri, 20 Apr 2007 23:55:23 GMT

The target uri really needs to be the space relative member's uri instead of the member's uri. And the semanics are wrong (you're calling these methods on some member, but the action applies to you, and only if you're entering/exiting the space/tool). Arguably, these methods are misplaced in the Member class. Enter/ExitSpace perhaps belongs to the Space class, and Enter/ExitTool to the Tool class. You can address this by only invoking the methods at the right time and ignoring the fact that the semantics are questionable. However, to address the first issue, which throws an exception, the code needs to look more like this (for all 4 methods)... ///

/// Signal to other workspace members that the current user has entered the workspace. ///

public void EnterSpace() { string targetURI = this.Space.MembersURI; // Get initialized reference to web service GrooveMembersWebService.GrooveMembers MembersWebService = this.GetInitializedMembersWebService(targetURI); System.DateTime BeginDateTime = System.DateTime.Now; // Ask service to enter space MembersWebService.EnterSpace(); if (GrooveWebServicesV12Helpers.Context.TraceEnabled) { System.TimeSpan TimeSpan = System.DateTime.Now.Subtract(BeginDateTime); System.Diagnostics.Debug.WriteLine("MembersWebService::EnterSpace, " + TimeSpan.TotalMilliseconds + " ms"); } }

CLOSED ISSUE: Helpers Identity.CreateSpace operation fails unless you specify i_Type=""

BobNovas — Fri, 20 Apr 2007 23:55:22 GMT

If you don't specify i_Type (the 3rd parameter to the method), but rather call one of the other overloads of that method, they pass GrooveWebServicesV12Helpers.Shared.GROOVE_GENERIC_CREATE_SPACE_TEMPLATE as the i_Type. But,... the Space web service Create operation says, about the i_Type parameter, which it calls the CSTURI: CSTURI xs:anyURI Specifies the type of workspace to be created. Must have an empty string value (""). All other values are reserved for future use. So calling any Identity.CreateSpace method other than the 3rd form, or even calling the 3rd form and passing anything but "" as the 3rd argument causes an exception from the web service. Need to fix the helpers to pass "" in the overloaded forms of the method.

CLOSED ISSUE: Checking Source URI validity

BobNovas — Fri, 20 Apr 2007 23:55:21 GMT

At least one of the parameters to the Subscription Service's Create operation, which creates a durable Subscription, has a very specific and critical form. And, if you do not get the form correct, the service will silently accept the incorrect form but not function properly. In my case, instead of using the Identity2.Spaces property, which contains the correct form of the Source URI, I formed a Source URI by combining two strings- to form a Source URI that looked like this: /GWS/Groove/2.0/Spaces/grooveIdentity://7746ttz47vtp5r3gha7hu5jv5wanax55@ Now, a Source URI in the correct form looks like this: /GWS/Groove/2.0/Spaces/grooveIdentity/7746ttz47vtp5r3gha7hu5jv5wanax55@ This is a subtle but critical difference. When given a Source URI in the incorrect form to Create a Subscription, Groove accepts the Source URI in the incorrect form without expressing any error. But, subsequently, a subscription works until Groove is shutdown, and then never works (i.e., never produces an event) again. Incidentally, another symptom of this problem is that the EventSource in the ReadExtendedResponse SOAP looks like this: grooveIdentity::// Instead of what it should look like, which is more like this: grooveIdentity://7746ttz47vtp5r3gha7hu5jv5wanax55@ Paresh had a great idea - to put some code to check the form of the SourceURI into the helpers at the "choke point" (where the subscription Create operation is invoked) and to error out invalid forms of Source URI there. There are other ways to screw up the SourceURI. For example, if you provide a valid form of the argument but an invalid value for the actual identity string, I think the same ill behavior results. ...Bob