Restrict Access Modifier of Form Class Properties in C#












0















I created a DLL class that inherited Windows.FORM , I want to Restrict its properties Access Modifier like Size(width-height) & FormBorderStyle to Private



so unreachable in another Assembly. what should i do and what is relevant to it?
use abstract class maybe? thank you for help










share|improve this question



























    0















    I created a DLL class that inherited Windows.FORM , I want to Restrict its properties Access Modifier like Size(width-height) & FormBorderStyle to Private



    so unreachable in another Assembly. what should i do and what is relevant to it?
    use abstract class maybe? thank you for help










    share|improve this question

























      0












      0








      0








      I created a DLL class that inherited Windows.FORM , I want to Restrict its properties Access Modifier like Size(width-height) & FormBorderStyle to Private



      so unreachable in another Assembly. what should i do and what is relevant to it?
      use abstract class maybe? thank you for help










      share|improve this question














      I created a DLL class that inherited Windows.FORM , I want to Restrict its properties Access Modifier like Size(width-height) & FormBorderStyle to Private



      so unreachable in another Assembly. what should i do and what is relevant to it?
      use abstract class maybe? thank you for help







      c# winforms inheritance properties access-modifiers






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 25 '18 at 18:14









      Amirreza HallajianAmirreza Hallajian

      31




      31
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Don't do it.



          access modifiers are meant to guide developers. They, in no way, offer any protection against usage.



          A developer which want to access them, is able to, even if they are private and messing with the frameworks defaults can lead to serious issues.





          Alternatively...



          If your form is a fully stand alone functionality or feature, then make a wrapper around the form.



          For example:



          //the wrapper
          public class PropertyPages : IPropertyPages
          {
          //your wrapped form...
          private YourForm _propertyForm = new YourForm();

          //a public show, but the form itself remain inaccessible.
          public void Show()
          {
          _propertyForm.Show();
          }
          }





          share|improve this answer

























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53470442%2frestrict-access-modifier-of-form-class-properties-in-c-sharp%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Don't do it.



            access modifiers are meant to guide developers. They, in no way, offer any protection against usage.



            A developer which want to access them, is able to, even if they are private and messing with the frameworks defaults can lead to serious issues.





            Alternatively...



            If your form is a fully stand alone functionality or feature, then make a wrapper around the form.



            For example:



            //the wrapper
            public class PropertyPages : IPropertyPages
            {
            //your wrapped form...
            private YourForm _propertyForm = new YourForm();

            //a public show, but the form itself remain inaccessible.
            public void Show()
            {
            _propertyForm.Show();
            }
            }





            share|improve this answer






























              0














              Don't do it.



              access modifiers are meant to guide developers. They, in no way, offer any protection against usage.



              A developer which want to access them, is able to, even if they are private and messing with the frameworks defaults can lead to serious issues.





              Alternatively...



              If your form is a fully stand alone functionality or feature, then make a wrapper around the form.



              For example:



              //the wrapper
              public class PropertyPages : IPropertyPages
              {
              //your wrapped form...
              private YourForm _propertyForm = new YourForm();

              //a public show, but the form itself remain inaccessible.
              public void Show()
              {
              _propertyForm.Show();
              }
              }





              share|improve this answer




























                0












                0








                0







                Don't do it.



                access modifiers are meant to guide developers. They, in no way, offer any protection against usage.



                A developer which want to access them, is able to, even if they are private and messing with the frameworks defaults can lead to serious issues.





                Alternatively...



                If your form is a fully stand alone functionality or feature, then make a wrapper around the form.



                For example:



                //the wrapper
                public class PropertyPages : IPropertyPages
                {
                //your wrapped form...
                private YourForm _propertyForm = new YourForm();

                //a public show, but the form itself remain inaccessible.
                public void Show()
                {
                _propertyForm.Show();
                }
                }





                share|improve this answer















                Don't do it.



                access modifiers are meant to guide developers. They, in no way, offer any protection against usage.



                A developer which want to access them, is able to, even if they are private and messing with the frameworks defaults can lead to serious issues.





                Alternatively...



                If your form is a fully stand alone functionality or feature, then make a wrapper around the form.



                For example:



                //the wrapper
                public class PropertyPages : IPropertyPages
                {
                //your wrapped form...
                private YourForm _propertyForm = new YourForm();

                //a public show, but the form itself remain inaccessible.
                public void Show()
                {
                _propertyForm.Show();
                }
                }






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 25 '18 at 18:23

























                answered Nov 25 '18 at 18:18









                StefanStefan

                8,53773861




                8,53773861
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53470442%2frestrict-access-modifier-of-form-class-properties-in-c-sharp%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Costa Masnaga

                    Fotorealismo

                    Sidney Franklin