XSharp Integration in VS 2019

Chris · Post by **Chris** » Fri Apr 24, 2020 6:10 pm

Thanks Leonid, both confirmed and logged:

https://github.com/X-Sharp/XSharpPublic/issues/370
https://github.com/X-Sharp/XSharpPublic/issues/371

leon-ts · Post by **leon-ts** » Mon Apr 27, 2020 10:11 am

Hi devteam!

When the "Show Completition list after character is typed" setting is turned on, there are very strong and frequent delays when entering text - the editor freezes for a while (from 3 to 10 seconds). Is there any way to improve the performance of this functionality? When the setting is off, input works without freezes, but ceases to be convenient.

P.S. Computer is powerful: 3GHz processor, 64GB RAM, RAID-0 disk (2x NVMe M.2).

Best regards,
Leonid

Chris · Post by **Chris** » Mon Apr 27, 2020 1:14 pm

Hi Leonid,

I am afraid for now you just need to keep this off, it is a known issue that with some solutions/projects it causes delays. This option has remained enabled only for those cases where it does not affect performance, in certain projects/solutions again.

Unfortunately I can't give you a timeframe for making it always work flawlessly either, because it is a very tricky area thing to get right.

leon-ts · Post by **leon-ts** » Mon Apr 27, 2020 1:24 pm

Chris, thanks for the answer!
I understand, optimization of some things is often a non-trivial task. We will look into the future with hope

I really hope that you will have some ideas for overcoming this problem.

Best regards,
Leonid

leon-ts · Post by **leon-ts** » Tue Apr 28, 2020 2:09 pm

Hi devteam!

Found a strange exception in debug mode (XSharp in VS 2019) when working with the "DATE" type.
Wrote the simplest example:

Code: Select all

FUNCTION Start() AS VOID STRICT
    LOCAL d AS DATE
    d := ConDate(2020, 04, 28)
    RETURN

When executing the line "d := ..." step by step, an exception occurs:

System.Threading.ThreadAbortException

I can not understand why this is happening?

P.S. Project type: VO Console Application (with default settings)

Best regards,
Leonid

robert · Post by **robert** » Wed Apr 29, 2020 6:43 am

Leonid,
I can reproduce this with both VS2019 and VS2019 preview. In Vs2017 it works as expected.
The problem is either in the VS debugger or our debugger support.
When you compile with VS2019 and then open the produced EXE as solution in VS2017 (did you know that you can do that ?) and then start the debugger then everything works as expected.

Robert

leon-ts · Post by **leon-ts** » Wed Apr 29, 2020 7:16 am

Robert,

Can I write this problem on GitHub as an error when working in VS2019?

P.S. I don't have VS2017 and I don't plan to use it.

Best regards,
Leonid

robert · Post by **robert** » Wed Apr 29, 2020 7:17 am

Leonid,
Yes please create a ticket, so we will not forget this.

Robert

robert · Post by **robert** » Wed Apr 29, 2020 4:12 pm

Leonid,
It took a while but I found it.
We have added a [DebuggerDisplay()] attribute to the Date type. In this attribute we are calling DTOC() to format the date according to your current settings. This accesses the runtime state
It looks like VS 2019 evaluates this on another thread than the current thread and this seems to cause the error.
We will fix this in the interim build that is planned for next week.

Robert

leon-ts · Post by **leon-ts** » Wed Apr 29, 2020 4:57 pm

Robert, thanks!

Best regards,
Leonid

Main menu