locked
tell the platform applied to compiled library files RRS feed

  • General discussion

  • How to identify the platform of the compiled library file (such as *.dll or *.lib), win32, windows mobile or pocket ?

    How to identify the version(debug/release) of compiled  library file?

    Thank you in advance.

    • Changed type Chao Kuo Tuesday, March 23, 2010 1:48 AM not related to VSX
    Tuesday, March 16, 2010 6:26 AM

All replies

  • hi. Is that question clear? Why no response?
    Wednesday, March 17, 2010 1:11 AM
  • Hello, Wang

    This forum is mainly talked about Visual studio extensibility, so next time please post your question in CLR forum.

    For How to identify the version(debug/release), because compiler use DebuggableAttribute  to generate debug version assembly, so you could check this attribute and its properties to identify the version.

    But as far as I invested, there is no better way for us to get the platform, a way is to use Process to start CorFlags.exe, we could get the PE header information in the output. And we could parse the output using regular expression or other way.

    About how PE store platform information, please reference this link.

    http://blogs.msdn.com/gauravseth/archive/2006/03/07/545104.aspx

    Thanks

    Chao

    Wednesday, March 17, 2010 5:53 AM
  • Thank you. Chao.

    I am sorry for not familiar with here.

    By the way, what is CLR? How can I reach CLR forum?
    Wednesday, March 17, 2010 7:03 AM
  • Hello, Wang
    I am sorry, not CLR forum, but this forum http://social.msdn.microsoft.com/Forums/en/netfxbcl/threads.
    Thanks
    Chao
    Thursday, March 18, 2010 2:42 AM
  • For How to identify the version(debug/release), because compiler use DebuggableAttribute  to generate debug version assembly, so you could check this attribute and its properties to identify the version.

    But as far as I invested, there is no better way for us to get the platform, a way is to use Process to start CorFlags.exe, we could get the PE header information in the output. And we could parse the output using regular expression or other way.

    About how PE store platform information, please reference this link.

    http://blogs.msdn.com/gauravseth/archive/2006/03/07/545104.aspx

    But how do you store the other information asked about in the OP? And how can that be stored in a way that can be viewed from the file attributes in the file dialog?

    The method described is an internal way to pull the information with a tool, and only in certain predefined slots. If you have a solution with several free form configurations, how do you store that information in way that can be easily accessed when the file is installed?

    Thanks! 

    Also, I think this question is actually more appropriate to this forum because I'd like to find out how to accomplish through the Studio settings or some other type of extensibility.

    Wednesday, May 5, 2010 4:03 AM