Sysprogs forums › Forums › VisualGDB › VisualGDB running as TFS remote build failure
Tagged: VISUALGDB TFS REMOTE BUILD
- This topic has 9 replies, 2 voices, and was last updated 5 years, 1 month ago by support.
-
AuthorPosts
-
March 14, 2019 at 16:34 #24254terry_short29Participant
I tried to set up a remote build on our TFS build agent and I think I had it working before but now it fails every time with the following message.
VisualGDB version 5.3.18.1973 System.InvalidOperationException System.InvalidOperationException: Showing a modal dialog box or form when the application is not running in UserInteractive mode is not a valid operation. Specify the ServiceNotification or DefaultDesktopOnly style to display a notification from a service application. at System.Windows.Forms.MessageBox.ShowCore(IWin32Window owner, String text, String caption, MessageBoxButtons buttons, MessageBoxIcon icon, MessageBoxDefaultButton defaultButton, MessageBoxOptions options, Boolean showHelp) at d81.m(String a, Object[] b) at oh1.f_4(ck1 a) at p52..ctor(VisualGDBProjectSettings2 b, mc c, IDELevelProjectInfoForBuilding d, uz a) at VisualGDB.MSBuild.BuildHelper..ctor(String vgdbSettingsFile, IDELevelProjectInfoForBuilding info) at Sysprogs.build.tasks.shared.LaunchVisualGDB.Execute() C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\Targets\external.targets(5,3): Error : Showing a modal dialog box or form when the application is not running in UserInteractive mode is not a valid operation. Specify the ServiceNotification or DefaultDesktopOnly style to display a notification from a service application. 2>C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\Targets\external.targets(5,3): error : Showing a modal dialog box or form when the application is not running in UserInteractive mode is not a valid operation. Specify the ServiceNotification or DefaultDesktopOnly style to display a notification from a service application. [C:\BuildAgentV2\_work\31\s\TDS07KB.vcxproj] 2>Done Building Project "C:\BuildAgentV2\_work\31\s\TDS07KB.vcxproj" (default targets) -- FAILED. 1>Done Building Project "C:\BuildAgentV2\_work\31\s\TDS07KB.sln" (default targets) -- FAILED.
Are there some build variables I can set to fix this?
- This topic was modified 5 years, 1 month ago by support. Reason: formatting
March 14, 2019 at 18:35 #24256supportKeymasterHi,
This looks like a bug that was fixed in the latest v5.4 release. Please try updating to it.
March 15, 2019 at 09:45 #24281terry_short29ParticipantChanged the error, now get…
2019-03-15T08:35:59.8663061Z Build started 15/03/2019 08:35:59.
2019-03-15T08:36:00.5850640Z 1>Project “C:\BuildAgentV2\_work\31\s\TDS07KB.sln” on node 1 (default targets).
2019-03-15T08:36:00.5850640Z 1>ValidateSolutionConfiguration:
2019-03-15T08:36:00.5850640Z Building solution configuration “Release|VisualGDB”.
2019-03-15T08:36:01.6944518Z 1>Project “C:\BuildAgentV2\_work\31\s\TDS07KB.sln” (1) is building “C:\BuildAgentV2\_work\31\s\TDS07KB.vcxproj” (2) on node 1 (default targets).
2019-03-15T08:36:01.6944518Z 2>PrepareFastUpToDataCheckDatabase:
2019-03-15T08:36:01.6944518Z VisualGDB version 5.4.103.3000
2019-03-15T08:36:01.6944518Z System.ArgumentException
2019-03-15T08:36:01.6944518Z System.ArgumentException: Path cannot be the empty string or all whitespace.
2019-03-15T08:36:01.6944518Z at System.IO.Directory.CreateDirectory(String path)
2019-03-15T08:36:01.6944518Z at Sysprogs.Build.Tasks.InitializeFastUpToDateCheckFile.Execute()
2019-03-15T08:36:01.7569552Z ##[error]C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\Targets\FastUpToDateCheck.targets(5,2): Error : Path cannot be the empty string or all whitespace.
2019-03-15T08:36:01.7569552Z 2>C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\Targets\FastUpToDateCheck.targets(5,2): error : Path cannot be the empty string or all whitespace. [C:\BuildAgentV2\_work\31\s\TDS07KB.vcxproj]
2019-03-15T08:36:01.7569552Z 2>Done Building Project “C:\BuildAgentV2\_work\31\s\TDS07KB.vcxproj” (default targets) — FAILED.
2019-03-15T08:36:01.7569552Z 1>Done Building Project “C:\BuildAgentV2\_work\31\s\TDS07KB.sln” (default targets) — FAILED.
2019-03-15T08:36:01.7569552Z
2019-03-15T08:36:01.7569552Z Build FAILED.March 15, 2019 at 17:24 #24284supportKeymasterThis looks like you have updated the VisualGDB binaries, but might be still using the MSBuild targets files from the old version. Please double-check that the project builds with VisualGDB 5.4 from Visual Studio and that the SysprogsPlatform.targets and other MSBuild files on the TFS machine match the corresponding files on the machine where the build succeeds.
March 18, 2019 at 09:32 #24313terry_short29ParticipantI tried running the build from within VS on the remote build machine succeeded. Building with V5.4 on my development machine worked. What else can I check? Can I turn up some debugging or something?
March 19, 2019 at 03:04 #24338supportKeymasterYes, please try running msbuild with the -verbosity:diag switch and either attach the diagnostic log here, or send it via our support form. It should explain what is going on.
March 19, 2019 at 09:42 #24342terry_short29ParticipantBuild log as requested…
Attachments:
You must be logged in to view attached files.March 20, 2019 at 18:05 #24387supportKeymasterThanks, looks like your project did not have the $(IntDir) variable set and that triggered an unexpected path format inside VisualGDB. We have added a check for it in the following build: VisualGDB-5.4.103.3019.msi
March 21, 2019 at 09:49 #24390terry_short29ParticipantI checked and the project does have IntDir set on my development PC however, I tried it with your new version and it seems to build ok now.
March 21, 2019 at 17:49 #24399supportKeymasterNo problem. The IntDir might have been set in a different order then (i.e. before VisualGDB computes the paths of some intermediate files). Either way, we have added the checks for this case in the new build, so unless you encounter further problems, the project should be good to go.
-
AuthorPosts
- You must be logged in to reply to this topic.