IIS Angular 7 page not loading images after upgrade to Angular 7 from 6











up vote
0
down vote

favorite












After upgrading Angular from 6 to 7 images that are being referenced in css with the rule background-image: url('../../../../../assets/icons/T04_24_edit.svg') are now being dumped directly into the dist folder when building for prod.



This is the dist folder:



enter image description here



And then my browser doesn't know how to load those svg's because IIS looks for them inside wwwrooot instead of dist:
enter image description here



enter image description here



This looks like some kind of optimization from the new Angular 7 build.



Is there any way I can disable this and revert to the Angular 6 way of using the path specified for images and not doing shady optimizations under the hood ?










share|improve this question




























    up vote
    0
    down vote

    favorite












    After upgrading Angular from 6 to 7 images that are being referenced in css with the rule background-image: url('../../../../../assets/icons/T04_24_edit.svg') are now being dumped directly into the dist folder when building for prod.



    This is the dist folder:



    enter image description here



    And then my browser doesn't know how to load those svg's because IIS looks for them inside wwwrooot instead of dist:
    enter image description here



    enter image description here



    This looks like some kind of optimization from the new Angular 7 build.



    Is there any way I can disable this and revert to the Angular 6 way of using the path specified for images and not doing shady optimizations under the hood ?










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      After upgrading Angular from 6 to 7 images that are being referenced in css with the rule background-image: url('../../../../../assets/icons/T04_24_edit.svg') are now being dumped directly into the dist folder when building for prod.



      This is the dist folder:



      enter image description here



      And then my browser doesn't know how to load those svg's because IIS looks for them inside wwwrooot instead of dist:
      enter image description here



      enter image description here



      This looks like some kind of optimization from the new Angular 7 build.



      Is there any way I can disable this and revert to the Angular 6 way of using the path specified for images and not doing shady optimizations under the hood ?










      share|improve this question















      After upgrading Angular from 6 to 7 images that are being referenced in css with the rule background-image: url('../../../../../assets/icons/T04_24_edit.svg') are now being dumped directly into the dist folder when building for prod.



      This is the dist folder:



      enter image description here



      And then my browser doesn't know how to load those svg's because IIS looks for them inside wwwrooot instead of dist:
      enter image description here



      enter image description here



      This looks like some kind of optimization from the new Angular 7 build.



      Is there any way I can disable this and revert to the Angular 6 way of using the path specified for images and not doing shady optimizations under the hood ?







      asp.net-mvc angular iis webpack upgrade






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 12 hours ago









      Goncalo Peres

      9211311




      9211311










      asked Nov 19 at 11:16









      Hazerd

      188216




      188216
























          2 Answers
          2






          active

          oldest

          votes

















          up vote
          0
          down vote













          To place static assets in dist folder, which is created after production build - you need add appropriate path to projects.your-project-name.architect.build.options.assets in angular.json file.






          share|improve this answer




























            up vote
            0
            down vote













            Apparently what made it work was changing the url in the scss files from background-image: url('../../../../../assets/icons/T04_24_edit.svg') to background-image: url('/assets/icons/T04_24_edit.svg')






            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',
              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%2f53373471%2fiis-angular-7-page-not-loading-images-after-upgrade-to-angular-7-from-6%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








              up vote
              0
              down vote













              To place static assets in dist folder, which is created after production build - you need add appropriate path to projects.your-project-name.architect.build.options.assets in angular.json file.






              share|improve this answer

























                up vote
                0
                down vote













                To place static assets in dist folder, which is created after production build - you need add appropriate path to projects.your-project-name.architect.build.options.assets in angular.json file.






                share|improve this answer























                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  To place static assets in dist folder, which is created after production build - you need add appropriate path to projects.your-project-name.architect.build.options.assets in angular.json file.






                  share|improve this answer












                  To place static assets in dist folder, which is created after production build - you need add appropriate path to projects.your-project-name.architect.build.options.assets in angular.json file.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 19 at 11:50









                  magos

                  1,67131837




                  1,67131837
























                      up vote
                      0
                      down vote













                      Apparently what made it work was changing the url in the scss files from background-image: url('../../../../../assets/icons/T04_24_edit.svg') to background-image: url('/assets/icons/T04_24_edit.svg')






                      share|improve this answer

























                        up vote
                        0
                        down vote













                        Apparently what made it work was changing the url in the scss files from background-image: url('../../../../../assets/icons/T04_24_edit.svg') to background-image: url('/assets/icons/T04_24_edit.svg')






                        share|improve this answer























                          up vote
                          0
                          down vote










                          up vote
                          0
                          down vote









                          Apparently what made it work was changing the url in the scss files from background-image: url('../../../../../assets/icons/T04_24_edit.svg') to background-image: url('/assets/icons/T04_24_edit.svg')






                          share|improve this answer












                          Apparently what made it work was changing the url in the scss files from background-image: url('../../../../../assets/icons/T04_24_edit.svg') to background-image: url('/assets/icons/T04_24_edit.svg')







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 19 at 12:13









                          Hazerd

                          188216




                          188216






























                               

                              draft saved


                              draft discarded



















































                               


                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53373471%2fiis-angular-7-page-not-loading-images-after-upgrade-to-angular-7-from-6%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

                              Refactoring coordinates for Minecraft Pi buildings written in Python