This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM. Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 4 years and 11 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
davidc wrote: ↑Fri Apr 19, 2019 6:39 am
Please update to the v162 service build. It will resolve the manifest issue as well as an encoding issue introduced in the v161 service build.
The v162 build also includes a manifest template you can access via the File->New menu. The template (Custom Packager Manifest) is located under the Other category.
I have updated to the latest version
[IMAGE REMOVED BY MODERATOR]
Then modify the XML file
Snipaste_2019-04-22_17-07-42.png (42.39 KiB) Viewed 2732 times
Snipaste_2019-04-22_17-09-45.png (30.95 KiB) Viewed 2732 times
Turns out extended path support requires .NET 4.6.2 or higher. We will look into updating the .NET runtimes for the V5 hosts. They are currently using .NET 4.5.2.
This topic is 4 years and 11 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.