5/26/2023 0 Comments Teamcity api![]() TeamCity can act as an internal NuGet server since version 2018.2. Whohoo! (It turned out the –configuration and /property parameters were not necessary.) Test run for F:\BuildAgent\work\99eb9e3ca10dee80\AvailabilityService.IntegrationTests\bin\Release\net47\win7-圆4\(.NETFramework,Version=v4.7) Starting: "C:\Program Files\dotnet\dotnet.exe" test F:\BuildAgent\work\99eb9e3ca10dee80\AvailabilityService.IntegrationTests\ -no-build directory: F:\BuildAgent\work\99eb9e3ca10dee80 The result:ĭotnet.exe test F:\BuildAgent\work\99eb9e3ca10dee80\AvailabilityService.IntegrationTests\ -no-build (51s) It is not available as a regular option, but it is possible to use /property:Platform=%system.Platform%. Let’s try specifying the platform as an argument to dotnet test. What? I certainly didn’t want to build for platform X68. Go to for more details on managing these settings.Ĭannot run tests in process - a 32 bit process is required. Following DLL(s) do not match framework/platform settings.Ī is built for Framework 4.7 and Platform X86. NETFramework,Version=v4.7 and platform X64. Test run will use DLL(s) built for framework. Microsoft (R) Test Execution Command Line Tool Version 15.9.0Ĭopyright (c) Microsoft Corporation. Test run for F:\BuildAgent\work\99eb9e3ca10dee80\AvailabilityService.IntegrationTests\bin\Release\net47\(.NETFramework,Version=v4.7) Starting: "C:\Program Files\dotnet\dotnet.exe" test F:\BuildAgent\work\99eb9e3ca10dee80\AvailabilityService.IntegrationTests\ -configuration Release -no-build /property:Platform=圆4 directory: F:\BuildAgent\work\99eb9e3ca10dee80 New try looked more promising – this time the executable was found: So to fix that, I changed the output path in project properties from blank to bin\Debug and bin\Release respectively ( net47 is added automatically) and changed the path in TeamCity to be **\bin\%system.Configuration%\net47\ without the platform ( 圆4). When built by Visual Studio, the test binary is placed in the bin\圆4\Release\net47 folder, but when using dotnet CLI, it is placed in bin\Release\net47. ![]() ![]() By trying it locally on a development computer, I discovered that there is something funny going on with output paths. What? OK, I didn’t want to debug this plug-in, so try CLI again. An attempt was made to load a program with an incorrect format. System.BadImageFormatException: Could not load file or assembly 'AvailabilityService.IntegrationTests, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Sachabarber on Compilation Errors in ASP.NET…Ĭommandline: F:\BuildAgent\tools\xunit-runner\bin\2.4.x\ F:\BuildAgent\work\99eb9e3ca10dee80\availabilityservice.integrationtests\bin\release\net47\ -teamcity Integration/Stack Te… on Integration Test ASP.NET Core… Integration/Stack Te… on Integration Testing ASP.NET Co… Using Private Azure DevOps NuGet Feeds in Docker Build.Adding Authentication and Authorization to an ASP.NET Core Web App – the Minimalist Approach.Serving Static Content from ASP.NET Core/Kestrel.
0 Comments
Leave a Reply. |