I've read the ASP.NET QuickStart Tutorial "Working with Resource Files" about
how to use satellite assemblies for resources in ASP.NET, and I've gotten it
to work... but I don't really understand HOW it works.

My confusion regards how the tutorial uses one name (qq.dll in \bin) in Step
1 for the assembly containing the default resources, but then uses a
different name (eg: qq.resources.dll in \bin\es-MX) in Step 3 for the
assemblies containing the localized resources. Then in Step 2 it shows the
app loading the resource assembly:

Dim a As Assembly = Assembly.Load("qq")

But how does the above method successfully load the qq assembly (from \bin)
when I don't over-ride currentUIcultrue but loads qq.resources (from
\bin\es-MX, when currentUIculture = "es-MX")?

(Yes, I understand that the search is based on the currentUIculture, but how
does it work since the default and culture-specific assemblies don't have the
same name?)

In short, how does a load for assembly "qq" result ever result in assembly
"qq.resource" being loaded?

Thanks,

DT

This section in MSDN covers it all:

http://msdn.microsoft.com/library/de...asp?frame=true

This specifically discusses the resource assembly probing and fallback mechanism:

http://msdn.microsoft.com/library/de...sourcesanchor1

-Brock
DevelopMentor
http://staff.develop.com/ballen



> I've read the ASP.NET QuickStart Tutorial "Working with Resource
> Files" about how to use satellite assemblies for resources in ASP.NET,
> and I've gotten it to work... but I don't really understand HOW it
> works.
>
> My confusion regards how the tutorial uses one name (qq.dll in \bin)
> in Step 1 for the assembly containing the default resources, but then
> uses a different name (eg: qq.resources.dll in \bin\es-MX) in Step 3
> for the assemblies containing the localized resources. Then in Step 2
> it shows the app loading the resource assembly:
>
> Dim a As Assembly = Assembly.Load("qq")
>
> But how does the above method successfully load the qq assembly (from
> \bin) when I don't over-ride currentUIcultrue but loads qq.resources
> (from \bin\es-MX, when currentUIculture = "es-MX")?
>
> (Yes, I understand that the search is based on the currentUIculture,
> but how does it work since the default and culture-specific assemblies
> don't have the same name?)
>
> In short, how does a load for assembly "qq" result ever result in
> assembly "qq.resource" being loaded?
>
> Thanks,
>
> DT
>