es-MX/snafu.resources.dll

[Robert Dobson]

I've run into a rather perplexing problem and unfortunately nobody has yet
been able to help me resolve it. I have built an application that supports
both English and Spanish text. When I compile, I get /bin/snafu.dll and
/bin/es-MX/snafu.resources.dll. When I run it on my workstation, everything
is fine; I can see both the English and Spanish versions. However, when I
copy the application to another machine, I can no longer see the Spanish
version of the verbiage. It is documented in the .Net API that
ResourceManager will default to the English if it is unable to find the
Spanish, however there's no reason (that I can figure out) that it can't
find the Spanish verbiage -- it's in the snafu.resources.dll file in the
es-MX subdirectory. Can somebody please explain this to me? This project
is reaching critical mass and if I don't resolve this problem I'm going to
need to build my own resource manager. Thanks!

[Bernie Yaeger]

Hi Robert,

Just a couple of probably useless suggestions:

1. why is the .dll named with 2 dots in one case but not in the other?
Perhaps the system is looking for snafu.dll and only finding
snafu.resources. I would name one snafu_e.dll and the other snafu_s.dll.

2. Use the same directory structure - bin/snafu_e.dll and bin/snafu_s.dll.
If you have to have different locations, bin/s/etc and bin/e/etc

My guess is that item 1. above is more on track.

HTH,

Bernie Yaeger

"Robert Dobson" <tr****@hotmail.com> wrote in message
news:uW*************@tk2msftngp13.phx.gbl...

I've run into a rather perplexing problem and unfortunately nobody has yet
been able to help me resolve it. I have built an application that supports both English and Spanish text. When I compile, I get /bin/snafu.dll and
/bin/es-MX/snafu.resources.dll. When I run it on my workstation, everything is fine; I can see both the English and Spanish versions. However, when I
copy the application to another machine, I can no longer see the Spanish
version of the verbiage. It is documented in the .Net API that
ResourceManager will default to the English if it is unable to find the
Spanish, however there's no reason (that I can figure out) that it can't
find the Spanish verbiage -- it's in the snafu.resources.dll file in the
es-MX subdirectory. Can somebody please explain this to me? This project
is reaching critical mass and if I don't resolve this problem I'm going to
need to build my own resource manager. Thanks!

[Robert Dobson]

Visual Studio .Net named the files and placed them in that directory
structure without any input from me :-)
"Bernie Yaeger" <be*****@cherwellinc.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

Hi Robert,

Just a couple of probably useless suggestions:

1. why is the .dll named with 2 dots in one case but not in the other?
Perhaps the system is looking for snafu.dll and only finding
snafu.resources. I would name one snafu_e.dll and the other snafu_s.dll.

2. Use the same directory structure - bin/snafu_e.dll and bin/snafu_s.dll. If you have to have different locations, bin/s/etc and bin/e/etc

My guess is that item 1. above is more on track.

HTH,

Bernie Yaeger

"Robert Dobson" <tr****@hotmail.com> wrote in message
news:uW*************@tk2msftngp13.phx.gbl...

I've run into a rather perplexing problem and unfortunately nobody has yet been able to help me resolve it. I have built an application that

supports

both English and Spanish text. When I compile, I get /bin/snafu.dll and
/bin/es-MX/snafu.resources.dll. When I run it on my workstation,

everything

is fine; I can see both the English and Spanish versions. However, when I copy the application to another machine, I can no longer see the Spanish
version of the verbiage. It is documented in the .Net API that
ResourceManager will default to the English if it is unable to find the
Spanish, however there's no reason (that I can figure out) that it can't
find the Spanish verbiage -- it's in the snafu.resources.dll file in the
es-MX subdirectory. Can somebody please explain this to me? This project is reaching critical mass and if I don't resolve this problem I'm going to need to build my own resource manager. Thanks!

[Bernie Yaeger]

Hi Robert,

I'm growing more confident that the name of the .dll is the problem.

I use several dlls in my vb .net apps. VS .Net never, never named them
anything but <classname>.dll. How did you create the .dll? Also, was it
managed code to begin with? Just for argument's sake, copy
snafu.resources.dll to snafu.dll and see if it can be found.

HTH,

Bernie Yaeger

"Robert Dobson" <tr****@hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

Visual Studio .Net named the files and placed them in that directory
structure without any input from me :-)
"Bernie Yaeger" <be*****@cherwellinc.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

Hi Robert,

Just a couple of probably useless suggestions:

1. why is the .dll named with 2 dots in one case but not in the other?
Perhaps the system is looking for snafu.dll and only finding
snafu.resources. I would name one snafu_e.dll and the other snafu_s.dll.

2. Use the same directory structure - bin/snafu_e.dll and bin/snafu_s.dll.

If you have to have different locations, bin/s/etc and bin/e/etc

My guess is that item 1. above is more on track.

HTH,

Bernie Yaeger

"Robert Dobson" <tr****@hotmail.com> wrote in message
news:uW*************@tk2msftngp13.phx.gbl...

I've run into a rather perplexing problem and unfortunately nobody has

yet been able to help me resolve it. I have built an application that

supports

both English and Spanish text. When I compile, I get /bin/snafu.dll and /bin/es-MX/snafu.resources.dll. When I run it on my workstation,

everything

is fine; I can see both the English and Spanish versions. However, when I

copy the application to another machine, I can no longer see the

Spanish version of the verbiage. It is documented in the .Net API that
ResourceManager will default to the English if it is unable to find the Spanish, however there's no reason (that I can figure out) that it can't find the Spanish verbiage -- it's in the snafu.resources.dll file in the es-MX subdirectory. Can somebody please explain this to me? This

project is reaching critical mass and if I don't resolve this problem I'm

going to need to build my own resource manager. Thanks!

[Robert Dobson]

I just chose Build->Rebuild Solution from the toolbar and Visual Studio .Net
created a subdirectory under /bin named /es-MX and placed in it a DLL named
snaful.resources.dll. And like I said in the original post, it works just
fine on my workstation. I tried renaming the DLL, and I also tried copying
it up into the /bin directory. Neither worked. Thanks for the suggestions.
"Bernie Yaeger" <be*****@cherwellinc.com> wrote in message
news:uF**************@tk2msftngp13.phx.gbl...

Hi Robert,

I'm growing more confident that the name of the .dll is the problem.

I use several dlls in my vb .net apps. VS .Net never, never named them
anything but <classname>.dll. How did you create the .dll? Also, was it
managed code to begin with? Just for argument's sake, copy
snafu.resources.dll to snafu.dll and see if it can be found.

HTH,

Bernie Yaeger