תשובה How does Visual Studio call cspack

  • lundi 26 mars 2012 12:58
     
     

    Hi

    My client has a requirement that anything deployed to Azure is obfuscated.

    I want to see how VS is calling cspack so I can simply make the necessary changes to the arguments to cspack.

    I've looked in the "output" window, and it doesn't appear there.

    Thanks

    Ronny

Toutes les réponses

  • mardi 27 mars 2012 10:53
    Modérateur
     
     Traitée

    Hi,

    I am not familiar with what exact command Visual Studio uses. But in general, you can find reference of cspack on http://msdn.microsoft.com/en-us/library/gg432988.aspx.

    Best Regards,

    Ming Xu.


    Please mark the replies as answers if they help or unmark if not.
    If you have any feedback about my replies, please contact msdnmg@microsoft.com.
    Microsoft One Code Framework

  • lundi 2 avril 2012 05:44
    Modérateur
     
     

    Hi,

    I will mark the reply as an answer. If you find it no help, please feel free to unmark it and follow up.

    Thanks.

    Best Regards,

    Ming Xu.


    Please mark the replies as answers if they help or unmark if not.
    If you have any feedback about my replies, please contact msdnmg@microsoft.com.
    Microsoft One Code Framework

  • mardi 17 avril 2012 17:42
     
     

    The Windows Azure Tools do not call the command line CSPack.exe; they instead call the CSPack custom MSBuild task that ships with the Windows Azure SDK.  That said, the two (task and command line utility) have very similar sets of arguments.  You can see how the Tools use the task by examining the Microsoft.WindowsAzure.targets file in:

    <Program Files>\MSBuild\Microsoft\VisualStudio\v10.0\Windows Azure Tools\<Tools Version>

    By default, the Output window shows only minimal logging during the packaging process.  If you want more verbose logging, you can adjust the verbosity via the Tools::Options menu:

    Tools::Options::Projects and Solutions::Build and Run::MSBuild project build output verbosity

    Set the value to Diagnostic, for example (and prepare to be buried in MSBuild output).

    -Phil