Visibility private fields on Object Explorer in Visual Studio 2017












-2















I created a public class in my project, using C# and Visual Studio 2017. I added some private fields to the class and assembly project. When I view my class on Object Explorer, I see all private fields.



class



Object Explorer



Is this a bug in VS or is this how it should be?










share|improve this question




















  • 2





    This is how it should be. You can see a little lock at the icon of your fields, which indicates that these are private

    – cmos
    Nov 23 '18 at 9:18






  • 2





    private is "to be used only be other members within this class", not "hide this from programmers".

    – Damien_The_Unbeliever
    Nov 23 '18 at 9:20
















-2















I created a public class in my project, using C# and Visual Studio 2017. I added some private fields to the class and assembly project. When I view my class on Object Explorer, I see all private fields.



class



Object Explorer



Is this a bug in VS or is this how it should be?










share|improve this question




















  • 2





    This is how it should be. You can see a little lock at the icon of your fields, which indicates that these are private

    – cmos
    Nov 23 '18 at 9:18






  • 2





    private is "to be used only be other members within this class", not "hide this from programmers".

    – Damien_The_Unbeliever
    Nov 23 '18 at 9:20














-2












-2








-2








I created a public class in my project, using C# and Visual Studio 2017. I added some private fields to the class and assembly project. When I view my class on Object Explorer, I see all private fields.



class



Object Explorer



Is this a bug in VS or is this how it should be?










share|improve this question
















I created a public class in my project, using C# and Visual Studio 2017. I added some private fields to the class and assembly project. When I view my class on Object Explorer, I see all private fields.



class



Object Explorer



Is this a bug in VS or is this how it should be?







c# visual-studio






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 23 '18 at 10:21









Rik D

415




415










asked Nov 23 '18 at 9:16









Sergey SulimovSergey Sulimov

32




32








  • 2





    This is how it should be. You can see a little lock at the icon of your fields, which indicates that these are private

    – cmos
    Nov 23 '18 at 9:18






  • 2





    private is "to be used only be other members within this class", not "hide this from programmers".

    – Damien_The_Unbeliever
    Nov 23 '18 at 9:20














  • 2





    This is how it should be. You can see a little lock at the icon of your fields, which indicates that these are private

    – cmos
    Nov 23 '18 at 9:18






  • 2





    private is "to be used only be other members within this class", not "hide this from programmers".

    – Damien_The_Unbeliever
    Nov 23 '18 at 9:20








2




2





This is how it should be. You can see a little lock at the icon of your fields, which indicates that these are private

– cmos
Nov 23 '18 at 9:18





This is how it should be. You can see a little lock at the icon of your fields, which indicates that these are private

– cmos
Nov 23 '18 at 9:18




2




2





private is "to be used only be other members within this class", not "hide this from programmers".

– Damien_The_Unbeliever
Nov 23 '18 at 9:20





private is "to be used only be other members within this class", not "hide this from programmers".

– Damien_The_Unbeliever
Nov 23 '18 at 9:20












1 Answer
1






active

oldest

votes


















0














Info on Acces Modifiers



All you do by setting them private is hiding them from access, they still show up in the resources, so this is intended behaviour.



If you want to hide the code itself, you could put it in a library and import that library into the project.






share|improve this answer
























  • Thanks for answer!

    – Sergey Sulimov
    Nov 23 '18 at 9:33











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%2f53443682%2fvisibility-private-fields-on-object-explorer-in-visual-studio-2017%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














Info on Acces Modifiers



All you do by setting them private is hiding them from access, they still show up in the resources, so this is intended behaviour.



If you want to hide the code itself, you could put it in a library and import that library into the project.






share|improve this answer
























  • Thanks for answer!

    – Sergey Sulimov
    Nov 23 '18 at 9:33
















0














Info on Acces Modifiers



All you do by setting them private is hiding them from access, they still show up in the resources, so this is intended behaviour.



If you want to hide the code itself, you could put it in a library and import that library into the project.






share|improve this answer
























  • Thanks for answer!

    – Sergey Sulimov
    Nov 23 '18 at 9:33














0












0








0







Info on Acces Modifiers



All you do by setting them private is hiding them from access, they still show up in the resources, so this is intended behaviour.



If you want to hide the code itself, you could put it in a library and import that library into the project.






share|improve this answer













Info on Acces Modifiers



All you do by setting them private is hiding them from access, they still show up in the resources, so this is intended behaviour.



If you want to hide the code itself, you could put it in a library and import that library into the project.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 23 '18 at 9:22









Dennis VanhoutDennis Vanhout

917




917













  • Thanks for answer!

    – Sergey Sulimov
    Nov 23 '18 at 9:33



















  • Thanks for answer!

    – Sergey Sulimov
    Nov 23 '18 at 9:33

















Thanks for answer!

– Sergey Sulimov
Nov 23 '18 at 9:33





Thanks for answer!

– Sergey Sulimov
Nov 23 '18 at 9:33


















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%2f53443682%2fvisibility-private-fields-on-object-explorer-in-visual-studio-2017%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

404 Error Contact Form 7 ajax form submitting

How to know if a Active Directory user can login interactively

TypeError: fit_transform() missing 1 required positional argument: 'X'