View previous topic :: View next topic |
Author |
Message |
Steven Sartain
Joined: 28 Apr 2021 Posts: 1
|
Posted: Wed Apr 28, 2021 2:04 pm Post subject: .NET Standard support |
|
|
I have an issue using our .NET Std projects. These are included successfully in the workspace and the resources can be completed. However, when trying to build the resx files we get an E005 (item is not longer included in the project - localized resources for this item will be be included in the project) error
I don't understand the problem as although the resx files in .NET Std are included by location (rather than existing in the actual project file), this shouldn't prevent the files from being produced from Globalizer |
|
Back to top |
|
 |
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Sat May 08, 2021 12:38 am Post subject: |
|
|
So you are getting an E005 error while trying to do a build with the "Deployed (binary) Localization" option - where Globalizer builds the localised DLLs for you? Is that correct?
Usually E005 errors occur in this situation because Globalizer is unable to locate the Invariant resource item in your compiled executable or DLL that corresponds to a given resource item in the workspace. This can happen if you changed the name of a resource after you scanned the project into the Globalizer workspace. If you can't track down the problem you can use a tool like ILSpy to decompile your executable and check that resources are being included with the names that you would expect. _________________ Infralution Support |
|
Back to top |
|
 |
|