[quoted text, click to view] > I spent a while trying to work out how to do an automated get from
> SourceSafe using Visual Studio but I gave up in the end and just did a get
> of the whole SourceSafe tree.
>
yes, tried that too, but does not work too great for web apps, because
devenv creates a virtual dir for them automatically, VSS does not do
that...
[quoted text, click to view] > It certainly should be possible but Microsoft doesn't seem that interested
> in supporting it VS 2003 (it seems odd to have a source control system that
> makes it so hard to do automated builds).
Looks like Source Safe is not really a member of the VS family, I have
the feeling MS bought VSS and does not know how to integrate it in
DEVENV... It's been ages since they upped the version on VSS (still
6.0 after so many years)
[quoted text, click to view] >
> Other people have suggested that it should be possible to get a project from
> source control using the automation interface. I believe Microsoft has a
> utility called "BuildIt" or "MSBuild" that does this and there is source
> code available but it only works for C#. I didn't research this possibility
> that much as I was getting fed up with looking for a solution by that point.
> It might be possible to get one of them and extend them to support C++ and
> make it all work.
Yeah, I'm also looking into Buildit and NANT, but I thought I could
get this to work in 10 minutes, the other solutions need some getting
used to and some set-up time. I wrote my CMD-buildscript in less than
30 minutes, just this last step with source-safe hits me harder than I
expected.
BTW: my example won't work since it does not know the macro's DTE.
Something like /COMMAND "File.GetLatest" works, but it does not always
select the solution, it just gets wherever the project-selector is on.
I'm thinking of calling a macro from the command-line, but for just 2