x64 Enhancer failing if project reference paths are too long

6 posts, 0 answers
  1. Rick
    Rick avatar
    3 posts
    Member since:
    Dec 2011

    Posted 31 Aug Link to this post

    We have upgraded a very large project from 2015 Q1 to 2016 Q1 fluent models and everything works fine when built using a x86 configuration but when using a x64 config, we get an error that the complier was unable to find a specific .dll referenced in the project and the path that it is trying to access is always missing a character in the middle of the path. If I reduce the length of the folder names in the referenced paths (reducing the overall length of the argument passed to the enhancer.exe command), it will build fine. Please offer assistance and/or fix the bug in the x64 enhancer to allow the reference paths arguments to be longer.

    Thanks

  2. Ady
    Admin
    Ady avatar
    588 posts

    Posted 02 Sep Link to this post

    Hi Rick,

     We are sorry for the inconvenience caused. We will look into reproducing the issue and resolving it.
    While we do that it would be helpful to know at approximately what length do you start facing these issues?

    Will keep you posted on the status of this issue.

    Regards,
    Ady
    Telerik by Progress
     
    Check out the latest announcement about Telerik Data Access vNext as a powerful framework able to solve core development problems.
  3. DevCraft banner
  4. Rick
    Rick avatar
    3 posts
    Member since:
    Dec 2011

    Posted 06 Sep in reply to Ady Link to this post

    I am not sure the exact character but it seems to be around character 8315 in the enhancer execution call. Notice how the "WebGrease.dll" file name is missing the 'G'. A character seems to be trimmed from a specific location in one of the reference paths. IF I change the number of references or the path to s reference, the trimmed character changes.

    Error   374 The referenced assembly 'E:\Repo\packages\WebGrease.1.1.0\lib\Webrease.dll' could not be found.

  5. Ady
    Admin
    Ady avatar
    588 posts

    Posted 12 Sep Link to this post

    Hello Rick,

     Thank you. I am able to reproduce the problem and am analyzing it. It's rather strange that it occurs only with the x64 build. 
    I will update you on the status of the problem as soon as I have a better explanation.

    Thank you for your patience.

    Regards,
    Ady
    Telerik by Progress
     
    Check out the latest announcement about Telerik Data Access vNext as a powerful framework able to solve core development problems.
  6. Ady
    Admin
    Ady avatar
    588 posts

    Posted 16 Sep Link to this post

    Hello Rick,

     For x64 builds we call the enhancer.exe explicitly by specifying the required parameters. There seems to be a problem with a long parameter value for the '-reference' parameter.

    As a workaround you need to add the following property to the project file for the assembly that is being enhanced. You can add it after the 'EnhancerAssembly' property. This will avoid the command line parameter value from being too long.

     <ReferencesArgs> "-reference:$(SolutionDir)\packages\Telerik.DataAccess.Core.2016.1.224.1\lib\net40\Telerik.OpenAccess.35.Extensions.dll" "-reference: (add your references)</ReferencesArgs> 

    You should add all the required assembly references. 

    Do get back in case you need further assistance.

    Regards,
    Ady
    Telerik by Progress
     
    Check out the latest announcement about Telerik Data Access vNext as a powerful framework able to solve core development problems.
  7. Rick
    Rick avatar
    3 posts
    Member since:
    Dec 2011

    Posted 4 days and 16 hours ago Link to this post

    Hi,

    Do you know if any progress has been made on addressing this issue? The workaround did help, but it is a limiting solution and one of our developers recently came across this issue again (same cause).

Back to Top
DevCraft banner