{"id":1170,"date":"2011-03-05T15:08:38","date_gmt":"2011-03-05T13:08:38","guid":{"rendered":"https:\/\/alax.info\/blog\/?p=1170"},"modified":"2011-03-05T15:11:19","modified_gmt":"2011-03-05T13:11:19","slug":"build-incrementer-add-in-for-visual-studio-latest-visual-studio-versions","status":"publish","type":"post","link":"https:\/\/alax.info\/blog\/1170","title":{"rendered":"Build Incrementer Add-In for Visual Studio: Latest Visual Studio Versions"},"content":{"rendered":"

If you share concept (as I do) that every build should have a unique file version stamp in it, for a simple purpose \u00e2\u20ac\u201c at least \u00e2\u20ac\u201c to distinguish between different version of the same binary, then a helpful tool of automatic incrementing fourth number in FILEVERSION’s file version is something you cannot live without. After going through several fixes and updates, it is finally here available for download.<\/p>\n

The last issue was in particular that projects that are in solution’s folder are not found by the add-in with Visual Studio<\/a> 2008. Why? OnBuildProjConfigBegin<\/a> event provides you with a unique project name string in Project argument, but it appears that it is only good enough as a quick lookup argument with Visual Studio 2010.<\/p>\n

\/\/ EnvDTE::_dispBuildEvents<\/span>\r\n    STDMETHOD(<\/span>OnBuildBegin)<\/span>(<\/span>_EnvDTE_vsBuildScope Scope,<\/span> _EnvDTE_vsBuildAction Action)<\/span> throw<\/span>(<\/span>)<\/span>\r\n    STDMETHOD(<\/span>OnBuildDone)<\/span>(<\/span>_EnvDTE_vsBuildScope Scope,<\/span> _EnvDTE_vsBuildAction Action)<\/span> throw<\/span>(<\/span>)<\/span>\r\n    STDMETHOD(<\/span>OnBuildProjConfigBegin)<\/span>(<\/span>BSTR Project<\/span><\/strong>,<\/span> BSTR ProjectConfig,<\/span> BSTR Platform,<\/span> BSTR SolutionConfig)<\/span> throw<\/span>(<\/span>)<\/span>\r\n    {<\/span>\r\n        _Z4(<\/span>atlTraceCOM,<\/span> 4<\/span>,<\/span> _T(<\/span>\"<\/span>Project <\/span>\\\"<\/span>%s<\/span>\\\"<\/span>, ProjectConfig <\/span>\\\"<\/span>%s<\/span>\\\"<\/span>, Platform <\/span>\\\"<\/span>%s<\/span>\\\"<\/span>, SolutionConfig <\/span>\\\"<\/span>%s<\/span>\\\"<\/span>\\n<\/span>\"<\/span>)<\/span>,<\/span> CString<\/span>(<\/span>Project)<\/span>,<\/span> CString<\/span>(<\/span>ProjectConfig)<\/span>,<\/span> CString<\/span>(<\/span>Platform)<\/span>,<\/span> CString<\/span>(<\/span>SolutionConfig)<\/span>)<\/span>;<\/span>\r\n        _ATLTRY\r\n        {<\/span>\r\n            \/\/ NOTE: const CString& cast forces compiler to process statement as variable definition rather than function forward declaration<\/span>\r\n            CProjectConfiguration ProjectConfiguration(<\/span>(<\/span>const<\/span> CString<\/span>&<\/span>)<\/span> CString<\/span>(<\/span>Project)<\/span>,<\/span> CString<\/span>(<\/span>ProjectConfig)<\/span>,<\/span> CString<\/span>(<\/span>Platform)<\/span>,<\/span> CString<\/span>(<\/span>SolutionConfig)<\/span>)<\/span>;<\/span>\r\n            CRoCriticalSectionLock DataLock(<\/span>m_DataCriticalSection)<\/span>;<\/span>\r\n            \/\/ NOTE: Check the project on the first run only (to skip multiple increments in batch build mode)<\/span>\r\n            if<\/span>(<\/span>!<\/span>Project |<\/span>|<\/span> m_VersionMap.<\/span>Lookup(<\/span>ProjectConfiguration)<\/span>)<\/span>\r\n                return<\/span> S_FALSE;<\/span>\r\n            _Z3(<\/span>atlTraceGeneral,<\/span> 3<\/span>,<\/span> _T(<\/span>\"<\/span>Checking project <\/span>\\\"<\/span>%s<\/span>\\\"<\/span>...<\/span>\\n<\/span>\"<\/span>)<\/span>,<\/span> CString<\/span>(<\/span>Project)<\/span>)<\/span>;<\/span>\r\n            \/\/ Checking the project is of C++ kind<\/span>\r\n            CComPtr<<\/span>EnvDTE::<\/span>Project><\/span> pProject =<\/span> GetProject(<\/span>CComVariant(<\/span>Project<\/span><\/strong>)<\/span>)<\/span>;<\/span>\r\n            _A(<\/span>pProject)<\/span>;<\/span>\r\n            .<\/span>.<\/span>.<\/span><\/pre>\n
Eventually, the add-in is here. It’s job is to go to .RC file and increment file version each time you build the binary. It reports the action into build output window:<\/p>\n
\"\"<\/a><\/p>\n
To install the add-in:<\/p>\n
When the project is in a folder, Projects::Item<\/a> can just fail if you are looking up for the element interface. In which case, you have to walk the collection taking into account SubProjects<\/a> and additionally look there yourself. Visual Studio 2010 is one step smarter and gives the thing to you right from the start.<\/p>\n