We had similar kind of setup... We created path forwarding rules for all the sdl micro services. We treated deployer and content service separately.
Synopsis of what we did:
Configured all services on the deployer boxes using lb domain
name... this you can do by replacing server name with lb name in the
cd_storage file of the respective service and ...
I've also seen this before and believe that it is expected behaviour (as the CD code is running in a JVM), but that it's just not documented very well.
As Paul Draper says here:
Using forward slashes will make it system independent. I'd stick to that for simplicity.
However, as he also says, there are ways to allow either within the code, so this ...
Although Velu provided you with the code sample, you should understand what IsPublished() overload methods do. There are few overload methods and most of them are combinations of the same parameters (if item is published to some publication target or not, or to some target type).
What you need to take a detailed look in Velu's code is the "true" parameter ...
Try this function for checking the page is published or not:
private bool IsPublished(Page page)
if (Engine.PublishingContext?.PublicationTarget != null)
return PublishEngine.IsPublished(page, Engine.PublishingContext.PublicationTarget, true);
if (Engine.PublishingContext?.TargetType != null)
This limited mostly by how big of a request TMS API can handle.
Translation Manager send all files in one request so if it is not split, at some point TMS API will fail with timeout or something.
Another consideration, is that with big amount of tasks in one job, TMS UI can become unwieldy for people who work on TMS side.
Also, if customer uses out-scaled ...
Multimedia Types include one or more file or mime types. I don't see why you need to rely on the Multimedia Type definitions for the mime types. I guess you might try to use Tridion to manage this list of mime types to extension, but I doubt they're available (at the granularity you need) over TOM.NET. Check the documentation to be sure.
If you really want ...
Here's few things you can try:
Check your Post Build event to make sure no Microsoft.Data.Edm.dll
file is being copied manually to bin folder.
Make sure other packages don't have dependency to Microsoft.Data.Edm . Easy way to
do this is by looking at your package.config files.
Uninstall WindowsAzure.Storage and Microsoft.Data.Edm packages. Then install