You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure that the FSharpLanguageServer (in `src/FSharpLanguageServer/bin/Release/netcoreapp3.0/PLATFORM/publish`) is in your PATH. Alternatively, you can set the path to the server executable manually within your .spacemacs user-config:
131
+
Make sure that the FSharpLanguageServer (in `src/FSharpLanguageServer/bin/Release/net6.0/publish`) is in your PATH. Alternatively, you can set the path to the server executable manually within your .spacemacs user-config:
@@ -166,7 +166,7 @@ Any help is very much appreciated, issues, PR's, even just asking a question abo
166
166
167
167
Run :
168
168
169
-
-``npm install`` to setup node deps (not needed unless you plan to build the vsix extension package)
169
+
-``yarn install`` to setup node deps (not needed unless you plan to build the vsix extension package)
170
170
171
171
-``dotnet tool restore`` to install paket
172
172
@@ -178,4 +178,19 @@ Essentially you just publish the language server with ``dotnet publish -c Releas
178
178
179
179
If you want to try your newly created extension run ``code --install-extension build.vsix``
180
180
181
-
You can also change the Fsharp.debug setting in vscode which will cause the installed extension to try to build fslsp when it launches. Very handy for testing many smaller changes without republishing the extension.
181
+
## Debugging
182
+
Set the Fsharp.debug and fsharp.CustomDll path settings in vscode.
183
+
fsharp.debug: Stops execution of the langserver until you attach the vscode debugger to the dotnet instance.
184
+
fsharp.customDllPath: allows you to specify a dll to run instead of the packaged version of fslsp.
185
+
#### Live project:
186
+
- Open two instances of vscode one in a testing project, one in the fsharp-language-server project
187
+
- Make changes to the test project and then run ``dotnet publish`` in src\FSharpLanguageServer.
188
+
- use the workspace settings in the test project to set fsharp.debug to true and fsharp.customDllPath to the path of the dll you just published
189
+
- Reload the other instance of vscode and attach the debugger to monitor the changes.
190
+
191
+
#### Tests:
192
+
- Write a test for your problem
193
+
- Change "test" to "ftest"
194
+
- In the vscode debugger dropdown select ".net expecto tests"
0 commit comments