18 July 2007 -- IntelliGantt Projects from Existing SharePoint and Groove Task Lists

Download IntelliGantt Standard (Build 3.0.0.203): Standard

Projects can now be created from existing SharePoint and Groove task lists (thank you Troy).
A new property ('Add Tasks Created in SharePoint/Groove') is available that tells IntelliGantt and MS Add-In to recognize tasks created in SharePoint/Groove (thank you Jeff).
IntelliGantt recognizes WSS 3.0 sites and takes advantage of Assigned To fields that accept multiple values (thank you Greg).
MindManager 7.0 Support.

IntelliGantt Add-In for MS Project is now its own MSI package.
Invitation files can now be copied to folders of your choice. In the project window, click the 'File' menu and then 'Save Invite File To...'. This will make it easier for non-Outlook users to send invite files to everyone in a project (thank you Jane).
WBS codes now have zeros preceding their values to make sorting in SharePoint easier (thank you Ken).
Improved feedback during Publish and Sychronize gives you the actual response of the back end server.
Groove synchronization now changes only the tasks that have either actually updated or need their schedule enforced (thank you Marsha).

Sharing to existing sites had a problem when resolving Groups that caused the entire share operation to fail. FIXED! (thank you Anne).
IntelliGantt recognizes the TD Task List, even when you rename it (thank you Fabrice).
SharePoint workspaces with 'bad' characters in their names weren't being handled correctly which broke the 'Go To Site' URL.
SharePoint servers outside a users timezone had a mismatched timestamp after the initial share.
Project names with quotes, or projects located in file paths with quotes, are now handled correctly (thank you Scott).
WBS codes were not updating correctly in SharePoint and Groove (if a user changed the order of tasks, IntelliGantt wasn't catching the change and updating the WBS field-- thank you Tim)
An intermittant bug during thread cleanup would sometimes abort Synchronization-- FIXED.

The IntelliGantt Add-In for MS Project 2007 on Windows Vista has an issue when shutting down MS Project. The error is totally benign except for a poor user experience. It appears that .NET 1.1 Add-Ins build from the Visual Studio 2003 Add-In template all exhibit this behavior.

Create SharePoint Workspaces with custom templates. (screencast) (Installation Info)
Create Groove Workspaces with custom templates. (screencast)
Unlocked Groove Forms Task List.
'Updated' flag now gives detailed list of what has changed when you mouse over the marker (far left column)
'Show Updated Tasks' filter added to basic filter list.

Windows Vista Support!
WBS codes are now added to IntelliGantt and SharePoint task lists to help identify tasks among MS Project, IntelliGantt and Sharepoint.
No longer need to close IntelliGantt Project Windows for auto-synchronization-- they can be open and you can now see synchronizations happen live.
When using the MS Project Add-In, the task ordinals in the Groove Task List now correspond to MS Project's view instead of IntelliGantt's view.
Speed enhancement during synchronization: only one lock/unlock cycle required for sync.
Getting Started document updated.

Email address matches between MS Project and SharePoint were case sensitive resulting in members not being match correctly.
When running the IntelliGantt Add-In for MS Project using MS Project 2007 and .NET 2.0, Groove task list updates were not synchronizing correctly
The 'Use IntelliGantt Resources' flag in the options dialog required IntelliGantt to be restarted to take effect. No restart required now.
IntelliGantt was not recognizing task lists in SharePoint workspaces other than Document Workspaces. IntelliGantt now uses List web service for all lists.
Local Workgroup sharing was not handling spaces within a share path correctly.
International number formats with IntelliGantt MS Project Add-In and SharePoint were not handled properly, but are correct now.
When creating a linked project with Microsoft Project and Mindjet MindManager documents, an apostrophe anywhere in the file path or name meant failure.