Does the new msbuild 15 /warnaserror switch allow to fail on all the warnings except some?












0














Specifically, I have a problem with MSB3026 - Could not copy bla-bla-bla to bla-bla-bla. Beginning retry 1 in 1000ms. The process cannot access the file bla-bla-bla because it is being used by another process.



I know why it happens - two different libraries use two different versions of the same dependency, but I cannot fix that right now.



So, I want to tell MSBuild to treat all the warnings, except MSB3026, as errors.



I do not understand if this is possible. Is it?










share|improve this question






















  • According to the documentation for warnaserror you can pass it a list of warnings, is that what you are looking for? Else there's e.g. stackoverflow.com/questions/17495278/…
    – stijn
    Nov 19 '18 at 19:35










  • Nope, I want all the warnings to be treated as errors, except MSB3026. But I think I have the answer here - github.com/Microsoft/msbuild/issues/3062#issuecomment-439945441
    – mark
    Nov 19 '18 at 19:51
















0














Specifically, I have a problem with MSB3026 - Could not copy bla-bla-bla to bla-bla-bla. Beginning retry 1 in 1000ms. The process cannot access the file bla-bla-bla because it is being used by another process.



I know why it happens - two different libraries use two different versions of the same dependency, but I cannot fix that right now.



So, I want to tell MSBuild to treat all the warnings, except MSB3026, as errors.



I do not understand if this is possible. Is it?










share|improve this question






















  • According to the documentation for warnaserror you can pass it a list of warnings, is that what you are looking for? Else there's e.g. stackoverflow.com/questions/17495278/…
    – stijn
    Nov 19 '18 at 19:35










  • Nope, I want all the warnings to be treated as errors, except MSB3026. But I think I have the answer here - github.com/Microsoft/msbuild/issues/3062#issuecomment-439945441
    – mark
    Nov 19 '18 at 19:51














0












0








0







Specifically, I have a problem with MSB3026 - Could not copy bla-bla-bla to bla-bla-bla. Beginning retry 1 in 1000ms. The process cannot access the file bla-bla-bla because it is being used by another process.



I know why it happens - two different libraries use two different versions of the same dependency, but I cannot fix that right now.



So, I want to tell MSBuild to treat all the warnings, except MSB3026, as errors.



I do not understand if this is possible. Is it?










share|improve this question













Specifically, I have a problem with MSB3026 - Could not copy bla-bla-bla to bla-bla-bla. Beginning retry 1 in 1000ms. The process cannot access the file bla-bla-bla because it is being used by another process.



I know why it happens - two different libraries use two different versions of the same dependency, but I cannot fix that right now.



So, I want to tell MSBuild to treat all the warnings, except MSB3026, as errors.



I do not understand if this is possible. Is it?







msbuild






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 '18 at 12:53









mark

19.4k56186373




19.4k56186373












  • According to the documentation for warnaserror you can pass it a list of warnings, is that what you are looking for? Else there's e.g. stackoverflow.com/questions/17495278/…
    – stijn
    Nov 19 '18 at 19:35










  • Nope, I want all the warnings to be treated as errors, except MSB3026. But I think I have the answer here - github.com/Microsoft/msbuild/issues/3062#issuecomment-439945441
    – mark
    Nov 19 '18 at 19:51


















  • According to the documentation for warnaserror you can pass it a list of warnings, is that what you are looking for? Else there's e.g. stackoverflow.com/questions/17495278/…
    – stijn
    Nov 19 '18 at 19:35










  • Nope, I want all the warnings to be treated as errors, except MSB3026. But I think I have the answer here - github.com/Microsoft/msbuild/issues/3062#issuecomment-439945441
    – mark
    Nov 19 '18 at 19:51
















According to the documentation for warnaserror you can pass it a list of warnings, is that what you are looking for? Else there's e.g. stackoverflow.com/questions/17495278/…
– stijn
Nov 19 '18 at 19:35




According to the documentation for warnaserror you can pass it a list of warnings, is that what you are looking for? Else there's e.g. stackoverflow.com/questions/17495278/…
– stijn
Nov 19 '18 at 19:35












Nope, I want all the warnings to be treated as errors, except MSB3026. But I think I have the answer here - github.com/Microsoft/msbuild/issues/3062#issuecomment-439945441
– mark
Nov 19 '18 at 19:51




Nope, I want all the warnings to be treated as errors, except MSB3026. But I think I have the answer here - github.com/Microsoft/msbuild/issues/3062#issuecomment-439945441
– mark
Nov 19 '18 at 19:51












1 Answer
1






active

oldest

votes


















0














The answer was provided here - https://github.com/Microsoft/msbuild/issues/3062#issuecomment-439945441 by Rainer Sigwald.



There is the flag /warnasmessage which demotes warnings to simple messages. It has higher priority than /warnaserror, so it is good enough.



To fail on all the warnings, except MSB3026 one would pass this to msbuild /err /nowarn:MSB3026






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%2f53375076%2fdoes-the-new-msbuild-15-warnaserror-switch-allow-to-fail-on-all-the-warnings-ex%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














    The answer was provided here - https://github.com/Microsoft/msbuild/issues/3062#issuecomment-439945441 by Rainer Sigwald.



    There is the flag /warnasmessage which demotes warnings to simple messages. It has higher priority than /warnaserror, so it is good enough.



    To fail on all the warnings, except MSB3026 one would pass this to msbuild /err /nowarn:MSB3026






    share|improve this answer


























      0














      The answer was provided here - https://github.com/Microsoft/msbuild/issues/3062#issuecomment-439945441 by Rainer Sigwald.



      There is the flag /warnasmessage which demotes warnings to simple messages. It has higher priority than /warnaserror, so it is good enough.



      To fail on all the warnings, except MSB3026 one would pass this to msbuild /err /nowarn:MSB3026






      share|improve this answer
























        0












        0








        0






        The answer was provided here - https://github.com/Microsoft/msbuild/issues/3062#issuecomment-439945441 by Rainer Sigwald.



        There is the flag /warnasmessage which demotes warnings to simple messages. It has higher priority than /warnaserror, so it is good enough.



        To fail on all the warnings, except MSB3026 one would pass this to msbuild /err /nowarn:MSB3026






        share|improve this answer












        The answer was provided here - https://github.com/Microsoft/msbuild/issues/3062#issuecomment-439945441 by Rainer Sigwald.



        There is the flag /warnasmessage which demotes warnings to simple messages. It has higher priority than /warnaserror, so it is good enough.



        To fail on all the warnings, except MSB3026 one would pass this to msbuild /err /nowarn:MSB3026







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 28 '18 at 20:02









        mark

        19.4k56186373




        19.4k56186373






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f53375076%2fdoes-the-new-msbuild-15-warnaserror-switch-allow-to-fail-on-all-the-warnings-ex%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

            android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

            SQL update select statement

            'app-layout' is not a known element: how to share Component with different Modules