在没有GAC的情况下引用程序集问题 [英] Referencing Assembly Question Without GAC?

问题描述

在我问我之前，我发现了这个问题：


----<上一个问题> ----

我们显然是在做什么这是错误的方式，所以在我们走得太远之前我需要一些建议。


我们所有常见的程序集都像我们的页面基类等位于我们的

开发服务器。


我们在所有应用程序中引用它们，Copy Local设置为trued


然后我们例如，将它们发布到生产服务器，这样每个asp.net

app都会在bin目录中有一个公共程序集的副本。


这当然是让我们在更改时必须在每个bin目录中替换

程序集。


避免此问题的最佳做法是什么？


万分感谢，


Jason MacKenzie"

----< /上一个问题> ----


我有同样的问题，但我不能使用GAC因为不同的原因我无法理解。有人可以帮忙做最好的练习吗？


谢谢！

I found this question before I asked mine:

----<previous question>----
We are clearly going about this the wrong way so before we get too far I
would like some advice.

We have all common assemblies like our page base class etc located on our
Dev server.

We reference them in all our applications with Copy Local set to trued

We then publish them to the production server for example so each asp.net
app has a copy of the common assembly in the bin directory.

This is of course leaving us with the problem of having to replace the
assembly in every bin directory when a change is made.

What is the best practice to avoid this issue?

Thanks a million,

Jason MacKenzie"
----</previous question>----

I have this same issue, however I can''t use the GAC because of different
reasons out of my control. Can someone help with the best practice?

THANKS!

推荐答案

我不知道是什么这个问题应该是。您应该避免使用

GAC，最佳做法是将程序集放在/ bin文件夹中。我不知道为什么Jason似乎认为每次组装都需要在更改时更换
。假设更改在一个项目中，

只需要换出一个DLL。并且使用新的DLL覆盖原始DLL，就可以轻松地将其转换出来。

有什么问题？


-

HTH，

Kevin Spencer

..Net开发人员

微软MVP

跟随者既不是b $ b也不是贷款人。


" Mike" <弥** @ discussions.microsoft.com>在消息中写道

news：35 ********************************** @ microsof t.com ...

I''m not sure what "this issue" is supposed to be. You should avoid using the
GAC, and the best practice is to put your assemblies in the /bin folder. I
don''t know why Jason seemed to think that every assembly needs to be
replaced when a change is made. Assuming that the change is in one project,
only that one DLL needs to be swapped out. And swappping it out is as simple
as overwriting the original DLL with the new one. What is the problem with
this?

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Neither a follower
nor a lender be.

"Mike" <Mi**@discussions.microsoft.com> wrote in message
news:35**********************************@microsof t.com...

在我问我之前我发现了这个问题：

----<上一个问题> ----
我们是显然这是错误的，所以在我们走得太远之前我想要一些建议。

我们的所有常见程序集都像我们的页面基类等位于我们的
Dev服务器。

我们在所有应用程序中引用它们，Copy Local设置为trued

然后我们将它们发布到生产服务器，例如每个asp.net
应用程序在bin目录中有一个通用程序集的副本。

这当然让我们在更改时必须更换每个bin目录中的
程序集。

避免这个问题的最佳做法是什么？

感谢上百万，

Jason MacKenzie"
----< ; /上一个问题> ----

我有同样的问题但是由于我不同的原因，我无法使用GAC。有人可以帮助进行最佳实践吗？

感谢！

I found this question before I asked mine:

----<previous question>----
We are clearly going about this the wrong way so before we get too far I
would like some advice.

We have all common assemblies like our page base class etc located on our
Dev server.

We reference them in all our applications with Copy Local set to trued

We then publish them to the production server for example so each asp.net
app has a copy of the common assembly in the bin directory.

This is of course leaving us with the problem of having to replace the
assembly in every bin directory when a change is made.

What is the best practice to avoid this issue?

Thanks a million,

Jason MacKenzie"
----</previous question>----

I have this same issue, however I can''t use the GAC because of different
reasons out of my control. Can someone help with the best practice?

THANKS!

如果你不能使用GAC那么你将不得不运行他们在当地。即bin目录中的
。 GAC只需在全球注册一个dll

，就可以同时运行多个版本

。 COM类型的dll可以在regasm.exe / codebase中注册。

这将使它们成为全局的，但它们需要强大的命名以便具有

多版本化功能。

希望这有帮助

-wiz


" Mike" <弥** @ discussions.microsoft.com>在消息中写道

news：35 ********************************** @ microsof t.com ...

If you can not use the GAC then you will have to run them locally. i.e. in
the bin directory. The GAC is there for a single point to have a dll
registered globally and have the ability to have multiple versions running
at the same time. COM type dlls can be registered with regasm.exe /codebase.
This will make them global but they need to be strong named inorder to have
multiversion capabilities.
Hope this helps
-wiz

"Mike" <Mi**@discussions.microsoft.com> wrote in message
news:35**********************************@microsof t.com...

在我问我之前我发现了这个问题：

----<上一个问题> ----
我们是显然这是错误的，所以在我们走得太远之前我想要一些建议。

我们的所有常见程序集都像我们的页面基类等位于我们的
Dev服务器。

我们在所有应用程序中引用它们，Copy Local设置为trued

然后我们将它们发布到生产服务器，例如每个asp.net
应用程序在bin目录中有一个通用程序集的副本。

这当然让我们在更改时必须更换每个bin目录中的
程序集。

避免这个问题的最佳做法是什么？

感谢上百万，

Jason MacKenzie"
----< ; /上一个问题> ----

我有同样的问题但是由于我不同的原因，我无法使用GAC。有人可以帮助做最好的练习吗？

感谢！

I found this question before I asked mine:

----<previous question>----
We are clearly going about this the wrong way so before we get too far I
would like some advice.

We have all common assemblies like our page base class etc located on our
Dev server.

We reference them in all our applications with Copy Local set to trued

We then publish them to the production server for example so each asp.net
app has a copy of the common assembly in the bin directory.

This is of course leaving us with the problem of having to replace the
assembly in every bin directory when a change is made.

What is the best practice to avoid this issue?

Thanks a million,

Jason MacKenzie"
----</previous question>----

I have this same issue, however I can''t use the GAC because of different
reasons out of my control. Can someone help with the best practice?

THANKS!

我有待纠正;但我相信你可以在wwwroot下的bin文件夹中部署所有常见的

程序集：

-wwwroot

---- / bin


这样所有子应用程序都可以共享在这个文件夹中部署的这个相同的程序集。因此，您只需要在wwwroot / bin文件夹下替换部署的单个汇编

。试试这个

" Mike"写道：

I stand to be corrected; but I believe you can just deploy all of your common
assemblies in a bin folder located under wwwroot:
-wwwroot
----/bin

this way all sub applications can share this very same assembly deployed in
this folder. So, you would just have to replace the single assemble deployed
under the wwwroot/bin folder. try this out
"Mike" wrote:

在我问我之前我发现了这个问题：

----<上一个问题> ----
我们是显然这是错误的，所以在我们走得太远之前我想要一些建议。

我们的所有常见程序集都像我们的页面基类等位于我们的
Dev服务器。

我们在所有应用程序中引用它们，Copy Local设置为trued

然后我们将它们发布到生产服务器，例如每个asp.net
应用程序在bin目录中有一个通用程序集的副本。

这当然让我们在更改时必须更换每个bin目录中的
程序集。

避免这个问题的最佳做法是什么？

感谢上百万，

Jason MacKenzie"
----< ; / /上一个问题> ----

我有同样的问题，但由于不同的原因我无法使用GAC我的控制。有人可以帮助做最好的练习吗？

感谢！

I found this question before I asked mine:

----<previous question>----
We are clearly going about this the wrong way so before we get too far I
would like some advice.

We have all common assemblies like our page base class etc located on our
Dev server.

We reference them in all our applications with Copy Local set to trued

We then publish them to the production server for example so each asp.net
app has a copy of the common assembly in the bin directory.

This is of course leaving us with the problem of having to replace the
assembly in every bin directory when a change is made.

What is the best practice to avoid this issue?

Thanks a million,

Jason MacKenzie"
----</previous question>----

I have this same issue, however I can''t use the GAC because of different
reasons out of my control. Can someone help with the best practice?

THANKS!

这篇关于在没有GAC的情况下引用程序集问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！