Batch tagging

[jporkka]

I'm trying to setup a automated system to sync my projects from source control and retag.

I'm using
    workspace_open( ....
    _workspace_update_files_retag
    workspace_close

This tends to wipe out my *.vpwhist file though.

How can I preserve that file?

[hs2]

There is the 'vsmktags' tool, which is quite helpful for use cases like yours. Maybe you should give it try.
HS2

[rdroaten]

I've been trying to do the same thing (auto/batch update of tagfiles).  Can vsmktags add new source files to a tagfile?

[hs2]

Can vsmktags add new source files to a tagfile?

Should work if your existing workspace::project(s) uses wildcards to specify the project files.
HS2

[jporkka]

Do wildcards really work?

[hs2]

Well, I was just guessing b/c I would've done it like that
But you're right - I should only post verified things.
Tested it with a small example workspace containing 1 *.cpp wildcard project containing the file 'cpp.cpp' (no subdirs).
1) run vsmktags -> listvtg (w/o invoking SE)
2) added a 2nd 'cpp2.cpp' file to the directory
3) run vsmktags -> listvtg (w/o invoking SE) again
Seems to work as expected,
HS2

[jporkka]

Confirmed.
But I also found that it only works if the project is in the directory with the source files.
So, I cannot have
   C:\Src\...
   C:\SlickProjectFiles\...
and get it to work.
No errors or anything, it just doesn't ever find anything.
 

[evanratt]

I use wildcards with the project in a completely separate directory. Then, I just need to "Refresh" the project to find and tag all newly added files, as well as retag modified files.

Make sure your project Working Directory is set to the directory with the source files? I think it uses that as the base for the wildcard search...

[hs2]

Unfortunately I'm not sure about the latest status, but it was required to keep the vpj in the topdir of the assoc. source tree. AFAIK b/c project working dir was/is used to build the file list relativ to this dir. vpw can be anywhere. Could be useful to specify different dir-prefixed wildcards (e.g. rel. to the project working dir)...
HS2

[evanratt]

Nope, I have all my Slickedit project files in a completely separate directory, but on the same drive as my source tree. Then, for my wildcards, I specify the full path. So, my working directory is "\<project_name>\src", and my project files are:
"\<project_name>\src\*.cpp"
"\<project_name>\src\*.h"
etc.

Works a treat for me, in my setup, at least...

[jporkka]

Well, heck, this actually works 

What does "Apply custom view filters (flat file list) " mean ?

What is the downside of this?
Grrrr...this seems like the feature I've wanted for a long time - seems like it should make managing projects under source control a whole heck of a lot easier.

Wierd that the wildcard can only be a single pattern, making adding *.cpp,*.h, *.etc, tiresome.

[chrisant]

This may be useful.