From: Steven Cheng[MSFT] on
Hi Dave,

So far I haven't found any built-in setting in VS IDE that can
automatically add assembly into GAC. I think you need to use the post-build
event to add the build assembly into GAC. BTW, is those problem assembly
originally put in BIN dir?

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.

From: David Thielen on
Elsewhere someone posted that it is fine to have strongly named DLLs in the
directory with the exe.

And VS 2005 does exactly that. So I think it is ok to not put them in the GAC.

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm




"Steven Cheng[MSFT]" wrote:

> Hi Dave,
>
> So far I haven't found any built-in setting in VS IDE that can
> automatically add assembly into GAC. I think you need to use the post-build
> event to add the build assembly into GAC. BTW, is those problem assembly
> originally put in BIN dir?
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
From: Steven Cheng[MSFT] on
Thanks for your reply Dave,

Yes, you are right. This limitation is specific to ASP.NET 1.0/1.1, in
ASP.NET 2.0, there is no longer such limitation, since no matter the
assembly is strong-named or not(in bin dir), it will be loaded per
app-domain and shadow copied. I've get confirmation from some other dev
team engineers.


Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.