-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sitecore ship throws MissingMethodException on SC9 #78
Comments
It works if you build the sources from this branch: https://github.com/dharnitski/Sitecore.Ship/tree/feature/sitecore82 with dlls from Sitecore 9. |
I have downloaded the branch(sitecore82) and with sitecore 9 dlls(Sitecore.Client.dll
Any idea sitecore ship supporting the sitecore 9 version? |
You should change target framework to 4.6.2 in Sitecore.Ship projects too |
Thanks working now. Issue 2: After upgrade the framework 4.6.2, there is no logs written in the sitecore log file about sitecore ship.(failure or success). |
@Amarapathi - i was also getting the same error and could not resolve this. Finally i had to switch to TDS package deployer module. |
@prabhatsingh2011 Could you please provide me the reference link which you have refered for the TDS package deployer. |
@Amarapathi - here it is. I have used Octopus and VSTS. if required i can share my step templates(powershell scripts) for you to use. https://www.teamdevelopmentforsitecore.com/Blog/sitecore-package-deployer |
@prabhatsingh2011 Yes please share the steps which you used. Thanks, |
@prabhatsingh2011 Can you please share the steps. I have to use same one with Octopus and Teamcity. Thanks, |
Hi
When trying to use Sitecore ship to install packages on a Sitecore 9 installation I'm getting the following error:
Method not found: 'Void Sitecore.Update.Installer.XmlEntrySerializer.Serialize(System.Collections.Generic.List`1<Sitecore.Update.Installer.ContingencyEntry>, System.IO.Stream)'.
I'm guessing they changed something in 9 that breaks functionality. Any ideas?
Thanks
The text was updated successfully, but these errors were encountered: