product information in converted VO application

leighproman · Post by **leighproman** » Wed Jun 12, 2019 9:27 am

How do you add product information (product name, company name etc) to a converted (xported) VO application in VS2017?
In VO28 we have a VERSIONINFO resource but this doesn't get carried over by VOXporter.
Thanks
Leigh

lumberjack · Post by **lumberjack** » Wed Jun 12, 2019 9:42 am

leighproman wrote:How do you add product information (product name, company name etc) to a converted (xported) VO application in VS2017?
In VO28 we have a VERSIONINFO resource but this doesn't get carried over by VOXporter.

Add an AssemblyInfo.prg to your application:

Code: Select all

#using System.Reflection
#using System.Runtime.InteropServices

[assembly: AssemblyTitleAttribute( "" )]
[assembly: AssemblyDescriptionAttribute( "" )]
[assembly: AssemblyConfigurationAttribute( "" )]
[assembly: AssemblyCompanyAttribute( "" )]
[assembly: AssemblyProductAttribute( "" )]
[assembly: AssemblyCopyrightAttribute( "Copyright © " )]
[assembly: AssemblyTrademarkAttribute( "" )]
[assembly: AssemblyCultureAttribute( "" )]

[assembly: AssemblyVersionAttribute( "1.0.*" )]
[assembly: AssemblyFileVersionAttribute( "1.0.*" )]

wriedmann · Post by **wriedmann** » Wed Jun 12, 2019 9:57 am

Hi Leigh,

unfortunately I don't know how to add this information to a Visual Studio project, but of course also a .NET application can contain a VersionInfo ressource (and in fact I'm using that one in all of my X# applications, both converted from VO and natively written in X#).

Wolfgang

wriedmann · Post by **wriedmann** » Wed Jun 12, 2019 9:59 am

Hi Johan,

unfortunately the AssemblyInfo.prg does not works like the VersionsInfo ressource, as the Windows Explorer does not displays this information, and the VersionInfo API does not shows these informations either.
Wolfgang

Chris · Post by **Chris** » Wed Jun 12, 2019 11:43 am

Hi Leigh,

Are you sure that VERSIONINFO resources do not get ported by VOXporter? They should be..

leighproman · Post by **leighproman** » Wed Jun 12, 2019 12:00 pm

Where should it end up?
In VO I have RESOURCE VS_VERSION_INFO VERSIONINFO etc in my Start module but no obvious sign of it or its data after VOXport-ing.

Leigh

Chris · Post by **Chris** » Wed Jun 12, 2019 1:35 pm

Hi Leigh,

Hmmm, you are right, I just tried and it indeed does not work. Very strange, no obvious reason why it shouldn't.

Will try to fix this for the next build (which should be out in a couple days if nothing serious happens), but in the meantime you can also add it yourself, just Add a new item in your project, select the Native Resource template and then copy/paste the contents from the VO resource to the .rc file that gets added, excluding the "RESOURCE" word. That should do the trick.

Edit: actually there's specific code in VOXporter to disallow porting this type of resource! Sorry about that, forgot about it, was done because it is tricky porting some of the accompanying defines necessary. Looking into it now.

leighproman · Post by **leighproman** » Wed Jun 12, 2019 2:15 pm

Thanks Chris - that compiles ok but I have the same issue as Wolfgang - Properties of the EXE in Windows Explorer doesn't show the information as it does from the VO compiled version.

Edit - or rather it compiles when I remove the defines, which is presumably why it doesn't work!

Leigh

wriedmann · Post by **wriedmann** » Wed Jun 12, 2019 2:21 pm

Hi Leigh,

if you compile the ressource correctly into the exe, the version information shows up also in the Windows Explorer:

: VersionInfo.png (26.34 KiB) Viewed 716 times

But I'm using XIDE and I don't know how to add that to a VS project.

: alpilog_xide.png (221.86 KiB) Viewed 716 times

Wolfgang

Chris · Post by **Chris** » Wed Jun 12, 2019 3:05 pm

Wolfgang, it's similar in VS. Leigh, can you please zip and attach your version .rc file so we can have a look? You may want to modify "sensitive" information first.

Main menu