There are version incompatibilities between Gauge and it's plugins in this project. Some features will not work as expected.

[GavinSun9527]

we have a gauge test project and upgrade from netframework to .net 8, and we want to run & debug the gauge in vs code, but I got this message when I open the project with vs code.

my vs code gauge extension version: 0.1.6
My Environment Information -----------
windows, 1.4.3, f98dd40
csharp (0.10.6), dotnet (0.5.7), html-report (4.3.1), screenshot (0.2.0), xml-report (0.5.1)

does anyone knows how check the version issue?

[chadlwilson]

Same as getgauge/gauge-vscode#945 ?

[GavinSun9527]

yes
I have updated to Gauge 1.6.6, but it still has the same issue

and I tried click run Scenario , I will got these message from output

Running tool: gauge.cmd run --hide-suggestion --simple-console c:\xxxxxxxxx (mark)\ProcessPaymentTests.spec:9
Building project: c:\xxxxxxxxxxxxxx.Gauge.Tests.csproj
c:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe c:\xxxxxxxxxxxx.Tests.csproj /t:Build /m /nodeReuse:False /v:q /p:RestorePackages="False" /p:OutputPath="c:\xxxxxxxxxx\gauge_bin" /p:Platform="Any CPU" /p:Configuration="Debug" /logger:Fake.MsBuildLogger+ErrorLogger,"C:\Users\gsun\AppData\Roaming\gauge\plugins\csharp\0.10.6\bin\FakeLib.dll"
Microsoft (R) Build Engine version 4.8.9037.0
[Microsoft .NET Framework, version 4.0.30319.42000]
Copyright (C) Microsoft Corporation. All rights reserved.
c:\xxxxxxxxxxxxxxxxx.Gauge.Tests.csproj(1,1): error MSB4041: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 f

do you know why it is still built with Microsoft.NET\Framework\v4.0.30319\MSBuild.exe ？ I have upgraded to .NET 8 for my project

[chadlwilson]

Please don't open/discuss the same issue in two different places. Let's stick to one place please.

[GavinSun9527]

sure,let's discuss here and let me close another the issue

[GavinSun9527]

Hi @chadlwilson
And another case is , I have another gauge test project, and I upgrade from NET Stardand 2.1 to .net 8, before upgrade all test cases can run success in vs code.

After upgrade (and upgrade the gauge version) , almost spec are failed

fail: Grpc.AspNetCore.Server.ServerCallHandler[6]
Error when executing service method 'ValidateStep'.
System.InvalidOperationException: Sequence contains no matching element
at System.Linq.ThrowHelper.ThrowNoMatchException()
at System.Linq.Enumerable.First[TSource](IEnumerable1 source, Func2 predicate)
at Gauge.Dotnet.AssemblyLoader.GetMethods(LibType type) in /home/runner/work/gauge-dotnet/gauge-dotnet/src/AssemblyLoader.cs:line 53
at Gauge.Dotnet.Models.HookRegistry..ctor(IAssemblyLoader assemblyLoader) in /home/runner/work/gauge-dotnet/gauge-dotnet/src/Models/HookRegistry.cs:line 42
at Gauge.Dotnet.HookExecutor..ctor(IAssemblyLoader assemblyLoader, IReflectionWrapper reflectionWrapper, Object classInstanceManager, IExecutionInfoMapper mapper) in /home/runner/work/gauge-dotnet/gauge-dotnet/src/HookExecutor.cs:line 30

And this is a failed spec file content, Each step (start with *) line has a red wavy underline

# Customer Tests
* Set "Sandbox" As Current Merchant

------------------------------------------------- Post Validation Start ---------------------------------------------------
## Run multiple create customer successfully

tags: testCustomer

   |PropertyName|PropertyValue|
   |------------|-------------|
   |reference   |[NEWID]      |
   |reference   |             |
   |email       |             |
* Generate and send default Create Customer Request for the "test" Merchant with Overriden Values

   |Property      |Value          |
   |--------------|---------------|
   |<PropertyName>|<PropertyValue>|
* Verify Create Customer Response Successful With ResultStatus "ok"

[chadlwilson]

As I said before, maybe because you still have the gauge-csharp plugin installed and it is using that, or maybe because you haven't correctly converted your project to dotnet core, but I don't know.

[GavinSun9527]

Sure, I got your point, but in vs code "TERMINAL" tab, if I run the command "dotnet build -c Release" in the project folder path, it can build success
like as the follows

MSBuild version 17.8.3+195e7f5a3 for .NET
  Determining projects to restore...
  All projects are up-to-date for restore.
...

[chadlwilson]

Did you remove the dotnet-csharp plugin and see if it's any different?

[GavinSun9527]

Okay, let me try

today I got these message from vs code output when I open the gauge project

[Error - 10:50:00 AM] An error occurred. Refer lsp.log for more details.
[Info  - 10:50:00 AM] Connection to server got closed. Server will restart.
true
[Error - 10:50:02 AM] An error occurred. Refer lsp.log for more details.
[Info  - 10:50:02 AM] Connection to server got closed. Server will restart.
true
[Error - 10:50:03 AM] An error occurred. Refer lsp.log for more details.
[Info  - 10:50:03 AM] Connection to server got closed. Server will restart.
true

check the lsp.log

15-04-2024 10:50:00.957 [Gauge] [INFO] Starting language runner
15-04-2024 10:50:01.813 [dotnet] [INFO] MSBuild version 17.8.3+195e7f5a3 for .NET
15-04-2024 10:50:01.824 [dotnet] [INFO] MSBUILD : error MSB1006: Property is not valid.
15-04-2024 10:50:01.824 [dotnet] [INFO] Switch:  LLC\Desktop\TestUpgrade\eWAY.GlobalRapidAPI.Gauge.Tests\gauge_bin
15-04-2024 10:50:01.824 [dotnet] [INFO] For switch syntax, type "MSBuild -help"
15-04-2024 10:50:02.287 [Gauge] [INFO] LangServer: reading on stdin, writing on stdout
15-04-2024 10:50:02.290 [Gauge] [CRITICAL] notif #0: initialized: runtime error: invalid memory address or nil pointer dereference
goroutine 26 [running]:
runtime/debug.Stack(0xc00065d780, 0x1261480, 0x1822a30)
	C:/hostedtoolcache/windows/go/1.16.13/x64/src/runtime/debug/stack.go:24 +0xa5
github.com/getgauge/gauge/api/lang.recoverPanic(0xc000154550)
	D:/a/gauge/gauge/api/lang/server.go:308 +0x65
panic(0x1261480, 0x1822a30)
	C:/hostedtoolcache/windows/go/1.16.13/x64/src/runtime/panic.go:965 +0x1c7
github.com/getgauge/gauge/runner.(*GrpcRunner).ExecuteMessageWithTimeout(...)
	D:/a/gauge/gauge/runner/grpcRunner.go:195
github.com/getgauge/gauge/api/lang.globPatternRequest(0x4, 0x4, 0x1205aa0)
	D:/a/gauge/gauge/api/lang/runner.go:87 +0x7e
github.com/getgauge/gauge/api/lang.registerRunnerCapabilities(0x1431c40, 0xc0000ce000, 0x14347b0, 0xc0000a6088, 0x0, 0x0)
	D:/a/gauge/gauge/api/lang/capabilities.go:110 +0x54
github.com/getgauge/gauge/api/lang.(*LangHandler).Handle(0x18803c8, 0x14347b0, 0xc0000a6088, 0x1431c40, 0xc0000ce000, 0xc000154550, 0xc00000bf08, 0xb36066, 0xc00008e1e0, 0xc0001648a0)
	D:/a/gauge/gauge/api/lang/server.go:76 +0x649
github.com/getgauge/gauge/api/lang.(*LangHandler).handle(0x18803c8, 0x14347b0, 0xc0000a6088, 0xc0000ce000, 0xc000154550, 0x0, 0x0, 0x0, 0x0)
	D:/a/gauge/gauge/api/lang/server.go:60 +0xac
github.com/sourcegraph/jsonrpc2.(*HandlerWithErrorConfigurer).Handle(0xc000508120, 0x14347b0, 0xc0000a6088, 0xc0000ce000, 0xc000154550)
	C:/Users/runneradmin/go/pkg/mod/github.com/sourcegraph/jsonrpc2@v0.0.0-20200429184054-15c2290dcb37/handler_with_error.go:21 +0x79
created by github.com/getgauge/gauge/api/lang.lspHandler.Handle
	D:/a/gauge/gauge/api/lang/server.go:55 +0x72

I tried to create a new gauge project in vs code, but still get this error message, do you know what happened？

[chadlwilson]

I don't know, but it looks like the vscode plugin is not talking correctly to the gauge server. (the LSP is the bit that understands the language syntax and works with VSCode to make VSCode Gauge-aware)

I would make sure you are on latest/recent versions of all the pieces e.g VSCode 1.88.1, Gauge 1.6.6, gauge-vscode 0.1.6 and gauge-dotnet 0.5.7. That looks like an old version of Gauge to me.