Am 04.04.2018 um 20:34 schrieb greatsam4sure:
> On Tuesday, 3 April 2018 at 23:02:42 UTC, WebFreak001 wrote:
>> new code-d (D extension for vscode) and serve-d (Language Server
>> Protocol server for it) release
>>
>> See the CHANGELOG in vscode, or on https://github.com/Pure-D/code-d/blob/master/CHANGELOG.md
>>
>> Today massive improvements towards windows installation have been made and it should be a lot more painless now.
>>
>> Big thanks to Mike Franklin for helping me debug the windows installation, making this available very quickly and to p0nce for compiling the windows release because my VM wasn't working for this anymore.
>>
>> As now the extension is in stable and no longer requires the beta branch a lot of issues have been fixed and old ones which are probably no longer valid closed. If you find any issue please create a new one or reopen if you have an old issue.
>>
>> Here are some of my personal highlights:
>>
>> https://wfr.moe/fmEfTw.png - documentation inside autocompletion
>> https://wfr.moe/fmq4Da.png - import timing
>> https://wfr.moe/fmqCNt.png https://wfr.moe/fmqh3H.png - simple
>> implement interface action
>> n/a - everything compiles and installs without reloads or cumbersome
>> dialogs, just install from marketplace, wait for the installation
>> which should be very quick, especially with prebuilt binaries and
>> start coding without any distractions!
>> https://wfr.moe/fmzcS8.png - dub dependency browser
>> n/a - automatic insertion of a module statement on rename and file
>> creation
>>
>> code-d beta and code-d are therefore on the same release right now, but code-d beta will still be continuing to get features early.
>>
>> eager to hear your feedback, though gonna go to sleep for now.
>>
>> Planned for next release is internationalizing the final few messages which are in the code-d part, all serve-d parts have already been translated to German and Japanese and are determined by vscode language.
> 
> Thanks a lot! It works fine for me now in windows 10
> 
> steps
> 
> * I delete  C:\Users\Greatsam\AppData\Roaming\code-d folder
> **Restart visual studio code at least twice with internet connect on to
> enable code-d serve-d to download DCD
> It shows dcd successfully installed with many deprecation message
> ***I used sdl in my dub project with the flags: dflags
> "-transition=intpromote" platform="dmd"
> 
> I don't know if this have any effect. This help me to avoid some errors from the compilers
> 
> 
> 
> Thanks all who make this a success on windows. It is a great achievement in moving D forward.
I just tried to get this to work, too, but I was not able to get it to work correctly. It seems that running dub fails somehow:

2018-04-09T23:40:19.281:source\app.d:main:196 Setting language to de
2018-04-09T23:40:19.281:source\app.d:main:205 Features fulfilled
2018-04-09T23:40:19.283:source\app.d:main:211 Started reading from stdin
2018-04-09T23:40:19.283:source\app.d:main:215 RPC started
2018-04-09T23:40:19.294:source\app.d:main:226 Has Message
2018-04-09T23:40:19.294:source\app.d:main:228 Message: RequestMessage(0,
"initialize",
{"capabilities":{"textDocument":{"codeAction":{"dynamicRegistration":true},"codeLens":{"dynamicRegistration":true},"completion":{"completionItem":{"commitCharactersSupport":true,"snippetSupport":true},"dynamicRegistration":true},"definition":{"dynamicRegistration":true},"documentHighlight":{"dynamicRegistration":true},"documentLink":{"dynamicRegistration":true},"documentSymbol":{"dynamicRegistration":true},"formatting":{"dynamicRegistration":true},"hover":{"dynamicRegistration":true},"onTypeFormatting":{"dynamicRegistration":true},"rangeFormatting":{"dynamicRegistration":true},"references":{"dynamicRegistration":true},"rename":{"dynamicRegistration":true},"signatureHelp":{"dynamicRegistration":true},"synchronization":{"didSave":true,"dynamicRegistration":true,"willSave":true,"willSaveWaitUntil":true}},"workspace":{"applyEdit":true,"didChangeConfiguration":{"dynamicRegistration":true},"didChangeWatchedFiles":{"dynamicRegistration":true},"executeCommand":{"dynamicRegistration":true},"symbol":{"dynamicRegistration":true}}},"processId":7464,"rootPath":"c:\\Users\\Johannes
Loher\\Development\\fsical-management","rootUri":"file:\/\/\/c%3A\/Users\/Johannes%20Loher\/Development\/fsical-management","trace":"off"})
2018-04-09T23:40:19.306:source\app.d:__lambda10:234 Processing as request
2018-04-09T23:40:19.306:source\app.d:processRequest:50 Initializing
2018-04-09T23:40:19.306:source\served\extension.d:initialize:143
Initializing serve-d for c:\Users\Johannes
Loher\Development\fsical-management
2018-04-09T23:40:19.306:source\served\extension.d:initialize:156
Starting dub...
2018-04-09T23:42:07.144:source\served\extension.d:safe:52
object.Exception@..\..\AppData\Local\dub\packages\dub-1.8.0\dub\source\dub\project.d(600):
Could not resolve configuration for package fsical-management
----------------
0x015C51EF
0x015C4FA2
0x015C2FBD
2018-04-09T23:42:07.144:source\served\extension.d:initialize:163 Failed
starting dub - falling back to fsworkspace
2018-04-09T23:42:07.144:source\served\jsonrpc.d:showErrorMessage:312
Error message:  Konnte dub nicht starten. Funktionalität begrenzt!
2018-04-09T23:42:07.144:source\served\jsonrpc.d:send:66
{"jsonrpc":"2.0","method":"window/showMessage","params":{"message":"
Konnte dub nicht starten. Funktionalität begrenzt!","type":1}}
2018-04-09T23:42:07.144:source\served\extension.d:initialize:194
Starting dmd
2018-04-09T23:42:07.144:source\served\extension.d:initialize:196
Starting dscanner
2018-04-09T23:42:07.144:source\served\extension.d:initialize:199
Starting dfmt
2018-04-09T23:42:07.144:source\served\extension.d:initialize:201
Starting dlangui
2018-04-09T23:42:07.144:source\served\extension.d:initialize:203
Starting importer
2018-04-09T23:42:07.144:source\served\extension.d:initialize:205
Starting moduleman


Do you have any idea what's going wrong?

On Monday, 9 April 2018 at 19:10:46 UTC, Samson wrote:
>
> Today I update code-d serve-d and vsc. After which I got the notification that
> WebFreak001 has deprecate code-d serve-d beta and auto completion stop working. I saw code-d extension with the same icon as code-d serve-d beta so I install it. After which code hinting and auto completion don't still.
>
> What is the solution to this problem?

Disable "normal" code-d, close VS, remove %appdata%/code-d, launch VS & enable code-d beta serve-d, enjoy.

We're in the same boat dude. I just did clean install of whole D ecosystem from 6 months old setup where everything was more or less working, and followed this treacherous deprecation message, got code-d 0.17.1 with betastream option instead of my trusty beta 0.17.9... OMG it is broken in so many ways...
it overwrites dub/serve-d paths settings, it messes with permissions, it removes already existing dub, dcd and serve-d executables!!!
Reverted back to "deprecated" beta, at least it somewhat working, it is still incredibly slow on showing meaningful completions, doesn't seem to recognize half of the project, and seems to be completely not working with workspaces, but it is better than nothing.

Overall I've got an awful experience from code-d. Now, unfortunattely, there is even no adequate editor with decent performance & usability on Windows, I mean yeah there is still visual-d but it takes about 3 seconds to actually show completions, and code-d is completely broken right now.

On Tuesday, 10 April 2018 at 03:37:59 UTC, evilrat wrote:
> On Monday, 9 April 2018 at 19:10:46 UTC, Samson wrote:
>>
>> Today I update code-d serve-d and vsc. After which I got the notification that
>> WebFreak001 has deprecate code-d serve-d beta and auto completion stop working. I saw code-d extension with the same icon as code-d serve-d beta so I install it. After which code hinting and auto completion don't still.
>>
>> What is the solution to this problem?
>
> Disable "normal" code-d, close VS, remove %appdata%/code-d, launch VS & enable code-d beta serve-d, enjoy.
>
> We're in the same boat dude. I just did clean install of whole D ecosystem from 6 months old setup where everything was more or less working, and followed this treacherous deprecation message, got code-d 0.17.1 with betastream option instead of my trusty beta 0.17.9... OMG it is broken in so many ways...
> it overwrites dub/serve-d paths settings, it messes with permissions, it removes already existing dub, dcd and serve-d executables!!!

well, don't store them in the code-d folder, it won't remove or mess up anything outside its own folder and it won't change the user settings if they point to valid executables either.

> Reverted back to "deprecated" beta, at least it somewhat working, it is still incredibly slow on showing meaningful completions, doesn't seem to recognize half of the project, and seems to be completely not working with workspaces, but it is better than nothing.
>
> Overall I've got an awful experience from code-d. Now, unfortunattely, there is even no adequate editor with decent performance & usability on Windows, I mean yeah there is still visual-d but it takes about 3 seconds to actually show completions, and code-d is completely broken right now.

fyi "deprecated" code-d beta and normal code-d is exactly the same plugin right now using exactly the same serve-d versions, except for the deprecation message.

On Monday, 9 April 2018 at 21:45:57 UTC, Johannes Loher wrote:
> Am 04.04.2018 um 20:34 schrieb greatsam4sure:
>> [...]
> I just tried to get this to work, too, but I was not able to get it to work correctly. It seems that running dub fails somehow:
>
> [...]

hm before it would have completely crashed workspace-d/serve-d to a point where nothing would work, now you basically only get stdlib and a guess of further import paths. Can you make a minimal test case where this happens? It is probably due to some dub.json settings. But as I use dub as a library it should work the same as just calling `dub build`

On Tuesday, 10 April 2018 at 11:54:47 UTC, WebFreak001 wrote:
>
> fyi "deprecated" code-d beta and normal code-d is exactly the same plugin right now using exactly the same serve-d versions, except for the deprecation message.

I wouldn't be complaining if it's not the case. With normal code-d it does remove everything in %appdata%/code-d on start, re-setting config paths(even though for exapmle dub is in PATH), downloading git repo, fails to build, and repeat, while with beta there is no such issues.

I would also suggest you to add explicit --compiler=dmd switch to build invocation since for example in my case dmd was in PATH env after ldc and so ldc used by default, which of course doesn't have x86_mscoff arch. I also think it is probably better to add --build=release too, since users usually don't do debug on that binaries.

What about workspaces? Let for exapmle have main project (really just a dub project with single app.d for testing library) and library project in one workspace. I don't get any autocompletion from both projects.
It also doesn't seems to work with dependency that has path property set, at least not when it's relative.
Is this ok?

On Tuesday, 10 April 2018 at 13:11:16 UTC, evilrat wrote:
> On Tuesday, 10 April 2018 at 11:54:47 UTC, WebFreak001 wrote:
>>
>> fyi "deprecated" code-d beta and normal code-d is exactly the same plugin right now using exactly the same serve-d versions, except for the deprecation message.
>
> I wouldn't be complaining if it's not the case. With normal code-d it does remove everything in %appdata%/code-d on start, re-setting config paths(even though for exapmle dub is in PATH), downloading git repo, fails to build, and repeat, while with beta there is no such issues.
>
> I would also suggest you to add explicit --compiler=dmd switch to build invocation since for example in my case dmd was in PATH env after ldc and so ldc used by default, which of course doesn't have x86_mscoff arch. I also think it is probably better to add --build=release too, since users usually don't do debug on that binaries.

No dmd has an optimization issue that it removes code making the program completely broken and freeze on IO if compiled with -O, which is implied by --build=release. I will never use build=release with dmd.

> What about workspaces? Let for exapmle have main project (really just a dub project with single app.d for testing library) and library project in one workspace. I don't get any autocompletion from both projects.
> It also doesn't seems to work with dependency that has path property set, at least not when it's relative.
> Is this ok?

Everything dub dependency related should work, I literally use dub as a library for this. Multi workspaces in vscode aren't implemented yet though.

Am 10.04.2018 um 14:27 schrieb WebFreak001:
> On Monday, 9 April 2018 at 21:45:57 UTC, Johannes Loher wrote:
>> Am 04.04.2018 um 20:34 schrieb greatsam4sure:
>>> [...]
>> I just tried to get this to work, too, but I was not able to get it to work correctly. It seems that running dub fails somehow:
>>
>> [...]
> 
> hm before it would have completely crashed workspace-d/serve-d to a point where nothing would work, now you basically only get stdlib and a guess of further import paths. Can you make a minimal test case where this happens? It is probably due to some dub.json settings. But as I use dub as a library it should work the same as just calling `dub build`

You are right, it indeed seems to be a dub problem. Running `dub build` gives me "Could not resolv configuration for package vibe-d". The strange thing is, it workls correctly on Linux / OS X with the same dub/dmd versions...

I tried it with another project with a more simple dub.json and it works fine out of the box. Very nice job!

On Tuesday, 10 April 2018 at 03:37:59 UTC, evilrat wrote:
> On Monday, 9 April 2018 at 19:10:46 UTC, Samson wrote:
>> [...]
>
> Disable "normal" code-d, close VS, remove %appdata%/code-d, launch VS & enable code-d beta serve-d, enjoy.
>
> [...]

Thanks your suggestion work for me. many thanks to you

On Tuesday, 10 April 2018 at 03:37:59 UTC, evilrat wrote:
> On Monday, 9 April 2018 at 19:10:46 UTC, Samson wrote:
>> [...]
>
> Disable "normal" code-d, close VS, remove %appdata%/code-d, launch VS & enable code-d beta serve-d, enjoy.
>
> [...]

Thanks, your suggestion work for me. Many thanks to you

On Tuesday, 10 April 2018 at 14:00:49 UTC, WebFreak001 wrote:
>> What about workspaces?
> Multi workspaces in vscode aren't implemented yet though.

By multi workspaces, do you mean a multi-root workspace ? If so, multi-roots arrived with LSP 3.6.0 / vscode-languageclient 3.4.0 (if you meant something else then nevermind this comment)