Issues with running solution build using Azure Build Pipeline

Posted by: adrian on 27 April 2019, 8:56 pm EST

    • Post Options:
    • Link

    Posted 27 April 2019, 8:56 pm EST

    Hi,

    I’ve set up an Azure build agent on one of my Azure servers.

    On my development machine I can make a change, build the code, run the solution and all works well.

    When I check in my code to vsts the Build Pipeline gets active but fails with the following message:

    error BC32207: The project currently contains references to more than one version of 'C1.Win.4', a direct reference to version 4.0.20191.359 and an indirect reference to version 4.0.20191.363
    ```.
    
    I have installed C1 on the build server and it is correctly licensed.  I have also installed Visual Studio on the build server and can build and run the solution from there.  I am at a loss as to how to fix this issue for the build pipeline.
    
    Any help would be greatly appreciated.
    
    Cheers.
    Adrian.
  • Posted 29 April 2019, 4:06 am EST

    Hello,

    Thank you for sharing the exception description. It looks like the ComponentOne version installed over your machine and over the build server are different (Though, both have 2019v1 ComponentOne installed but one has been upgraded to use the hotfix version *.363).

    So, please upgrade ComponentOne on the machine that’s running *.20191.359 version to make sure both the machine run the same ComponentOne version. This would avoid issues as many assemblies internally refer other assemblies like C1.Win.

    Also, I’d suggest you to manually delete the Bin/Obj folders in your application over build agent and then rebuild your project.

    Thanks,

    Ruchir

  • Posted 4 May 2019, 4:31 am EST

    Thanks for your reply, But I don’t think this is the case. I’ve run C1Live on my local machine and on the Azure build server and both report version 4.0.20191.363 is installed. And in any event when the build starts on the build machine it starts with an empty folder. it gets all the files from tfs and starts the build.

    I’ve checked the references in the project and they refer to 4.0.20191.363 so I’m a little stuck to see why *.359 version is coming from.

    Any ideas?

  • Posted 6 May 2019, 4:02 am EST

    Adrian,

    Could you please confirm that the ‘licenses.licx’ file present in your project contains ‘4.0.20191.363’ as the version? If not, please remove the Version, Culture and PublicKeyToken from all the entries in that file and re-build the project.

    Thanks,

    Ruchir

  • Posted 9 May 2019, 3:56 am EST

    Hi,

    I have checked the licenses.licx files in all the projects of my solution and none contain the Culture or PublicKeyToken information, they all have entries like

    C1.Win.Layout.C1DashboardLayout, C1.Win.DashboardLayout.4
    C1.Win.Olap.C1OlapGrid, C1.Win.Olap.4
    C1.Win.Olap.C1OlapPage, C1.Win.Olap.4
    C1.Win.TreeView.C1TreeView, C1.Win.TreeView.4
    

    If I Remote into the Azure server I’m using as a build machine and run Visual studio it builds correctly. It only fails when the build is triggered by Devops pipeline either automatically or manually.

    Adrian

  • Posted 10 May 2019, 2:43 am EST

    Hello Adrian,

    Could you please confirm do you have any other products of C1 are installed on Azure. If yes, Could you please check after updating all the product from the C1Live.

    Also, please check the C1Win.dll location and see from where it is picked “C1Win.dll”

    Thanks.

  • Posted 26 May 2019, 5:09 am EST

    Hi mohitg,

    Sorry it’s taken a while for me to circle back to this. I updated my installation with C1Live see the zipped image .C1versions.zip All is not up to date.

    Problem still exists. I’ve attached the build log from the build server. Are you able to figure out what is occurring.

    log_7_85 (1).zip

    Thanks.

    Adrian.

  • Posted 27 May 2019, 4:34 am EST

    Hello Adrian,

    Please see the following log:

    2019-05-26T09:01:08.3165485Z ##[warning]C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2114,5): Warning MSB3277: Found conflicts between different versions of “C1.Win.4” that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

    2019-05-26T09:01:08.3166365Z C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2114,5): warning MSB3277: Found conflicts between different versions of “C1.Win.4” that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed. [C:\agent_work\2\s\Captell_Common\Captell_Common.vbproj]

    2019-05-26T09:01:08.3167574Z ##[warning]C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2114,5): Warning MSB3277: Found conflicts between different versions of “C1.Win.C1FlexGrid.4” that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

    2019-05-26T09:01:08.3168069Z C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2114,5): warning MSB3277: Found conflicts between different versions of “C1.Win.C1FlexGrid.4” that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed. [C:\agent_work\2\s\Captell_Common\Captell_Common.vbproj]

    There is still mismatch version in your project:

    Please do the following steps;

    1: Delete the bin/Obj of the Project

    2. Open the solution explorer and right click and remove each one of the C1 components. Re-add them by right clicking on References and selecting Add Reference (they can be located selecting Browse and navigating to the C:\Program Files (x86)\ComponentOne\WinForms Edition\bin\v4.0 folder).

    1. For each of the new C1 components, you added to your references, change the Specific Version property to False.

    Hope it helps.

    Thanks.

  • Posted 1 June 2019, 4:33 am EST

    Hi,

    Thanks for the reply. I’ve done as you suggest and on my development machine all projects in the solution have correct references to the latest version with Specific Version property all set to False.

    However, when I try the build server build the references are all messed up.

    This is what I did.

    • “On the development machine followed your steps above, then double checked all references. So far so good.”

    • “I checked in the updated solution and all it’s projects.”

    • “On my build machine I fired up VS and checked out the solution. All references still look fine”

    • “I created a new build pipeline using the solution in TFS”

    • “Queued the pipeline and it failed with the same or similar errors”

    So I checked the working folder for the Build pipeline where it checked out the code to. I examined the projects in here and the references are now very strange. For instance, many of the C1.Win.4 references point to C:\Program Files (x86)\ComponentOne\ASP.NET Web Forms Edition\bin\v4\C1.Win.4.dll

    Instead of the WinForms version.

    Do you know if there is anything more I can try?

  • Posted 1 June 2019, 4:37 am EST - Updated 4 October 2022, 1:11 am EST

    Here’s a snip of the references in the main project of the solution checked out by the build pipeline. You can see a bunch of them are pointing at ASP.NET Web Forms

  • Posted 1 June 2019, 4:40 am EST - Updated 4 October 2022, 1:11 am EST

    And here is a snip of the references from the same project if I manually check it out on the build server.

    As you can see they all correctly reference WinForms version.

    I can’t figure out how the build pipeline version can be referencing the wrong version

  • Posted 3 June 2019, 6:45 am EST

    Hello,

    Can you please check after manually replacing all dlls in “C:\Program Files (x86)\ComponentOne\ASP.NET Web Forms Edition\bin\v4” with the dlls present in

    “C:\Program Files (x86)\ComponentOne\WinForms Edition\bin\v4.0” folder.

    Thanks.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels