P
Plamen Doykov
Hi everybody
I couldn't find detailed information about referencing assemblies in a
ASP.NET 2.0 web site.
Basically what I want to do is to share files with code between a tool
assembly and a web project when the web project references that tool
assembly. My first idea was to use internal classes, which should be shared
without name clashes. But the new way of building web sites in VS 2005
builds many different assemblies and thus undermines this truly useful
feature on .NET, namely 'internal' (sigh). AFAIK this limitation still
applies to web deployment project, since WDP merges already compiled
separate assemblies. If I am wromg and there is any way of using internal
classes, please tell me, I'll be very grateful.
The next idea was to make tool classes public and resolve name clashes by
using aliases when referencing assemblies. But I could not find where this
reference is remembered, having no project file. I found it in WDP, but this
is of no use, and web.config assembly section doesn't seem to allow
reference aliases.
I know it is possible to put all shared tool classes in a separate assembly
and use them from there, but this is a very very very ugly approach :-(
Thanks a lot
Plamen
I couldn't find detailed information about referencing assemblies in a
ASP.NET 2.0 web site.
Basically what I want to do is to share files with code between a tool
assembly and a web project when the web project references that tool
assembly. My first idea was to use internal classes, which should be shared
without name clashes. But the new way of building web sites in VS 2005
builds many different assemblies and thus undermines this truly useful
feature on .NET, namely 'internal' (sigh). AFAIK this limitation still
applies to web deployment project, since WDP merges already compiled
separate assemblies. If I am wromg and there is any way of using internal
classes, please tell me, I'll be very grateful.
The next idea was to make tool classes public and resolve name clashes by
using aliases when referencing assemblies. But I could not find where this
reference is remembered, having no project file. I found it in WDP, but this
is of no use, and web.config assembly section doesn't seem to allow
reference aliases.
I know it is possible to put all shared tool classes in a separate assembly
and use them from there, but this is a very very very ugly approach :-(
Thanks a lot
Plamen