M
Mike Lansdaal
I am using InfoPath2003 SP2 (with VS 2005/VSTO 2005 first release), and I
have a situation where I wanted to take advantage of the .NET
Internationalization features and custom cultures.
Unfortunately, I have found that while InfoPath will embedd a
dependent/referenced .NET assembly into the XSN file, it does not similarly
the related package resource files. Nor does the MS regform tool pick them up
when making a MSI file. Adding the resource assembly to the manifest doesn't
work either.
I figured that I would have to deploy the resource files separately, but
here's what I ran into. Placing the localized assembly files in the installed
directory “C:\Program Files\InfoPath Templates†does not result in loading
the appropriate culture assembly – turns out that InfoPath extracts the DLLs
from the InfoPath XSN file and then stores them in the .NET system download
cache ( C:\Documents and Settings\[profilename]\Local Settings\Application
Data\assembly\dl3 and in a sub-directory several layers down from this base
which will be a function of the template version information I assumes).
Manually placing the culture assemblies in that directory still does get them
located (by the .NET resource manager) but does not get them loaded (i.e., I
can't get a localized value - only the default value).
Anyone else try to solve this problem (and find a solution)?
Thanks, Mike
have a situation where I wanted to take advantage of the .NET
Internationalization features and custom cultures.
Unfortunately, I have found that while InfoPath will embedd a
dependent/referenced .NET assembly into the XSN file, it does not similarly
the related package resource files. Nor does the MS regform tool pick them up
when making a MSI file. Adding the resource assembly to the manifest doesn't
work either.
I figured that I would have to deploy the resource files separately, but
here's what I ran into. Placing the localized assembly files in the installed
directory “C:\Program Files\InfoPath Templates†does not result in loading
the appropriate culture assembly – turns out that InfoPath extracts the DLLs
from the InfoPath XSN file and then stores them in the .NET system download
cache ( C:\Documents and Settings\[profilename]\Local Settings\Application
Data\assembly\dl3 and in a sub-directory several layers down from this base
which will be a function of the template version information I assumes).
Manually placing the culture assemblies in that directory still does get them
located (by the .NET resource manager) but does not get them loaded (i.e., I
can't get a localized value - only the default value).
Anyone else try to solve this problem (and find a solution)?
Thanks, Mike