View previous topic :: View next topic |
Author |
Message |
Emanuele
Joined: 21 Oct 2009 Posts: 78 Location: Bologna (Italy)
|
Posted: Tue Nov 15, 2011 9:56 pm Post subject: Assembly Information |
|
|
In Visual Studio projects, both executables or dll, it is possible to define some assembly information (like company name, product version, copyright...), which will be visible in the compiled file properties. This can be easily obtained by setting appropriate values in the project properties page.
Is there a way to do the same thing for FTN95 projects (.NET mode), by setting compiler options or by coding? |
|
Back to top |
|
 |
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8210 Location: Salford, UK
|
Posted: Wed Nov 16, 2011 9:10 am Post subject: |
|
|
You can set the version number by using /ver on the dbk_link command line (or via the linker settings in a project) but, as far as I know, other values are automatically provided (or not) by the linker. |
|
Back to top |
|
 |
Emanuele
Joined: 21 Oct 2009 Posts: 78 Location: Bologna (Italy)
|
Posted: Wed Nov 16, 2011 11:01 am Post subject: |
|
|
Thank you for the quick reply. That's ok for the version number, but other values remain blank. You said that the linker automatically provides or not the values of "company", "copyright" and so on, but depending on what? Where and when they should be set? |
|
Back to top |
|
 |
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8210 Location: Salford, UK
|
Posted: Wed Nov 16, 2011 4:17 pm Post subject: |
|
|
What I meant was that the linker adds this information for some fields but leaves others blank. I don't know of a way to fill in the blanks except for us to add extra options to the linker for you. |
|
Back to top |
|
 |
Emanuele
Joined: 21 Oct 2009 Posts: 78 Location: Bologna (Italy)
|
Posted: Wed Nov 16, 2011 7:40 pm Post subject: |
|
|
Wow, it would be grate! In fact it is not a vital point, but it maight be useful not only for me...
Thank you again. |
|
Back to top |
|
 |
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8210 Location: Salford, UK
|
Posted: Wed Nov 16, 2011 8:14 pm Post subject: |
|
|
Which are the most important? Let's suppose I can add two more fields. |
|
Back to top |
|
 |
Emanuele
Joined: 21 Oct 2009 Posts: 78 Location: Bologna (Italy)
|
Posted: Wed Nov 16, 2011 9:24 pm Post subject: |
|
|
Thank you very much Paul.
In my opinion the most important are:
1) copyright
2) product description
3) company
Of course this ranking is questionable! |
|
Back to top |
|
 |
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8210 Location: Salford, UK
|
Posted: Thu Nov 17, 2011 8:47 am Post subject: |
|
|
Maybe the simplest solution will be to get dbk_link to accept a .cs file on the command line, this file containing standard [assembly: ...] instructions. |
|
Back to top |
|
 |
Emanuele
Joined: 21 Oct 2009 Posts: 78 Location: Bologna (Italy)
|
Posted: Thu Nov 17, 2011 9:43 pm Post subject: |
|
|
I think this solution is very close to what Visual Studio actually does. |
|
Back to top |
|
 |
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8210 Location: Salford, UK
|
Posted: Thu Nov 24, 2011 4:48 pm Post subject: |
|
|
I have added this feature to the linker for the next release. |
|
Back to top |
|
 |
Emanuele
Joined: 21 Oct 2009 Posts: 78 Location: Bologna (Italy)
|
Posted: Thu Nov 24, 2011 6:14 pm Post subject: |
|
|
Thank you very much!  |
|
Back to top |
|
 |
Emanuele
Joined: 21 Oct 2009 Posts: 78 Location: Bologna (Italy)
|
Posted: Tue Jan 24, 2012 9:49 pm Post subject: |
|
|
Is this feature already added to 6.20 release or it will come with the next one? |
|
Back to top |
|
 |
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8210 Location: Salford, UK
|
Posted: Wed Jan 25, 2012 10:05 am Post subject: |
|
|
Hopefully it is in the current release. I have not checked.
You should now be able to include an standard assembly file on the DBK_LINK command line. |
|
Back to top |
|
 |
|