Re: VS_VERSION_INFO static ctrl

From:

"JCO" <someone@somewhere.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Mon, 14 Jun 2010 18:54:46 -0500

Message-ID:

<Oigi3zBDLHA.2012@TK2MSFTNGP02.phx.gbl>

I think I'm missing something but I'm interested in this topic.
If you have your version defined in a header file, then you can display it
in the dialog, however, if you did a "property" on the exe file, has it
really changed? If so, then I got lost somewhere in this thread.

Also;
I was under the impression that you can set something in VS that allowed the
version to change each time you do a build. I don't remember how to do this
but I always thought this was possible. Now it may only change the Build
number and not anything else, however, this is a good feature. Is this
still possible, if so .... how do you do it?

Thanks

"Giovanni Dicanio" <giovanniDOTdicanio@REMOVEMEgmail.com> wrote in message
news:eg3hiCyCLHA.2012@TK2MSFTNGP02.phx.gbl...

On 13/06/2010 15:47, RB wrote:

void CFileHandlingApp::OnAppAbout()
{
   CAboutDlg aboutDlg;
   CString s;
   s.Format( _T(" version %d.%d.%d.%d"), VERMAJ, VERMIN, VERFIX,
BUILDNUMBER );
   aboutDlg.m_CtrlStaticVer.SetWindowText(s); //gets a Debug Assertion
Failed
   aboutDlg.DoModal();

You may want to add a method to your CAboutDlg class like
SetVersionString(LPCTSTR pszVersion) and a data member of type CString
(e.g. CString m_strVersion).
This new method should set the version string, storing it into the proper
data member.

Then, CAboutDlg::OnInitDialog would get this string and .SetWindowText()
it in the proper static control.

e.g.:

class CAboutDlg
{
   ...
public:
   void SetVersionString(LPCTSTR pszVersion)
   {
       m_strVersion = pszVersion;
   }

...

private:
   CString m_strVersion;
};

In CAboudDlg::OnInitDialog() do:

  m_CtrlStaticVer.SetWindowText(m_strVersion);

Giovanni