xsharp.eu

Hello Everyone,

I've noticed that by using an older Xsharp version (2.12.0.0) in combination with Visual Studio 2022 Community edition that the compiler does not show any errors or warnings. This problem does not occur in the most recent version of Xsharp which is 2.13.2.2.

We prefer using the 2.12.0.0 version because for our projects it detects errors in our code that 2.13 ignores. We also think X# 2.12. is more developer friendly. However, maybe it would be useful to specify that this version is (partly) incompatible with VS 2022.

For now, we can just use Visual Studio 2019.

Version numbers:
Visual Studio 2022 Community 17.3.6 Last updated 08/11/2022
Xsharp: 2.13.2.2 && 2.12.0.0
Windows 10

Frank

Hi Frank,

If you do not provide a sample showing that 2.13 does not detect errors that it should and 2.12 does, then this will never get fixed in any future build, at least not at least maybe someone else sees the same problem, too. So far only thing you have shown is the issue with the ^ operator, which is acknowledged and will be fixed, but this is hardly a high impact problem.

Frank,

FdeRaadt post=24368 userid=6489 wrote:Hello Everyone,

I've noticed that by using an older Xsharp version (2.12.0.0) in combination with Visual Studio 2022 Community edition that the compiler does not show any errors or warnings. This problem does not occur in the most recent version of Xsharp which is 2.13.2.2.

We prefer using the 2.12.0.0 version because for our projects it detects errors in our code that 2.13 ignores. We also think X# 2.12. is more developer friendly. However, maybe it would be useful to specify that this version is (partly) incompatible with VS 2022.

For now, we can just use Visual Studio 2019.

Version numbers:
Visual Studio 2022 Community 17.3.6 Last updated 08/11/2022
Xsharp: 2.13.2.2 && 2.12.0.0
Windows 10

Frank

This is a known issue in 2.12 that was fixed in one of the 2.13 builds.
Of course you can choose to keep using 2.12, but then you will have to live with this problem.
We would really like to fix the issues that you have with 2.13 but you will have to give us examples of the problems that you have.

Robert

Hello Chris, Robert,

robert post=24371 userid=253 wrote: We would really like to fix the issues that you have with 2.13 but you will have to give us examples of the problems that you have.

I know. But I mentioned [multiple errors which we got in 2.12 (about 20 errors which definitely did not pop up in Frank's 2.13. and after I cloned the project, appeared in my 2.12. See https://www.xsharp.eu/forum/public-prod ... low-errors

Chris tried a few and they gave the error which 100% did not appear on Frank's Pc.

I wrote that, unlike with some situations, we can not send a reproducible sample anymore. But it happened exactly as I wrote.

Currently VS 2019 & X# 2.12 are preferable above Vs 2022 resp. X# 2.13..

Maybe we will try again with an X# update in the further future and find that these issues are solved.

Dick

Hi Dick,

OK, then I have to ask, what was the point of the original post then? Just to state that 2.12 is better than 2.13, without helping out making 2.13 better? Or to warn other users that may want to go back to 2.12, that VS2022 is not working properly with it?

Hi Chris,

to warn other users that may want to go back to 2.12, that VS2022 is not working properly with it?

This.

Frank

Hello Chris,

Chris post=24377 userid=313 wrote: OK, then I have to ask, what was the point of the original post then? Just to state that 2.12 is better than 2.13, without helping out making 2.13 better??

I am not sure why you phrase it like this. I think we have done a lot to reproduce issues and you have done a lot to solve them.

Sometimes issues can't be reproduced or solved. Then it's good for others to know what can go wrong with certain versions like Frank explained here. I don't know why then you think you need to write"without helping to make 2.13 better". Reaction like this scares people off from posting something. Is that what you want?

Dick

Hi Dick,

It just felt to me that the original post was just a rant, but truth is that intent is often very hard to read in written text, so I'm glad that I was wrong about this!

Hello Chris,

You are absolutely right, thanks for writing this.

I want to emphasize that we don't think that X# 2.13 isn't good, so certainly no rant intended, only that there are some issues which are absent in 2.12 which, for us, weigh heavier than other issued which were actually solved in 2.13.

Others might have the same or another reason for using #2.12 and then it's good to know that they should wait with VS 2022.

Dick