Re: source code verification
- From: Julián Rodríguez Bajo <julian.rodriguez@xxxxxxxxxx>
- Date: Fri, 27 Jul 2007 10:03:08 +0200
David Ching escribió:
"Julián Rodríguez Bajo" <julian.rodriguez@xxxxxxxxxx> wrote in message news:u8tn8u2zHHA.5380@xxxxxxxxxxxxxxxxxxxxxxxHi Dani.
In my company, we use a SCC string for every source file used, like:
static LPCTSTR VSSID = _T("$Header:$")
This way, every time you check in the source file, VSS (or any other SCC system that supports keyword expansion) expands "$Header:$" to something like "$Header: /Sockets/Test/TestApp.cpp 4 18/02/07 user $", This string is included in the final executable, so later you can check (whith ident, strings or any string-find utility) what source files were used to build an exe, dll or ocx. Output is something like:
I would say this is a great diagnostics for development, but due to issues of different tools and SDK's that could be used in the build process, it still isn't sufficient to guarantee 100% that the .exe you have is identical to the one that was deployed.
-- David
Of course you are right, David. But in a small company with a development team of about 10 programmers as is my case, it is really easy to force everybody use the same tools and SDKs. Very different situation in a bigger company with a lot of development teams.
At least, you allways have valuable data knowing with what version of one particular file is one executable built, since you can check if the problem your customer is reporting was corrected in a posterior version of the same file.
It is not a binary equivalence system, but a "do we solve this issue in a later version" helper.
Regards.
.
- References:
- source code verification
- From: dani
- Re: source code verification
- From: Julián Rodríguez Bajo
- Re: source code verification
- From: David Ching
- source code verification
- Prev by Date: Re: Want Input boxes to accept unicode strings on Standard Window
- Next by Date: Re: Want Input boxes to accept unicode strings on Standard Window
- Previous by thread: Re: source code verification
- Next by thread: Beware platform SDK with VS2005
- Index(es):
Relevant Pages
|