I have the prjhelper merge module for DesktopEdition v8.0.0.300. When adding it to an installer project and trying to build I get an error describing that the path to extract the merge file (or decompress to) is too long for windows to create the directory.
"The file path is longer than the limit set by the operating system. Change the build location of the current release to a shorter path to resolve this issue."
Looking at the description, I see paths that the merge module is trying to use with huge number of characters.
…\MergeModules\MapSuitePrjHelper.BCFFE32A_1733_4DC2_9FAD_39C4DC6D3E20\COORDINATE_AXIS.CSV.BCFFE32A_1733_4DC2_9FAD_39C4DC6D3E20
Can you please check this merge module? I am not ready to upgrade to 9.0.
Thanks,
Damian
PrjHelper Merge Module Problem
Hi Damian,
I am sorry I can’t reproduce your issue, I test “MapSuitePrjHelper.msm” with Microsoft setup project and Wix installer project, but it can’t be reproduced.
I don’t know your installer tool set, could you please tell me your installer tool set name or sent us a simple sample?
Thanks,
Hi Don,
I am using Install Shield with VS2013.
Thanks,
Damian
Hi Damian,
I am sorry we hadn’t use this Install Shield for it, I will download that and test whether I can reproduce it.
Regards,
Don
Hi Damian,
Today I use a Eval InstallShield Limited Edition in VS2012, only append the MapSuitePrjHelper.msm from 8.0, and it succeed deploy the dlls into C:\Windows\SysWOW64\Map Suite 8.0\MapSuitePrjHelper folder.
So we still cannot reproduced your issue.
Please let us know more about it and please test other version merge module and see whether they works.
Regards,
Don
Hi Don,
Apparently, the path to my VS Installer project output for the merge module name with extra characters (shown above) was too long for VS (or windows?) to use to successfully stage the output. I renamed my installer to a shorter name and it built successfully.
Regards,
Damian
Great. Please let us know if any other questions.
Thanks,
Troy