Hi,

I have prepared a beta for the next release of Visual D. Here are some highlights:

- fixed installation/uninstallation issues in VS2017
- new VC project: allow adding C++ skeleton, fix some default settings
- settings: removed some legacy settings and made scope clearer
- dparser: support for "static foreach", fixed "find references", experimental "show value of constants in tooltip"
- mago: fix crash in VS2017, shows return values of functions stepped over
- fixed "Compile and Run" on selection
- fixed help via F1

You can find the installer and more details here:
https://github.com/dlang/visuald/releases/tag/v0.48.0-beta1

Rainer

Thx, no issues with VS 2017 anymore after a quick check.

On Friday, 5 October 2018 at 12:41:52 UTC, Rainer Schuetze wrote:
> Hi,
>
> I have prepared a beta for the next release of Visual D. Here are some highlights:
>
> - fixed installation/uninstallation issues in VS2017
> - new VC project: allow adding C++ skeleton, fix some default settings
> - settings: removed some legacy settings and made scope clearer
> - dparser: support for "static foreach", fixed "find references", experimental "show value of constants in tooltip"
> - mago: fix crash in VS2017, shows return values of functions stepped over
> - fixed "Compile and Run" on selection
> - fixed help via F1
>
> You can find the installer and more details here:
> https://github.com/dlang/visuald/releases/tag/v0.48.0-beta1
>
> Rainer

I just upgraded and now I'm constantly getting

A new guard page for the stack cannot be created

DParserCOMServer.

I upgraded from the linked file

On 07/10/2018 13:47, James Japherson wrote:
> On Friday, 5 October 2018 at 12:41:52 UTC, Rainer Schuetze wrote:
>> Hi,
>>
>> I have prepared a beta for the next release of Visual D. Here are some highlights:
>>
>> - fixed installation/uninstallation issues in VS2017
>> - new VC project: allow adding C++ skeleton, fix some default settings
>> - settings: removed some legacy settings and made scope clearer
>> - dparser: support for "static foreach", fixed "find references",
>> experimental "show value of constants in tooltip"
>> - mago: fix crash in VS2017, shows return values of functions stepped
>> over
>> - fixed "Compile and Run" on selection
>> - fixed help via F1
>>
>> You can find the installer and more details here: https://github.com/dlang/visuald/releases/tag/v0.48.0-beta1
>>
>> Rainer
> 
> I just upgraded and now I'm constantly getting
> 
> A new guard page for the stack cannot be created
> 
> DParserCOMServer.

Seems to be C#'s message for a stack overflow.

> 
> I upgraded from the linked file

Please specify a few more details about your environment: VS ersion, OS, etc.

Is this happening for a specific project or source code? Does it happen for a new "Hello World" project, too?

I installed 0.47 and tried intellisense and got an exception. I'll downgrade back to 0.46 which was working...

Seems that intellisense is broke. In 0.48 I did get the intellisense but on the same code with 0.46 it doesn't want to show up.

This is possibly because I'm using a static foreach to generate the structure in that case which 0.48 handled properly except it would crash most of the time.

(maybe the static foreach code added is buggy?)

0.46 doesn't crash though.

On Sunday, 7 October 2018 at 13:38:18 UTC, Rainer Schuetze wrote:
>
>
> On 07/10/2018 13:47, James Japherson wrote:
>> On Friday, 5 October 2018 at 12:41:52 UTC, Rainer Schuetze wrote:
>>> Hi,
>>>
>>> I have prepared a beta for the next release of Visual D. Here are some highlights:
>>>
>>> - fixed installation/uninstallation issues in VS2017
>>> - new VC project: allow adding C++ skeleton, fix some default settings
>>> - settings: removed some legacy settings and made scope clearer
>>> - dparser: support for "static foreach", fixed "find references",
>>> experimental "show value of constants in tooltip"
>>> - mago: fix crash in VS2017, shows return values of functions stepped
>>> over
>>> - fixed "Compile and Run" on selection
>>> - fixed help via F1
>>>
>>> You can find the installer and more details here: https://github.com/dlang/visuald/releases/tag/v0.48.0-beta1
>>>
>>> Rainer
>> 
>> I just upgraded and now I'm constantly getting
>> 
>> A new guard page for the stack cannot be created
>> 
>> DParserCOMServer.
>
> Seems to be C#'s message for a stack overflow.
>
>> 
>> I upgraded from the linked file
>
> Please specify a few more details about your environment: VS ersion, OS, etc.
>
> Is this happening for a specific project or source code? Does it happen for a new "Hello World" project, too?


Pretty much latest of everything. Obviously Windows by default. Any project.

This seems to happen when I use intellisense. Almost definitely an issue with any changes recently made. This did not happen with 0.44.


It seems that if I do something like

obj. <- crashes when adding the .

repeat, sometimes crashes sometimes not. Eventually I get a list of the intellisense.

Not sure if it only happens with . but it definitely seems to trigger it regularly, making this release nearly impossible to use. I think it also happens outside of intellisense though.

On Sunday, 7 October 2018 at 13:38:18 UTC, Rainer Schuetze wrote:
>
>
> On 07/10/2018 13:47, James Japherson wrote:
>> On Friday, 5 October 2018 at 12:41:52 UTC, Rainer Schuetze wrote:
>>> Hi,
>>>
>>> I have prepared a beta for the next release of Visual D. Here are some highlights:
>>>
>>> - fixed installation/uninstallation issues in VS2017
>>> - new VC project: allow adding C++ skeleton, fix some default settings
>>> - settings: removed some legacy settings and made scope clearer
>>> - dparser: support for "static foreach", fixed "find references",
>>> experimental "show value of constants in tooltip"
>>> - mago: fix crash in VS2017, shows return values of functions stepped
>>> over
>>> - fixed "Compile and Run" on selection
>>> - fixed help via F1
>>>
>>> You can find the installer and more details here: https://github.com/dlang/visuald/releases/tag/v0.48.0-beta1
>>>
>>> Rainer
>> 
>> I just upgraded and now I'm constantly getting
>> 
>> A new guard page for the stack cannot be created
>> 
>> DParserCOMServer.
>
> Seems to be C#'s message for a stack overflow.
>
>> 
>> I upgraded from the linked file
>
> Please specify a few more details about your environment: VS ersion, OS, etc.
>
> Is this happening for a specific project or source code? Does it happen for a new "Hello World" project, too?


Basically I'm having lots of problems with 0.48.

1. I get that one error about the stack constantly. Usually happens when I hit '.' but sometimes not.

2. error messages are pointing to lines below the actual error. Was very confusing to have D say the error is at line x when it is at line x - 3.

3. Not all debug symbols are showing in locals. foreach does not allow one to see symbols outside it, all kinds of problems here.

4. I tried downgrading to 0.46 which was working find yesterday and now it gives me an error about not being able to find user32.lib. Upgrading back to 0.47 fixes the user32.lib



So far 0.47 seems to be the best of 0.46 and 0.48. I haven't used it enough to know though.

Not sure what happened but 0.48 has become unusable. All kinds of minor problems.

Hopefully it is just a simple fix!

On 08/10/2018 17:16, James Japherson wrote:
> Basically I'm having lots of problems with 0.48.
> 
> 1. I get that one error about the stack constantly. Usually happens when I hit '.' but sometimes not.

I can reproduce with a combination of "static foreach" and "tupleof", I hope we can find a solution.

> 
> 2. error messages are pointing to lines below the actual error. Was very confusing to have D say the error is at line x when it is at line x - 3.

I don't see this. If the error reported in the output window is already wrong, it is the compiler to blaim. Visual D doesn't modify the output.

I see a one line offset with "Find References", though. (And a crash :-/ )

> 3. Not all debug symbols are showing in locals. foreach does not allow one to see symbols outside it, all kinds of problems here.

That happens if the foreach body is translated to a delegate literal. It should not be new to this version of Visual D and very much depends on the compiler generated debug info.

> 
> 4. I tried downgrading to 0.46 which was working find yesterday and now it gives me an error about not being able to find user32.lib. Upgrading back to 0.47 fixes the user32.lib

I suspect this happened due to some changes to the default library
search paths, that are migrated upwards, but not downwards with 0.47 IIRC.

> 
> 
> So far 0.47 seems to be the best of 0.46 and 0.48. I haven't used it enough to know though.
> 
> Not sure what happened but 0.48 has become unusable. All kinds of minor problems.
> 
> Hopefully it is just a simple fix!

Let's hope so. Thanks for reporting.

On 08/10/2018 19:55, Rainer Schuetze wrote:
> 
> 
> On 08/10/2018 17:16, James Japherson wrote:
>> Basically I'm having lots of problems with 0.48.
>>
>> 1. I get that one error about the stack constantly. Usually happens when I hit '.' but sometimes not.
> 
> I can reproduce with a combination of "static foreach" and "tupleof", I hope we can find a solution.
> 

Please try the new beta: https://github.com/dlang/visuald/releases/tag/v0.48.0-beta2

On Wednesday, 10 October 2018 at 06:37:33 UTC, Rainer Schuetze wrote:
>
>
> On 08/10/2018 19:55, Rainer Schuetze wrote:
>> 
>> 
>> On 08/10/2018 17:16, James Japherson wrote:
>>> Basically I'm having lots of problems with 0.48.
>>>
>>> 1. I get that one error about the stack constantly. Usually happens when I hit '.' but sometimes not.
>> 
>> I can reproduce with a combination of "static foreach" and "tupleof", I hope we can find a solution.
>> 
>
> Please try the new beta: https://github.com/dlang/visuald/releases/tag/v0.48.0-beta2

Oh man! Almost! It worked for about 3 minutes! I thought I was going to get somewhere! It got me with the stack frame bug.

I'm having a bigger problem though, not sure I think this is always been a problem with visual D.

I can't see any outer variables in the debug windows. It seems lambda's and inner functions and global scope is never shown while in those scopes! This makes it very hard to debug them because one can't see the outside variables. One has to make a sort of local copy.

e.g.,

int x = 3; // Won't be seen while in foo

void foo()
{
   // BP stopped here, can't see x in debug watches unless we do the following:
   int tmpx = x;
}


--
Best I can tell is that the stack frame bug occurs much less. Maybe 1/10th of the time(before it was every few seconds, now it's every minute maybe(although it might get worse after it gets worse).