Assembly info not showing up in explorer in managed DLL
-
Hello, I made a DLL wrapper in managed code which is merely a wrapper function around a native C++ DLL. The DLL works perfectly except I can not see the assembly info in explorer. Using ILDASM, I can see the fields in the manifest. What could be wrong? Thanks in advance
-
Hello, I made a DLL wrapper in managed code which is merely a wrapper function around a native C++ DLL. The DLL works perfectly except I can not see the assembly info in explorer. Using ILDASM, I can see the fields in the manifest. What could be wrong? Thanks in advance
The C# and VB compilers will pull the info from assemblyinfo.cs and create the required version resource. Since C++ supports native resources it will not do this automatically. You will have to create a native version resource manually like you would with a native project. There will be some information duplication of course, but it's not a big deal I guess.
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
-
The C# and VB compilers will pull the info from assemblyinfo.cs and create the required version resource. Since C++ supports native resources it will not do this automatically. You will have to create a native version resource manually like you would with a native project. There will be some information duplication of course, but it's not a big deal I guess.
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
OK, thanks Nishant, I added a resource to VS2010 project which created the info. I needed. So in AssemblyInfo.cpp the only information that I can affect is for signing the assembly and where the key is located. Can I then remove the other fields or are they used?
-
OK, thanks Nishant, I added a resource to VS2010 project which created the info. I needed. So in AssemblyInfo.cpp the only information that I can affect is for signing the assembly and where the key is located. Can I then remove the other fields or are they used?
alleyes wrote:
Can I then remove the other fields or are they used?
Yeah you can remove them if you don't want to have that info in the assembly metadata (which is query-able from .NET).
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application