zoukankan      html  css  js  c++  java
  • simplified build configuration

    http://blogs.msdn.com/b/saraford/archive/2005/08/16/452411.aspx

    Did you know… That you can hide the solution and advanced build configurations

    Under Tools – Options – Projects and Solutions – General, there are options for both Always show solution and Show advanced build configurations. 

    Both options will affect the menu structure, changing which items appear or are enabled. 

    The Show advanced build configurations includes the Configuration Manager and the Solution Configurations and Solution Platforms combo boxes on the standard toolbar.

    Under most conditions, these options will work; however, there are some exceptions. 

    • Regardless of setting, the solution will still appear if you open a solution with multiple projects.
    • Regardless of setting, Advanced build configurations will appear if you open a project or solution that has mixed platforms or mixed solution and project configurations, like Solution is set to Debug, but Project is set to Release.

    Happy Visual Studio’ing!

    https://msdn.microsoft.com/zh-cn/library/ff452649(v=vs.110).aspx

    When you use the simplified build configuration, Visual Studio determines whether to build a debug or release version. Choosing the simplified build configuration implements the following settings:

    • The Start Debugging command on the Debug menu (F5) creates a debug version, and puts the build in the debug location regardless of the output path you specify.

    • The Build command on the Build menu uses the settings from the appropriate Project Designer pages.The Output path is on the Build page (C#) or Compile page (Visual Basic) of the Project Designer.

    • The Build menu does not contain the Configuration Manager command.

    • The Configuration and Platform drop-down lists do not appear on Project Designer pages.

    • On the toolbar, the Solution Configurations and Solution Platforms drop-down lists are not available.

    特别需要注意的是第一点和第二点:

    调试就是Debug的版本,生成就是Release的版本

    1.调试菜单中的开始调试命令,会自动创建一个Debug版本的程序,并且将调试版本的程序输出到默认的Debug路径(不管你在项目属性中设置的输出路径是什么)

    可以在binDebug目录下找到生成的Debug版本的程序

    2.生成菜单上的生成命令,会使用项目属性中的配置来生成程序,并且输出路径是项目属性中指定的

    已启动全部重新生成: 项目: WindowsFormsApplication2, 配置: Release Any CPU 

    不管你在项目属性中设置的是什么,提示都是Release Any CPU 

    即便你使用的是Debug的属性配置,并且目标平台是x86

  • 相关阅读:
    RecSys Challenge 2015
    Python 多行注释
    编译型语言与解释型语言
    vs2012 提示 未能正确加载 "Visual C++ Language Manager Package" 包
    人工智能 VS 机器学习 VS 深度学习
    CV-视频分析:静态背景下的运动检测
    消费者做出购买决策的流程
    Fat jar用途
    Eclipse中打包插件Fat Jar的安装与使用
    Eclipse将引用了第三方jar包的Java项目打包成jar文件的两种方法
  • 原文地址:https://www.cnblogs.com/chucklu/p/4836221.html
Copyright © 2011-2022 走看看