|
Thank you for using TamTam SVN SCC.
Below is a list of recent product updates/enhancements. If you
should encounter an issue with TamTam please let me know and
I'll be sure to address it as quickly as possible.
If you're already a registered user you can upgrade to the
latest release by downloading and installing the latest product
install.
CLICK HERE TO DOWNLOAD AND
INSTALL THE LATEST UPDATE
v1.2.4 Release, July 2008
|
|
|
 |
- Corrected issue where moving controlled files
within a project failed to invoke the subversion move/rename
command.
- While adding items to the repository Subversion
reports an error indicating that the repository UUID's do not match.
This issue appears when using Subversion v1.5.
v1.2.3 Release, June 2008
|
|
|
|
|
- Corrected issue which caused the subversion
client to crash when adding a new solution to the repository and
repository path ends with a "/". The svn error indicates "Assertion
failed: is_canonical(path->data, path->len)..."
v1.2.2 Release, June 2008
|
|
|
|
|
- Corrected issue where directories that contained
"." in them would be treated as files.
v1.2.1 Release, May 2008
|
|
|
|
|
- Added support for the latest 1.4.6 release of
Subversion
- Corrected issues with adding subfolders to the
repository
- Corrected issues when checking of a folder
exists in the repository
- Corrected issue where files containing ".vsscc"
in the file extension failed to be checked into the repository
v1.1.27 Release, March 2008
|
|
|
|
|
- Enable true atomic commits for all files within
a solution/project
- Help documentation is missing sections
v1.1.26 Release, March 2008
|
|
|
|
|
- Correct bug which prevented new folders from
being created and renamed in visual studio.
v1.1.25 Release, February 2008
|
|
|
|
|
- Corrected a user reported issue were TamTam
would appear to lock up when performing certain source control
actions.
- Corrected the build versioning to report the
correct/proper product version
v1.1.24 Release
|
|
|
|
|
- Fixed a bug where an internal hidden window used
by TamTam for thread communication was not being destroyed causing a
memory leak when then plugin is unloaded.
|
