I suggest you ...

Allow saving multiple publishing configurations...

Currently, a VS LS project has a property sheet that allows you to publish the application directly to Azure / IIS. The settings (user name & passwords, connectionstrings, ...) are stored per project.

It would be a nice addition if we could save multiple sets of these settings per project. That way, I could set up a:
* development environment (IIS on local LAN, super admin user for sql user)
* QA environment (another IIS on local lan, but with restricted user)
* Acceptation environment (another IIS but on LAN of the customer)
* Production environment (Azure - the real deal)

The publish button would simply allow me to select my "stored settings" of choice, and publish to different environments / configurations.

68 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jan Van der HaegenJan Van der Haegen shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your suggestion on improving LightSwitch. However, Visual Studio 2015 is the last release of Visual Studio that includes the LightSwitch tooling and we recommend users not begin new application development with LightSwitch. That said, we will continue to support users with existing LightSwitch applications, including critical bug fixes and security issues as per the Microsoft Support Lifecycle. Please see the blog post for more information: https://blogs.msdn.microsoft.com/lightswitch/2016/10/14/lightswitch-update/

    – The Visual Studio Team

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base