locked
vs express web. where is release configuration?! RRS feed

  • Question

  • User1129400750 posted

    i just installed visual studio express web and i'm studing. in configuration manager i should have preinstalled release and debug  configurations but i have only debug listed.

    why no release here?! thanks

    Saturday, April 19, 2014 7:09 AM

Answers

  • User281315223 posted

    The example that I demonstrated above was using Visual Studio 2013 Express.

    The issue may actually be related to the type of application that you are running. Could you go through the steps that you are taking to build your application (specifically the type of project that it is) as I just created another example as you mentioned (ASP.NET Web Application > Empty) and still had the options for Debug / Release available.

    If you are explicitly using a Web Site application, you don't really need a Release mode as when it is built all of the files within it will be copied to the server.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Sunday, April 20, 2014 8:26 AM
  • User-1454326058 posted

    Hi pietro,

    I installed VS 2013 express for web, I found there isn’t the Release mode for the website project.

    I think that is by design.

    This is my tests below both in VS2012 and VS2013:

    1. Open a solution that contains the web application and web site projects
    2. Change the configuration to the Debug mode in the configuration dropdownlist.
    3. Right click the solution=>Configuration Manager
    4. All the projects’ configuration are changed to Debug
    5. Repeat the step 2 to change the configuration to the Release mode
    6. Repeat the step3, only the web applications’ configuration are changed to the Release, the websites’ configuration are remained Debug.

    Based on these tests, in my opinion, the Release model is used for the web application project.

    So, in the VS2013, it isn’t the Release model if we open the website project.

    Thanks

    Best Regards

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, April 21, 2014 10:27 PM

All replies

  • User281315223 posted

    I can't think of a reason that your Release option wouldn't be there by default (assuming that you just installed Visual Studio 2013 and haven't made any major configuration changes).

    It should be accessible when checking out the Package/Publish Web or Package/Publish SQL tabs within the Properties Menu for your Project :

    Additionally, the Configuration Manager area should also display the available build options :

    Do you have any additional information about the current type of application you are running or using?  Does this occur on any other applications or just this one? Have you tried restarting Visual Studio or running it as an Administrator (Right-click > Run as Administrator)?

    Saturday, April 19, 2014 9:00 AM
  • User1129400750 posted

    i'm running visual studio express for web 2013. it happens even running as administrator.

    i don't have the package/publish options you're showing. is it possible because express edition is limited?!

    edit: little update. if i create i project (asp.net empty site) i see the release configuration. if i create new web site (razor) release configuration is missing.

    Saturday, April 19, 2014 10:27 AM
  • User281315223 posted

    The example that I demonstrated above was using Visual Studio 2013 Express.

    The issue may actually be related to the type of application that you are running. Could you go through the steps that you are taking to build your application (specifically the type of project that it is) as I just created another example as you mentioned (ASP.NET Web Application > Empty) and still had the options for Debug / Release available.

    If you are explicitly using a Web Site application, you don't really need a Release mode as when it is built all of the files within it will be copied to the server.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Sunday, April 20, 2014 8:26 AM
  • User1129400750 posted

    The example that I demonstrated above was using Visual Studio 2013 Express.

    The issue may actually be related to the type of application that you are running. Could you go through the steps that you are taking to build your application (specifically the type of project that it is) as I just created another example as you mentioned (ASP.NET Web Application > Empty) and still had the options for Debug / Release available.

    If you are explicitly using a Web Site application, you don't really need a Release mode as when it is built all of the files within it will be copied to the server.

    file > new web site > razor template

    i think , after creating different kinf of projects, that the feature is just disabled for web sites.

    Monday, April 21, 2014 7:25 PM
  • User-1454326058 posted

    Hi pietro,

    I installed VS 2013 express for web, I found there isn’t the Release mode for the website project.

    I think that is by design.

    This is my tests below both in VS2012 and VS2013:

    1. Open a solution that contains the web application and web site projects
    2. Change the configuration to the Debug mode in the configuration dropdownlist.
    3. Right click the solution=>Configuration Manager
    4. All the projects’ configuration are changed to Debug
    5. Repeat the step 2 to change the configuration to the Release mode
    6. Repeat the step3, only the web applications’ configuration are changed to the Release, the websites’ configuration are remained Debug.

    Based on these tests, in my opinion, the Release model is used for the web application project.

    So, in the VS2013, it isn’t the Release model if we open the website project.

    Thanks

    Best Regards

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, April 21, 2014 10:27 PM
  • User281315223 posted

    i think , after creating different kinf of projects, that the feature is just disabled for web sites.

    Correct.

    As I mentioned in my earlier response (and Starain mentions in hers), Web Sites don't need to differentiate between different builds as they simply will copy all of the files for your Web Site project to the appropriate location when you deploy it (unlike a Web Application which will be compiled into DLL files).

    Tuesday, April 22, 2014 8:17 AM