>>> You should use SubWCRev the same way TSVN does: use a template file
>>> which then you can create the file you use in VS.NET from.
>>> We had SubWCRev as a pre-build step in the TSVN build process too. But I
>>> removed it from there and put it in the batch file because I sometimes
>>> don't want it to run everytime I build the project.
>> So you want me to have duplicate copies of every source file in my
>> project that I want SubWCRev to process? One that's the template that
>> I'll edit, and one which will get compiled.. I'd have to open the
>> template also in VS.Net in order to edit it, but I can't have in
>> included in the solution because VS.Net would try to compile it and it
>> would clash with the "destination" source file.
> Sorry, but no.
> - VS.NET does _not_ compile files just because they're in your project.
> Give it another extension (like TSVN does with the version.h file, the
> template is called version.in).
I'd loose completion and syntax highlighting.
Possibly other stuff.
And it's yeach ugly and needs a lot of setting up.
> - If you use the revision number in more than one file, you're not using
> it right. Every programming language knows includes. So have *one* file
> with the revision number in it, and include that wherever you need it.
I have multiple projects in one solution.
>> - I'd loose synchronization with the other developers, because the
>> template file is not in the solution file but in my "personal user
>> preferences of what files should be open in the editor", eg. the .suo
> You can easily put it in the project.
The amount of effort to use SubWCRev just keeps going up and up and up...
I'm not saying this can't be done, I'm just saying it could be done in
a much easier-to-use, shallower-learning-curve, less-complicated,
overall prettier way.
>> - I'd have to answer to them why VS.Net complains about missing files
>> when they check out the source code and open the project (it's because
>> you have to run SubWCRev to make the files exist).
> If you add SubWCRev to the pre-build step, then VS.NET won't complain
> about missing files.
No.. Chicken/egg, the pre-build wont run before you build, and you
can't build without opening the freshly-checked-out project first.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Apr 9 22:52:02 2005