ASP.NET Core 2.1 Use HttpContext in view












0















I have this httpcontext claim that I would like to use in my view to show the current users username. This is how I do it so far:



<p>@Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")</p>


However, the result is something like this:




UserName: user@email.com




Am I missing something? I tried to do this:



@Context.User.Claims.SingleOrDefault(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()


But it doesn't allow me to use Select after the SingleOrDefault.










share|improve this question

























  • Is it should be @Context.User.Claims.Where(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()?

    – Tetsuya Yamamoto
    Nov 15 '18 at 3:37
















0















I have this httpcontext claim that I would like to use in my view to show the current users username. This is how I do it so far:



<p>@Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")</p>


However, the result is something like this:




UserName: user@email.com




Am I missing something? I tried to do this:



@Context.User.Claims.SingleOrDefault(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()


But it doesn't allow me to use Select after the SingleOrDefault.










share|improve this question

























  • Is it should be @Context.User.Claims.Where(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()?

    – Tetsuya Yamamoto
    Nov 15 '18 at 3:37














0












0








0








I have this httpcontext claim that I would like to use in my view to show the current users username. This is how I do it so far:



<p>@Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")</p>


However, the result is something like this:




UserName: user@email.com




Am I missing something? I tried to do this:



@Context.User.Claims.SingleOrDefault(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()


But it doesn't allow me to use Select after the SingleOrDefault.










share|improve this question
















I have this httpcontext claim that I would like to use in my view to show the current users username. This is how I do it so far:



<p>@Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")</p>


However, the result is something like this:




UserName: user@email.com




Am I missing something? I tried to do this:



@Context.User.Claims.SingleOrDefault(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()


But it doesn't allow me to use Select after the SingleOrDefault.







c# asp.net linq asp.net-core asp.net-core-mvc






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 15 '18 at 3:45









Tetsuya Yamamoto

16.5k42240




16.5k42240










asked Nov 15 '18 at 3:29









JianYAJianYA

6771128




6771128













  • Is it should be @Context.User.Claims.Where(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()?

    – Tetsuya Yamamoto
    Nov 15 '18 at 3:37



















  • Is it should be @Context.User.Claims.Where(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()?

    – Tetsuya Yamamoto
    Nov 15 '18 at 3:37

















Is it should be @Context.User.Claims.Where(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()?

– Tetsuya Yamamoto
Nov 15 '18 at 3:37





Is it should be @Context.User.Claims.Where(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()?

– Tetsuya Yamamoto
Nov 15 '18 at 3:37












2 Answers
2






active

oldest

votes


















4














The SingleOrDefault() returns single element that matches with the criteria, not another IQueryable or IEnumerable collection which can be Select-ed later.




Returns a single, specific element of a sequence, or a default value
if that element is not found.




You should use Where() to return a collection before using Select():



@Context.User.Claims.Where(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()


For C# 6.0 and above, use null-conditional operator to get its value:



@Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")?.Value





share|improve this answer

































    0















    However, the result is something like this:




    Because .SingleOrDefault returns a claim item, then the view renders the item with its .ToString method.




    But it doesn't allow me to use Select after the SingleOrDefault.




    .SingleOrDefault returns a item in the collection, while .Select expects a collection. You should just visit the .Value property of this item directly.



    @Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")?.Value





    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%2f53312009%2fasp-net-core-2-1-use-httpcontext-in-view%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      4














      The SingleOrDefault() returns single element that matches with the criteria, not another IQueryable or IEnumerable collection which can be Select-ed later.




      Returns a single, specific element of a sequence, or a default value
      if that element is not found.




      You should use Where() to return a collection before using Select():



      @Context.User.Claims.Where(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()


      For C# 6.0 and above, use null-conditional operator to get its value:



      @Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")?.Value





      share|improve this answer






























        4














        The SingleOrDefault() returns single element that matches with the criteria, not another IQueryable or IEnumerable collection which can be Select-ed later.




        Returns a single, specific element of a sequence, or a default value
        if that element is not found.




        You should use Where() to return a collection before using Select():



        @Context.User.Claims.Where(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()


        For C# 6.0 and above, use null-conditional operator to get its value:



        @Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")?.Value





        share|improve this answer




























          4












          4








          4







          The SingleOrDefault() returns single element that matches with the criteria, not another IQueryable or IEnumerable collection which can be Select-ed later.




          Returns a single, specific element of a sequence, or a default value
          if that element is not found.




          You should use Where() to return a collection before using Select():



          @Context.User.Claims.Where(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()


          For C# 6.0 and above, use null-conditional operator to get its value:



          @Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")?.Value





          share|improve this answer















          The SingleOrDefault() returns single element that matches with the criteria, not another IQueryable or IEnumerable collection which can be Select-ed later.




          Returns a single, specific element of a sequence, or a default value
          if that element is not found.




          You should use Where() to return a collection before using Select():



          @Context.User.Claims.Where(u => u.Type == "UserName").Select(c => c.Value).SingleOrDefault()


          For C# 6.0 and above, use null-conditional operator to get its value:



          @Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")?.Value






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 15 '18 at 4:03

























          answered Nov 15 '18 at 3:41









          Tetsuya YamamotoTetsuya Yamamoto

          16.5k42240




          16.5k42240

























              0















              However, the result is something like this:




              Because .SingleOrDefault returns a claim item, then the view renders the item with its .ToString method.




              But it doesn't allow me to use Select after the SingleOrDefault.




              .SingleOrDefault returns a item in the collection, while .Select expects a collection. You should just visit the .Value property of this item directly.



              @Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")?.Value





              share|improve this answer




























                0















                However, the result is something like this:




                Because .SingleOrDefault returns a claim item, then the view renders the item with its .ToString method.




                But it doesn't allow me to use Select after the SingleOrDefault.




                .SingleOrDefault returns a item in the collection, while .Select expects a collection. You should just visit the .Value property of this item directly.



                @Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")?.Value





                share|improve this answer


























                  0












                  0








                  0








                  However, the result is something like this:




                  Because .SingleOrDefault returns a claim item, then the view renders the item with its .ToString method.




                  But it doesn't allow me to use Select after the SingleOrDefault.




                  .SingleOrDefault returns a item in the collection, while .Select expects a collection. You should just visit the .Value property of this item directly.



                  @Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")?.Value





                  share|improve this answer














                  However, the result is something like this:




                  Because .SingleOrDefault returns a claim item, then the view renders the item with its .ToString method.




                  But it doesn't allow me to use Select after the SingleOrDefault.




                  .SingleOrDefault returns a item in the collection, while .Select expects a collection. You should just visit the .Value property of this item directly.



                  @Context.User.Claims.SingleOrDefault(u => u.Type == "UserName")?.Value






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 15 '18 at 3:53









                  Danny ChenDanny Chen

                  30.5k1586138




                  30.5k1586138






























                      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%2f53312009%2fasp-net-core-2-1-use-httpcontext-in-view%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

                      Florida Star v. B. J. F.

                      Danny Elfman

                      Lugert, Oklahoma