TOPIC:

Good day to you all!

I have just stumbled into an enormous body of work due to the fact that in X# one cannot have an access / assign with the same name as a member.

Unfortunately, all my classes written in VO use the same name for the member, the access and the assign.

This turns out to be an enormous amount of work which I have already started.

What I am doing is renaming the protected variables to “X_..” and then dealing with all the errors.

Any ideas / recommendations would be really helpful!

As always thank you, keep well and,

Cheers, JK

Hi John,
unfortunately this is not a limitation of X# itself, but of the .NET Framework.
There is another limitation: there cannot be a method and a access or assign with the same name.
Wolfgang
P.S. I'm using the underscore alone to distinguish my protect variables - that makes also my code easier to read because I see immediatly if a variable is a local or a protected variable

Hi there!

Ok - I am on exactly the same page...

Just a lot of changes to do - not hard but tedious!

As always, thank you, keep well and,

Cheers, JK

John
The sporter has an option to rename the variables.

Robert

Sporter !!!!

Where would I find such a beast?

Thank you!

John,
That was a typo.
I meant the VOXporter.
See www.xsharp.eu/help/example-1-the-vo-explorer-examp.html
Enable the checkbox "CheckForIVarAndPropertyConflicts"

Robert

Robert,

Arghh, I had completely forgotten I had implemented this in the VOXporter (after you had had suggested to do so)! I think the latest threads in the last days have given enough ideas for a "VO to X#" part 3 session...

Wowzer!

It worked really well!!!

Mucho gracias!!!

Cheers, JK

Hi Chris,
so I don't feel that stupid now as I had not even noted that option in the VOXporter.
A question: do you are renaming the declaration only or also the places where it is used? (I see that a bit risky, and since I try to fix my code always on the VO side I don't think I will use this option)
Wolfgang

HI Wolfgang,

It adjusts also the places where it is used. I agree it is a bit risky, this is why the option is disabled by default. But in our tests I think we haven't found any problems so far.

.

Hi Chris,
thank you very much for this clarification!
Wolfgang

Chris,

Chris wrote: Robert,
Arghh, I had completely forgotten I had implemented this in the VOXporter (after you had had suggested to do so)! I think the latest threads in the last days have given enough ideas for a "VO to X#" part 3 session...

Ok, please start preparing then

Robert

Good day to you all,

We all look forward to it!

So far, my big migration job is going pretty well thanks to you gentlemen..

As always, thank you and,

Cheers, JK

robert wrote:

Chris wrote: Arghh, I had completely forgotten I had implemented this in the VOXporter (after you had had suggested to do so)! I think the latest threads in the last days have given enough ideas for a "VO to X#" part 3 session...

Ok, please start preparing then

Wouldn't had said it otherwise, I already am! Mentally at least

.