Missing version info in multifile assembly

[=?Utf-8?B?aWduaGVucnk=?=]

In my solution, I have several C# and C++ projects. Since I need them to
produce multifile assembly, I use C# and C++ command line compiler. To avoid
compile error caused by redundant code in AssemblyInfo.cs in each of the
projects, I then created GlobalAssemblyInfo.cs at the solution level, which
contains copyright, version number, etc, and have it shared among the
projects. I manage to build the solution and get several netmodules and one
DLL.

Now my question is why the DLL's properties window in windows explorer does
not display the version tab, while roeder's .net reflector shows that the
version related information are embedded correctly in the assembly.

What am I doing wrong?

Thanks in advance
-- Henry

[Jeffrey Tan[MSFT]]

Hi Henry,

I assume you are using link.exe to combine and generate the final .Net
assembly. I suspect this issue is the same as I originally replied below:
http://groups.google.com/group/micro.../msg/d5cf65083
4f8c947

For C++ compiler and linker, AssemblyInfo.cpp
attributes(AssemblyVersionAttribute etc...) will be added into the final
assembly as .Net manifest. However, it will not be used to display the
version tabpage in PE property window. While C# compiler/linker will use
AssemblyVersionAttribute to generate the version tabpage in PE property
window.

To resolve this issue, you may add the win32 resource *.rc file which
contains the Version resource to the C++ compiler/linker, I assume this
will be shown in the final DLL property window. See my reply in the URL
above for more details.

Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[=?Utf-8?B?aWduaGVucnk=?=]

Hi Jeffrey,

Thanks for the explanation. I tried your suggestion and the version tab now
appears in the properties windows.

Henry
""Jeffrey Tan[MSFT]"" wrote:

Hi Henry,

I assume you are using link.exe to combine and generate the final .Net
assembly. I suspect this issue is the same as I originally replied below:
http://groups.google.com/group/micro.../msg/d5cf65083
4f8c947

For C++ compiler and linker, AssemblyInfo.cpp
attributes(AssemblyVersionAttribute etc...) will be added into the final
assembly as .Net manifest. However, it will not be used to display the
version tabpage in PE property window. While C# compiler/linker will use
AssemblyVersionAttribute to generate the version tabpage in PE property
window.

To resolve this issue, you may add the win32 resource *.rc file which
contains the Version resource to the C++ compiler/linker, I assume this
will be shown in the final DLL property window. See my reply in the URL
above for more details.

Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.