MBR IT/.NET 247 : Is this true: Web Applications, by default, do not look in the GAC to resolve assembly references at runtime. on ASPFriends.com 'aspngfreeforall' list

Is this true: Web Applications, by default, do not look in the GAC to resolve assembly references at runtime.

Messages

Related Types

This message was discovered on ASPFriends.com 'aspngfreeforall' list.

Bill Bassler

Is it true that ASP.Net web Applications, by default, do not look in the GAC
to resolve assembly references at runtime?

If this is, by default, so ... is it possible to set up an application build
so that at run-time an ASP.Net application will look for shared assemblies
in the GAC at run-time?

Or am I always forced to put a copy of commonly used .dlls (such as a
third-party components) in the local project directory when I build?

If this is true, that implies that I can't use Shared components with
ASP.Net? That would not be a very good default behavior. It would seem
anyway.

True or not?

Reply to this message...

Steve Mark

You can use the GAC with ASP.NET.

Steve

[Original message clipped]

Reply to this message...

Bill Bassler

My "understanding" is essentially the same ... if an assembly is built using
a strong name... it can be registered in the GAC, otherwise it cannot.

With that said, the .Net run-time loader search order is:

- An assembly calling another will first look locally (deemed private
assembly) for the dependant assembly. Assemblies NOT installed in the GAC do
not enforce versioning at all and are not signed with a strong name.

- Unless a <assemblyname>.config file is used in a caller's build to
specifically instruct the calling assembly to use another dependant assembly
via the <dependant assembly> <binding redirect newVersion ....> versioning
scheme ... the assembly in the GAC containing the version that the calling
assembly was built against will be used.

- I assume ... if a private copy of the assembly is NOT available to the
calling assembly and version that the calling assembly was built against
does not reside in the GAC ... and there is no explicit assembly binding
redirection compiled into the caller that is able to locate the "redirected
to assembly", ann exception will be thrown???

Is the correct and complete.

"André Colbiörnsen" <Click here to reveal e-mail address> wrote in message
news:699811@aspngfreeforall...

Afaik you can register all assemblies with the GAC util. An application
will (also afaik) start by looking for the assembly, and if it can't be
found there, search the GAC.

Regards/Halsningar

Andre Colbiornsen
--------------------------------------
Sonnenburg Communications
Bergsgatan 3,
SE-211 54 Malmö
Sweden
Tel.: +46-(0)40-97 78 80
Fax.: +46-(0)40-97 78 80
Mob.: +46-(0)708-97 78 79
Mail: Click here to reveal e-mail address
Web.: www.sonnenburg.se
----------------------------------------
B2B Web Solutions - Specializing in .Net
----------------------------------------

-----Ursprungligt meddelande-----
Från: Bill Bassler [mailto:Click here to reveal e-mail address]
Skickat: den 19 augusti 2002 16:42
Till: aspngfreeforall
Ämne: [aspngfreeforall] Is this true: Web Applications, by default, do
not look in the GAC to resolve assembly references at runtime.

Is it true that ASP.Net web Applications, by default, do not look in the
GAC to resolve assembly references at runtime?

If this is, by default, so ... is it possible to set up an application
build so that at run-time an ASP.Net application will look for shared
assemblies in the GAC at run-time?

Or am I always forced to put a copy of commonly used .dlls (such as a
third-party components) in the local project directory when I build?

If this is true, that implies that I can't use Shared components with
ASP.Net? That would not be a very good default behavior. It would seem
anyway.

True or not?

| ASP.net DOCS = http://www.aspng.com/docs
| [aspngfreeforall] member Click here to reveal e-mail address = YOUR ID
| http://www.asplists.com/aspngfreeforall = JOIN/QUIT
| news://ls.asplists.com = NEWSGROUP

Reply to this message...

Bill Bassler

I can see another question would be ..
How do a simply tell a calling assembly not to even look for a private
assembly, just go straight to the GAC and look for it.
Is there a way to do this?

"Bill Bassler" <Click here to reveal e-mail address> wrote in message
news:699779@aspngfreeforall...
[Original message clipped]

Reply to this message...

MBR BootFX
Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

	Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd.
	Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com