<t>Robert,<br/>
<br/>
>However, supporting Xamarin requires more than just a special Targets file.<br/>
<br/>
obviously.<br/>
<br/>
>We are planning to start working on extensions to the Visual Project System this Summer. Support for Xamarin, but also for .Net Core and portable class libraries are ...

<r>Hi,<br/>
<br/>
since December 2016, I have developed an Android application (with Xamarin and C#) where users see various measurements regarding company ship's voyage data.<br/>
<br/>
Also, by incorporating Google Maps into the app, users see the course of ships displaying useful parameters for ...

<t>Chris,<br/>
<br/>
I converted another Vulcan project to X# and the Error list window shows the errors exactly.<br/>
Then, I re-open the previous one and this one also works now.<br/>
Probably, it needs to be saved after changing the 'Current Project' to 'Entire Solution'<br/>
<br/>
thanks<br ...

<r>Hi Chris,<br/>
<br/>
>The image is not clear, but I think the combobox selection in the top left of the Errors window is set to Current Project, maybe this is the problem? Try changing it to "Entire Solutin" and rebuild, do the errors show now?<br/>
<br/>
Changing to "Entire Solution" and rebuild ...

To be more clear about the IntelliSense issue, this happens when the Class MyCommonClass contained into a referenced assembly (DLL).

<r>Hi DevTeam,<br/>
<br/>
I was delighted to see the GA release of XSharp.<br/>
Congratulations to you all.<br/>
<br/>
In the first 1 hour playing with the GA 1.0.1, I noticed 2 issues.<br/>
Perhaps I am missing something, but I would like to share my experience with you:<br/>
<br/>
1. Trying to ...

Jean-Pierre,

you have to type:
cTest := Vegas.Version to access a Static-Class member

Chris,

>That's because vulcan is an outdated compiler

You are right.
The .Net Reactor's version is the old 4.0.
I will upgrade it to 4.9 or (I see it now) in 5.0.

thank you
George

Hi Karl,

when you compiled (with X# of course) didn't you see the warning for the line:
68 (Form1 Methods.prg) ?

I am using the beta 0.9.

regards
George

<t>Chris,<br/>
<br/>
>I think this is a correct warning, isn't it? In the code there is a DO WHILE TRUE without an EXIT statement, so execution will never go out of this loop, and any code after it will not execute, thus the warning.<br/>
<br/>
That's true: Putting a conditional EXIT or RETURN ...