They are left over from features that have been removed and can be ignored. The CommerceManagerLink setting is used however.
Thanks, would be nice to remove obsolete parts from config files, it misleads a bit.
Yes of course, it was a mistake to leave them in there and I have registered it as a bug. Thanks for bringing it to our attention!
I've post similar question in another thread (http://world.episerver.com/Modules/Forum/Pages/Thread.aspx?id=78804&epslanguage=en)
Could you please take a look?
Hi,
Those keys, although legacy, are used for upgrading script. They should be here :).
/Q
Are these still needed? Quite a bit of time has passed since this was last answered. They pose quite a bit of a problem when using automated deployment solutions when deploying to new folders every time. And in general, getting rid of config is a good feeling.
We are updating our commerce manager via nugets these days anyways, so I'm just guessing the SharedPath-setting is utterly obsolete anyways.
Well, we switched to nuget approach and dig out old installation files, so it should be safe to remove those settings.
Regards.
/Q
There are follwoing application settings in my front site web.config (created by Deployment center):
<add key="CommerceManagerBinPath" value="C:\EPiServer75\CommerceManager\wwwroot\Bin" />
<add key="CommerceManagerSharedPath" value="C:\EPiServer75\CommerceManager\eCommerceFramework\5.3\" />
<add key="CommerceManagerApplicationName" value="CommerceManager" />
Does anybody know what they for? I can't find usage of them.