编译为不同的文件扩展名 [英] Compileing to diffrent file extensions
问题描述
大家好，
我在我的应用程序中做的是我有一个基本应用程序，然后是一堆
插件dll文件。好吧，这会混淆
真正的插件与不用作
插件的实际链接库之间的区别（实际上它们都是DLL文件）无论如何我可以制作
VS.NET将我的VB.NET DLL插件项目编译成不同的扩展但是
仍然是DLL文件？ （我不想用手改变数十个扩展名
每个版本）我希望扩展名为.bdbPlugin而不是
of .DLL for the plug -ins所以我也可以将文件类型与它们关联起来
在windows中为它们提供带有文件类型关联的自定义图标...谢谢！
Hi everyone,
What I am doing in my application is I have a base app, then a bunch of
plug-in dll files. Well this gets confuseing to diferentiate between the
real plug-ins and the actual link libraries that are not to be used as
plugins (in reality they are both DLL files) is there anyway I could make
VS.NET compile my VB.NET DLL plug-in projects into a diffrent extension but
still be DLL files? (i dont feel like changeing tens of extensions by hand
each build) I''d like the extension to be something like .bdbPlugin instead
of .DLL for the plug-ins so i could also associate a file type with them and
give them custom icons with the file type association in windows... thanks!
推荐答案
*" Brian Henry" < brianiup [NOSPAM] @ adelphia.net> scripsit：
* "Brian Henry" <brianiup[nospam]@adelphia.net> scripsit:
我在我的应用程序中做的是我有一个基本应用程序，然后是一堆
插件DLL文件。好吧，这让人感到困惑的是真正的插件与不用作插件的实际链接库之间的区别（实际上它们都是DLL文件）无论如何我都可以使用
仍然是DLL文件？ （我不想用手改变数十个扩展程序每个构建）我希望扩展名为.bdbPlugin而不是
AFAIS，你不能这样做，我不会这样做。选择一个名称，如
" MySample1.PlugIn.dll"或类似的东西。
插件的.DLL的
所以我也可以将文件类型与它们关联起来，并在窗口中为它们提供带有文件类型关联的自定义图标...谢谢！
What I am doing in my application is I have a base app, then a bunch of
plug-in dll files. Well this gets confuseing to diferentiate between the
real plug-ins and the actual link libraries that are not to be used as
plugins (in reality they are both DLL files) is there anyway I could make
VS.NET compile my VB.NET DLL plug-in projects into a diffrent extension but
still be DLL files? (i dont feel like changeing tens of extensions by hand
each build) I''d like the extension to be something like .bdbPlugin instead
AFAIS, you cannot do that, and I would not do it. Choose a name like
"MySample1.PlugIn.dll" or something like that.
of .DLL for the plug-ins so i could also associate a file type with them and
give them custom icons with the file type association in windows... thanks!
你有没有看到另一个应用程序？我没有看到很多意义
隐藏用户文件实际上包含
可以执行的代码这一事实。
-
Herfried K. Wagner [MVP]
< URL：http：//dotnet.mvps.org/>
Did you ever see that for another application? I don''t see much sense
in hiding the user the fact that the file actually contains code that
can be executed.
--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>
许多应用程序这样做是为了区分不同类型的库
他们可能已经创建了...它在C ++中更具有预防性，我用它来
在那里做。 VB.NET似乎更多地扼杀了你编译
文件的内容。在C ++中，我们和其他公司制作的许多文件是
真正编译的DLL文件作为不同类型传递（AOL，Adobe和MS
为某些人执行此操作文件类型）仅举几例。
" Herfried K. Wagner [MVP]" <喜*************** @ gmx.at>在消息中写道
news：2g ************ @ uni-berlin.de ...
many applications do this to distinguish the different types of libraries
they may have created... it''s a lot more prevelant in C++, which I am use to
doing it there. VB.NET seems to have more of a strangle on what you compile
files into. In C++ a lot of files that we and other companies make are
really compiled DLL files passed off as a diffrent type (AOL, Adobe, and MS
do this for some file types) to name a few.
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:2g************@uni-berlin.de...
*" Brian Henry" < brianiup [NOSPAM] @ adelphia.net> scripsit：
* "Brian Henry" <brianiup[nospam]@adelphia.net> scripsit:
我在我的应用程序中做的是我有一个基本应用程序，然后是一堆
插件DLL文件。好吧这让人感到困惑的是真正的插件与不用作插件的实际链接库之间的区别（实际上它们都是DLL文件）无论如何我都可以
让VS.NET将我的VB.NET DLL插件项目编译成不同的扩展名
但仍然是DLL文件？ （我不想用每个版本的
手动改变数十个扩展名）我希望扩展名为.bdbPlugin
而不是
What I am doing in my application is I have a base app, then a bunch of
plug-in dll files. Well this gets confuseing to diferentiate between the
real plug-ins and the actual link libraries that are not to be used as
plugins (in reality they are both DLL files) is there anyway I could make VS.NET compile my VB.NET DLL plug-in projects into a diffrent extension but still be DLL files? (i dont feel like changeing tens of extensions by hand each build) I''d like the extension to be something like .bdbPlugin instead
AFAIS，你不能这样做，我不会这样做。选择像
MySample1.PlugIn.dll这样的名称。或类似的东西。
AFAIS, you cannot do that, and I would not do it. Choose a name like
"MySample1.PlugIn.dll" or something like that.
of .DLL for the plug-ins所以我也可以将文件类型与它们关联
of .DLL for the plug-ins so i could also associate a file type with them
并给它们自定义图标Windows中的文件类型关联...
and give them custom icons with the file type association in windows...
谢谢！
你有没有看到另一个应用程序？在隐藏用户文件实际上包含可以执行的代码这一事实时，我没有多大意义。
-
Herfried K. Wagner [MVP]
< URL：http：//dotnet.mvps.org/>
thanks!
Did you ever see that for another application? I don''t see much sense
in hiding the user the fact that the file actually contains code that
can be executed.
--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>
*" Brian Henry" < brianiup [NOSPAM] @ adelphia.net> scripsit：
* "Brian Henry" <brianiup[nospam]@adelphia.net> scripsit:
许多应用程序这样做是为了区分他们可能已经创建的不同类型的库...它在C ++中更具有预防性，我将其用于
在那里做。 VB.NET似乎更多地扼杀了你编译的文件。在C ++中，我们和其他公司制作的很多文件都是真正编译的DLL文件，它们作为一种不同的类型传播（AOL，Adobe和MS对某些文件类型执行此操作），仅举几例。
many applications do this to distinguish the different types of libraries
they may have created... it''s a lot more prevelant in C++, which I am use to
doing it there. VB.NET seems to have more of a strangle on what you compile
files into. In C++ a lot of files that we and other companies make are
really compiled DLL files passed off as a diffrent type (AOL, Adobe, and MS
do this for some file types) to name a few.
基本上，这也不应该是.NET程序集的问题，但是VS
并不支持更改扩展程序输出。你所能做的只是
编写一个加载项，用
完成构建之后用新名称创建DLL的副本。我没有测试它，但它可能有效。
-
Herfried K. Wagner [MVP]
< URL：http：//dotnet.mvps.org/>
Basically, that should not be a problem for .NET assemblies too, but VS
doesn''t support changing the extension of the output. All you can do is
writing an add-in that creates a copy of the DLL with the new name after
completing the build. I didn''t test it, but it may work.
--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>
这篇关于编译为不同的文件扩展名的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
