Are there any reasons to have class members public rather than internal in a winform (EXE) or webform app? This isn't about the DLLs they may reference, which will need Public members.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Nope there is no need to keep them public, as there won't be any other application or assembly accessing those members.
Though there is a model in .NET Websites where every webform is compiled as a separate dll, there if you have to call even another webform, it has to be public but its very unusual (infact bad design) to make call to another webforms member from any webform.
Business Accounts
Answer for Membership
by: JimBrandleyPosted on 2009-01-16 at 13:41:05ID: 23397696
brettr - Usually, members are made private to the class. However, either type of application can use multiple assemblies. If you have a class in one assembly, and a class in another assembly needs to reference a member of the first class, the property that exposes that member needs to be made public. If that's not the case, you can make it either internal, to limit the access to other classes in the assembly, or private to limit access to that class.
Jim