How is this set in visual c++. I assumed it was in the AssemblyInfo.cpp
file, but the changes are never picked up and
Application::ProductVersion keeps coming back empty.
Help is appreciated.
Hi Mike,
> How is this set in visual c++. I assumed it was in the AssemblyInfo.cpp
> file, but the changes are never picked up and
> Application::ProductVersion keeps coming back empty.
Unfortunately, Application::ProductVersion never returns the correct
information (or rather, any information at all) for an MC++ application.
It's the same case as what I describe in detail here:
http://groups-beta.google.com/group/microsoft.public.dotnet.languages.vc/msg/ec9
ccbab4c9798c7?hl=en&
the good news is that this is fixed in VS2005.

Signature
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
Mike E - 15 Jul 2005 03:29 GMT
So how do you set all the version stuff, the old MFC way with
version_info?
Tomas Restrepo (MVP) - 15 Jul 2005 04:18 GMT
Hi Mike,
> So how do you set all the version stuff, the old MFC way with
> version_info?
Not necessarily. You can *still* use the information encoded in the assembly
attributes if you want, you just have to dig it out yourself using
System::Reflection; the corresponding properties in the Application class
are just "shortcuts" to that info.

Signature
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
Mike E - 15 Jul 2005 04:23 GMT
I was talking about the right click, properties, version tab stuff.
Thanks,
Mike
Tomas Restrepo (MVP) - 15 Jul 2005 04:47 GMT
Hi Mike,
>I was talking about the right click, properties, version tab stuff.
Ahh, that, sorry :)
Yes, you get those by using the usual unmanaged VERSION resource on the
exe/dll.

Signature
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
Mike E - 15 Jul 2005 21:05 GMT
gratzi!
> Hi Mike,
>
[quoted text clipped - 4 lines]
> Yes, you get those by using the usual unmanaged VERSION resource on the
> exe/dll.