Question
Hoverstate
US
Last activity: 8 Mar 2022 12:41 EST
Openspan compiling error file name / extension too long
I'm working on a large robotics RDA project and have run into this error when trying to compile:
The specified task executable "OSC.exe" could not be run. The file name or extension is too long.
Until yesterday I had been able to run the project in debug mode, visual studio 2015 but once I went to build the project and it returned this error I have not been able to run in debug mode either.
When I initially began working on this project I ran into an error and had to reduce the length of file names enough for the compiler to work and I'm unsure if this is the same error as then. I have reduced file names considerably, but would like some verification before I take any more action in that direction.
How can I check the total file length allowed vs what we are trying to push through?
Is there another cause of this error?
Thank you.
Accepted Solution
Updated: 8 Mar 2022 12:40 EST
Pegasystems Inc.
US
@DanQuinlog Without seeing your solution and the logs, I can't be sure. It is always a good practice though to compartmentalize functionality, so if you do have parts that can be moved to their own project, that would be a good idea. That should be relatively easy to test though and should not require much time unless everything in your project is tied directly together. In my experience, I don't generally have more than 100 or so files in a project and generally keep my file names to 15 characters or less, so I don't ever see this problem.
Pegasystems Inc.
US
@DanQuinlog I believe there is a limit to how many files too. You might enable your FilePublisher for Studio and check the StudioLog. It might help understand which file is the culprit. If you cannot determine from there which file is the problem, you might need to open a support request as this one may require someone to get a hold of your solution.
Hoverstate
US
@ThomasSasnettTo check - if I take some of these automations and build a separate project with them, connecting them through activities / interaction manager would that resolve this error? Seems like it would to me but before I put in that kinda work a confirmation would be nice.
Thanks for your help so far.
Accepted Solution
Updated: 8 Mar 2022 12:40 EST
Pegasystems Inc.
US
@DanQuinlog Without seeing your solution and the logs, I can't be sure. It is always a good practice though to compartmentalize functionality, so if you do have parts that can be moved to their own project, that would be a good idea. That should be relatively easy to test though and should not require much time unless everything in your project is tied directly together. In my experience, I don't generally have more than 100 or so files in a project and generally keep my file names to 15 characters or less, so I don't ever see this problem.
Hoverstate
US
@ThomasSasnettI was able to segment some of the code to a separate project and the error resolved. We'll continue down this route.
Thank you.