Skip to main content
deleted 1 character in body
Source Link
Eric Alexander
  • 43.3k
  • 10
  • 54
  • 93

I have a feature in which several aspx pages are deployed to the pages library of a 2010 environment. These are fairly standard aspx pages in that they are attaching to the default maser page, have placeholder main and placeholder additionalpagehead content regions, and have the page content publishing control in them. They have dataview web parts and jQuery in them.

These pages now need to be localized in some other languages. I can add resource files to the solution and put them into place like:

<span class="form-headers"><b><asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>"/></b></span>

This results in an error as such:

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Literal expressions like '<%$Resources:FriendsLocs,FullName%>' are not allowed. Use <asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>" /><asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>" /> instead.

I've tried putting the resources files in the App_GlobalResources and every other place imaginable as mentioned in the various articles on localizing SharePoint features. I cannot get this to work properly.

So my question is how can you localize pages that get deployed to the Pages library or do I have to take some other approach to localize these files?

I have a feature in which several aspx pages are deployed to the pages library of a 2010 environment. These are fairly standard aspx pages in that they are attaching to the default maser page, have placeholder main and placeholder additionalpagehead content regions, and have the page content publishing control in them. They have dataview web parts and jQuery in them.

These pages now need to be localized in some other languages. I can add resource files to the solution and put them into place like:

<span class="form-headers"><b><asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>"/></b></span>

This results in an error as such:

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Literal expressions like '<%$Resources:Friends,FullName%>' are not allowed. Use <asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>" /> instead.

I've tried putting the resources files in the App_GlobalResources and every other place imaginable as mentioned in the various articles on localizing SharePoint features. I cannot get this to work properly.

So my question is how can you localize pages that get deployed to the Pages library or do I have to take some other approach to localize these files?

I have a feature in which several aspx pages are deployed to the pages library of a 2010 environment. These are fairly standard aspx pages in that they are attaching to the default maser page, have placeholder main and placeholder additionalpagehead content regions, and have the page content publishing control in them. They have dataview web parts and jQuery in them.

These pages now need to be localized in some other languages. I can add resource files to the solution and put them into place like:

<span class="form-headers"><b><asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>"/></b></span>

This results in an error as such:

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Literal expressions like '<%$Resources:Locs,FullName%>' are not allowed. Use <asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>" /> instead.

I've tried putting the resources files in the App_GlobalResources and every other place imaginable as mentioned in the various articles on localizing SharePoint features. I cannot get this to work properly.

So my question is how can you localize pages that get deployed to the Pages library or do I have to take some other approach to localize these files?

added 22 characters in body
Source Link
Eric Alexander
  • 43.3k
  • 10
  • 54
  • 93

I have a feature in which several aspx pages are deployed to the pages library of a 2010 environment. These are fairly standard aspx pages in that they are attaching to the default maser page, have placeholder main and placeholder additionalpagehead content regions, and have the page content publishing control in them. They have dataview web parts and jQuery in them.

These pages now need to be localized in some other languages. I can add resource files to the solution and put them into place like:

<span class="form-headers"><b><asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>"/></b></span>

This results in an error as such:

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Literal expressions like '<%$Resources:Friends,FullName%>' are not allowed. Use <asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>" /> instead.

I've tried putting the resources files in the App_GlobalResources and every other place imaginable as mentioned in the various articles on localizing SharePoint features. I cannot get this to work properly.

So my question is how can you localize pages that get deployed to the Pages library or do I have to take some other approach to localize these files?

I have a feature in which several aspx pages are deployed to the pages library. These are fairly standard aspx pages in that they are attaching to the default maser page, have placeholder main and placeholder additionalpagehead content regions, and have the page content publishing control in them. They have dataview web parts and jQuery in them.

These pages now need to be localized in some other languages. I can add resource files to the solution and put them into place like:

<span class="form-headers"><b><asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>"/></b></span>

This results in an error as such:

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Literal expressions like '<%$Resources:Friends,FullName%>' are not allowed. Use <asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>" /> instead.

I've tried putting the resources files in the App_GlobalResources and every other place imaginable as mentioned in the various articles on localizing SharePoint features. I cannot get this to work properly.

So my question is how can you localize pages that get deployed to the Pages library or do I have to take some other approach to localize these files?

I have a feature in which several aspx pages are deployed to the pages library of a 2010 environment. These are fairly standard aspx pages in that they are attaching to the default maser page, have placeholder main and placeholder additionalpagehead content regions, and have the page content publishing control in them. They have dataview web parts and jQuery in them.

These pages now need to be localized in some other languages. I can add resource files to the solution and put them into place like:

<span class="form-headers"><b><asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>"/></b></span>

This results in an error as such:

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Literal expressions like '<%$Resources:Friends,FullName%>' are not allowed. Use <asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>" /> instead.

I've tried putting the resources files in the App_GlobalResources and every other place imaginable as mentioned in the various articles on localizing SharePoint features. I cannot get this to work properly.

So my question is how can you localize pages that get deployed to the Pages library or do I have to take some other approach to localize these files?

Source Link
Eric Alexander
  • 43.3k
  • 10
  • 54
  • 93

Proper method of localizing aspx pages

I have a feature in which several aspx pages are deployed to the pages library. These are fairly standard aspx pages in that they are attaching to the default maser page, have placeholder main and placeholder additionalpagehead content regions, and have the page content publishing control in them. They have dataview web parts and jQuery in them.

These pages now need to be localized in some other languages. I can add resource files to the solution and put them into place like:

<span class="form-headers"><b><asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>"/></b></span>

This results in an error as such:

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Literal expressions like '<%$Resources:Friends,FullName%>' are not allowed. Use <asp:Literal runat="server" Text="<%$Resources:Locs,FullName%>" /> instead.

I've tried putting the resources files in the App_GlobalResources and every other place imaginable as mentioned in the various articles on localizing SharePoint features. I cannot get this to work properly.

So my question is how can you localize pages that get deployed to the Pages library or do I have to take some other approach to localize these files?