Optional parameter not recognized

wriedmann · Post by **wriedmann** » Fri Aug 31, 2018 5:41 pm

Hi Chris,

"Clean" and "Rebuild all" fixed it for me.

Wolfgang

Chris · Post by **Chris** » Fri Aug 31, 2018 5:59 pm

Thanks Wolfgang! Mathias, please start from scratch again, with a fresh new solution and try to implement the same thing, I am pretty sure it will work. I think the problem in that particular solution is some kind of corruption/dll versioning issue, because this compiler error happens when there is some runtime dll mixup, for example the dll is using one runtime dll file, but the vulcan app uses another and this confuses the vulcan compiler making it report this error.

But in any case, please just try to get away from the vulcan compiler completely as soon as possible. X# is very compatible to vulcan, there have been many very large apps which have been ported from vulcan to X# with minimal changes. For the things that indeed do not work, just please report them to us and we will take care of them? Apart from CCallNative which Robert said it is relatively easy to implement in X#, too, are you getting any other errors when compiling your vulcan code in x#?

Chris

wriedmann · Post by **wriedmann** » Fri Aug 31, 2018 7:32 pm

Hi Mathias,

please let me add something very important: the X# devteam is very different from the former Vulcan product owner: they listen to us because we are important for them.

So if you encounter a problem or something that does not work: post it here and they will find a solution.

I can say this because they have helped me a lot of times, not only showing me my errors, but also adding something to the language or changing some behavior.

So before mixing up Vulcan compiled code with X# compiled code because CCallNative() was not implemented: please ask for a solution here!

Wolfgang

Kromi · Post by **Kromi** » Mon Sep 03, 2018 5:53 am

Hi Wolfgang and Chis,

you are certainly right that I should not mix the two compilers, I just thought that way I could skip this one problematic library and to get a chance to see the errors in the other libraries. So I stumbled on this topics error, reproduced it in a new solution... anyway, I' follow you advice and post the X# compiler errors I get in this forum.

Thanks for your help, I really appreciate the work of the X# team and how fast we get answers on this forum.

Mathias

wriedmann · Post by **wriedmann** » Mon Sep 03, 2018 6:10 am

Hi Mathias,

I' follow you advice and post the X# compiler errors I get in this forum.

this is very important because not only it helps you, but it helps others that may read this message, and it helps the devteam to understand where the problems stay.
In my own experience, most of the times it was my error, and the answers helped me to understand why. And in a (very few) cases something in the compiler or the runtime was changed. The devteam really needs our feedback.

Wolfgang

Chris · Post by **Chris** » Mon Sep 03, 2018 10:08 am

Hi Matias,

Kromi wrote:So I stumbled on this topics error, reproduced it in a new solution...

So you created a new solution and still had the same problem? OK, now I am really puzzled, as this does not happen at all here. Just in case, can you please install the newest public build that was released very recently and try again?

Chris

Kromi · Post by **Kromi** » Mon Sep 03, 2018 10:24 am

Hi Chris,

the error is gone with the new version.
I have no idea if that really is a different behavior of the new version or if I somehow did something wrong previously.

Mathias

Chris · Post by **Chris** » Mon Sep 03, 2018 10:34 am

Hi Mathias,

Kromi wrote:Hi Chris,

the error is gone with the new version.
I have no idea if that really is a different behavior of the new version or if I somehow did something wrong previously.

Mathias

OK, great to hear! Out of curiosity, I will install the old build a little later and see if I can reproduce the problem with it.

Chris

Main menu