Usage of areas in .NET core












0















I am developing an ASP.NET MVC Core application. In this application I'm using areas. I have multiple areas now: Administrator (for website maintenance), Identity (for identity razor pages) and Public (for visitors).



I like those areas, but I dont' like the fact that I need my visitors url's look like: https://localhost:5001/Public/Home and https://localhost:5001/Public/Catalogue, etc.



I more like urls like https://localhost:5001/Home and https://localhost:5000/Catalogue etc.



Is there any possibility, where I can use areas, except for the visitor part of the website?










share|improve this question



























    0















    I am developing an ASP.NET MVC Core application. In this application I'm using areas. I have multiple areas now: Administrator (for website maintenance), Identity (for identity razor pages) and Public (for visitors).



    I like those areas, but I dont' like the fact that I need my visitors url's look like: https://localhost:5001/Public/Home and https://localhost:5001/Public/Catalogue, etc.



    I more like urls like https://localhost:5001/Home and https://localhost:5000/Catalogue etc.



    Is there any possibility, where I can use areas, except for the visitor part of the website?










    share|improve this question

























      0












      0








      0








      I am developing an ASP.NET MVC Core application. In this application I'm using areas. I have multiple areas now: Administrator (for website maintenance), Identity (for identity razor pages) and Public (for visitors).



      I like those areas, but I dont' like the fact that I need my visitors url's look like: https://localhost:5001/Public/Home and https://localhost:5001/Public/Catalogue, etc.



      I more like urls like https://localhost:5001/Home and https://localhost:5000/Catalogue etc.



      Is there any possibility, where I can use areas, except for the visitor part of the website?










      share|improve this question














      I am developing an ASP.NET MVC Core application. In this application I'm using areas. I have multiple areas now: Administrator (for website maintenance), Identity (for identity razor pages) and Public (for visitors).



      I like those areas, but I dont' like the fact that I need my visitors url's look like: https://localhost:5001/Public/Home and https://localhost:5001/Public/Catalogue, etc.



      I more like urls like https://localhost:5001/Home and https://localhost:5000/Catalogue etc.



      Is there any possibility, where I can use areas, except for the visitor part of the website?







      asp.net-core routes .net-core






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 30 '18 at 9:12









      Roel GeusensRoel Geusens

      5718




      5718
























          1 Answer
          1






          active

          oldest

          votes


















          1














          I will not recommend to get rid of "area name" in the url, because the routing will not work properly when you have similar page names in different areas! e.g. if you have two areas "public" and "private" and both contains pages with similar name "Index" most probably you will see an error that there is multiple pages using the same route, and thats why areas are exists.



          back to your issue, if you are using razor pages you may add the route template directly to the top of razor page:



          @page "/catalog"


          or if you have parameters:



          @page "{id}"
          @Url.Page("/catalog")


          if you are using MVC, then you may use attribute routing and keep AreaPrefix empty:



          [RouteArea("Public", AreaPrefix = "")]
          [RoutePrefix("catalog")]
          public class CatalogsController : Controller


          you can read more about routing in the docs here: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/routing?view=aspnetcore-2.2






          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%2f53976419%2fusage-of-areas-in-net-core%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









            1














            I will not recommend to get rid of "area name" in the url, because the routing will not work properly when you have similar page names in different areas! e.g. if you have two areas "public" and "private" and both contains pages with similar name "Index" most probably you will see an error that there is multiple pages using the same route, and thats why areas are exists.



            back to your issue, if you are using razor pages you may add the route template directly to the top of razor page:



            @page "/catalog"


            or if you have parameters:



            @page "{id}"
            @Url.Page("/catalog")


            if you are using MVC, then you may use attribute routing and keep AreaPrefix empty:



            [RouteArea("Public", AreaPrefix = "")]
            [RoutePrefix("catalog")]
            public class CatalogsController : Controller


            you can read more about routing in the docs here: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/routing?view=aspnetcore-2.2






            share|improve this answer




























              1














              I will not recommend to get rid of "area name" in the url, because the routing will not work properly when you have similar page names in different areas! e.g. if you have two areas "public" and "private" and both contains pages with similar name "Index" most probably you will see an error that there is multiple pages using the same route, and thats why areas are exists.



              back to your issue, if you are using razor pages you may add the route template directly to the top of razor page:



              @page "/catalog"


              or if you have parameters:



              @page "{id}"
              @Url.Page("/catalog")


              if you are using MVC, then you may use attribute routing and keep AreaPrefix empty:



              [RouteArea("Public", AreaPrefix = "")]
              [RoutePrefix("catalog")]
              public class CatalogsController : Controller


              you can read more about routing in the docs here: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/routing?view=aspnetcore-2.2






              share|improve this answer


























                1












                1








                1







                I will not recommend to get rid of "area name" in the url, because the routing will not work properly when you have similar page names in different areas! e.g. if you have two areas "public" and "private" and both contains pages with similar name "Index" most probably you will see an error that there is multiple pages using the same route, and thats why areas are exists.



                back to your issue, if you are using razor pages you may add the route template directly to the top of razor page:



                @page "/catalog"


                or if you have parameters:



                @page "{id}"
                @Url.Page("/catalog")


                if you are using MVC, then you may use attribute routing and keep AreaPrefix empty:



                [RouteArea("Public", AreaPrefix = "")]
                [RoutePrefix("catalog")]
                public class CatalogsController : Controller


                you can read more about routing in the docs here: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/routing?view=aspnetcore-2.2






                share|improve this answer













                I will not recommend to get rid of "area name" in the url, because the routing will not work properly when you have similar page names in different areas! e.g. if you have two areas "public" and "private" and both contains pages with similar name "Index" most probably you will see an error that there is multiple pages using the same route, and thats why areas are exists.



                back to your issue, if you are using razor pages you may add the route template directly to the top of razor page:



                @page "/catalog"


                or if you have parameters:



                @page "{id}"
                @Url.Page("/catalog")


                if you are using MVC, then you may use attribute routing and keep AreaPrefix empty:



                [RouteArea("Public", AreaPrefix = "")]
                [RoutePrefix("catalog")]
                public class CatalogsController : Controller


                you can read more about routing in the docs here: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/routing?view=aspnetcore-2.2







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 30 '18 at 12:55









                Laz ZiyaLaz Ziya

                733513




                733513






























                    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%2f53976419%2fusage-of-areas-in-net-core%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

                    Monofisismo

                    Angular Downloading a file using contenturl with Basic Authentication

                    Olmecas