为.tlh和.tli文件生成的标头 [英] Header generated for .tlh and .tli files

问题描述

当从外部.tlb或.dll导入时，Microsoft C ++编译器当前生成类似这样的标题。

The Microsoft C++ compiler currently generates a header like this one when importing from an external .tlb or .dll.

// Created by Microsoft (R) C/C++ Compiler Version 14.13.26129.0 (6ddc810e).
//
// c:\workspace\development\bridgenet\application\bridgenet.compiler\release\probeenvsrvr.tlh
//
// C++ source equivalent of Win32 type library probeenvsrvr.tlb
// compiler-generated file created 03/26/18 at 14:04:41 - DO NOT EDIT!

没有太多的目的让文件在标题中包含自己的路径。 如果我打开此文件以查看其内容，那么我已经知道该文件的位置。  （如果我不这样做，Visual Studio IDE无论如何都会告诉我。）

There's not much purpose to having a file include a path to itself in the header.  If i ever open this file to view its content, then I already know where the file is located.  (And if I don't, the Visual Studio IDE will tell me anyway.)

更有用的是在此标题中包含.tlb或.dll的路径用于生成我当前正在查看的.tlh或.tli文件。 当某人最终遇到分散在不同文件夹中的冲突DLL时，
这将使您一眼就知道编译器是否使用了您真正打算使用的文件。 我浪费了一整天，因为编译器是从一个模糊的系统路径中选择一个DLL的内容，而不是在我的项目中定义的实际包含文件夹
......

What WOULD be much more useful is to have in this header the path to the .tlb or .dll that was used to generate this .tlh or .tli file that I am currently viewing.  When someone ends up with conflicting DLLs that are spread across different folders, this would let you know at a glance if the compiler used the file that you really intended to use.  I have just wasted a whole day because the compiler was content choosing a DLL from an obscure system path in place of the actual include folders that were defined in my project...

请考虑这是一个建议。

推荐答案

>请考虑这是一个建议。

>Consider this as a suggestion, please.

您可以在此处提供建议：
https：// visualstudio .uservoice.com / forums / 121579-visual-studio

You can provide suggestions here: https://visualstudio.uservoice.com/forums/121579-visual-studio

这篇关于为.tlh和.tli文件生成的标头的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！