Different scope for Get/Set properties in VB.Net

[Jerkerus]

I'm having problem with properties in VB.Net. We frequently use different scope for the Get and Set operations. Typically the Get operation is Public, wheras the Set operation is Friend so it can be set by our internal objects, but not external applications using our components. This is supported and works well in Visual Studio.

When importing the class into EA it does not recognize that it is a property - it creates the attribute and the operations correct, but does not understand that they belong together (the property checkbox of the variable is unset). Also it created problems when re-generating the code, scince EA generates an additional property with the same name but an empty variable.

For other languages (such as Delphi) it is possible to set different scope on the Get and Set operations - but not VB.Net even though it works fine in the code.