Can you use a resource file with jbimp to include a version number in the resulting dll?
If so, what steps are necessary to create a resource file?
Currently, there is no support in jbimp to specify version numbers in the
dll generated nor is there support to add a win32 resource file to the dll
generated.
However, can you please let us know what version number do you want to
associate with the dll? Is it the .NET assembly version number (which will
be used by the CLR) or the file version number (used by Explorer for
instance)? From your post, it looks like the latter, but could you please
confirm?
Thanks
Sadagopan Rajaram
Microsoft Visual J# .NET Product Team.
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------
>Thread-Topic: jbimp version resource
>thread-index: AcRVbOKpq26iO7DST2aLR4v3T48BZg==
[quoted text clipped - 22 lines]
>
>If so, what steps are necessary to create a resource file?
Thomas Alex [MSFT] - 09 Jul 2004 21:13 GMT
Another alternative you could try is to use jbimp to produce a module, and
then use al.exe to create a multi-file assembly from the module.
Al.exe has options to specify both assembly version and file (win32)
version. For more information, see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/html/cp
grfAssemblyGenerationUtilityAlexe.asp
thanks
Thomas Alex
Microsoft Visual J# Product Team
This posting is provided "AS IS" with no warranties, and confers no
rights.
> Currently, there is no support in jbimp to specify version numbers in the
> dll generated nor is there support to add a win32 resource file to the
[quoted text clipped - 44 lines]
>>
>>If so, what steps are necessary to create a resource file?
jkwalnut - 11 Jul 2004 05:10 GMT
thanks, I'll take a look at that. I need to get some version info, doesn't matter if it's just a file version or the assembly version.
I actually have 2 libraries I create, one with the JBIMP for 3rd party libraries and the other my own library. I can get assemby & file versions into my library and I need to keep track of the dependencies between the two libraries.
It looks like I can combine the two libraries with the al.exe.
> Another alternative you could try is to use jbimp to produce a module, and
> then use al.exe to create a multi-file assembly from the module.
[quoted text clipped - 58 lines]
> >>
> >>If so, what steps are necessary to create a resource file?