Arry-eng comments

Results 4 comments of


                                            Arry-eng

VB.NET does not allow defining a Private `WriteOnly` property with the same name as a Public `ReadOnly` property. This causes issues when trying to encapsulate state management in a nice VB.NET way.

Auto Properties with private setters #508 - does not propose Orverridding based on ReadOnly and WriteOnly Attributes Overloading Getter And Setter of Property Using Attribute (FEATURE REQUEST) #279 is something...

VB.NET does not allow defining a Private `WriteOnly` property with the same name as a Public `ReadOnly` property. This causes issues when trying to encapsulate state management in a nice VB.NET way.

### Why This Matters **1. Code Complexity in Configuration Management (.xml or .json files)**: "The current requirement for compile-time constants often forces developers to use more complex and less readable...

VB.NET does not allow defining a Private `WriteOnly` property with the same name as a Public `ReadOnly` property. This causes issues when trying to encapsulate state management in a nice VB.NET way.

I don't think the above would compile. Even if so, the main issue is with (1)- the ability of the VB.NET language to be able to provide overloading and override...

VB.NET does not allow defining a Private `WriteOnly` property with the same name as a Public `ReadOnly` property. This causes issues when trying to encapsulate state management in a nice VB.NET way.

Yeah, thanks a lot! Yes, the above compiles and runs (- I checked it with Copilot though). It would also work for this base Command-Response sync scenario. Your time and...