Hi,
I want to do the localization for the filter options in WebDataGrid.I found the document with the step by step instructions to change the file WebDataGridStrings.resx
But in Version 10.3 the strings are in the file WebDataGridStrings_runtime.resx.
I tried to do the same with this file, but no luck.
Have someone any ideas whats wrong?
Thanks.
Jürgen
Thank you for the link. It will be usefull for me. It was a question in suspend in my team.
But I don't find any point related to my initial question :p
Are you sure for the link ?
Hello,
In this following forum thread one of our developers mentions there are two approaches for using the resource assembly: build on the server or place the assembly in the GAC.
http://help.infragistics.com/NetAdvantage/ASPNET/Current/CLR4.0/?page=WebDataGrid_Handling_Server_Side_Exceptions_Using_AJAX.html
It sounds like the second approach is the one you want. You should first build the localization assembly on your development machine. Once this is done copy it over to your server and use gacutil to add it to the Global Assembly Cache of the server. For more information on using gacutil please see the following MSDN article:
http://msdn.microsoft.com/en-us/library/ex0ss12c(v=vs.80).aspx
Please let me know if I can be of any further assistance with this matter.
I want to localize filters (Clear All etc) in my WebDataGrid, and after a research in this forum I found the document step by step.
But we got a problem, we cant build on the server (don't ask why please, we just can't). How can we do to work around the problem ?
Thanks you very much.
Hi grueningd,
could you attach this application so we can look into it.
Thank you
We have created a small test application using Visual Studio 2010. Using target framework .NET3.5 (ASP.NET2.0) the filter texts were not displayed in a localized manner, with target framework .NET4.0, however, it functioned as expected.Thx
We have created a small test application using Visual Studio 2010.
Using target framework .NET3.5 (ASP.NET2.0) the filter texts were not displayed in a localized manner, with target framework .NET4.0, however, it functioned as expected.Thx