locked
Azure SDK Default RRS feed

  • Question

  • Another probably simple question / answer...

    We are using Visual Studio 2012 Update 2 with the latest Azure SDK (and dependencies) installed. However, for every new project we create in VS LS, we must "upgrade" the project. Otherwise it appears to use an older version of LS (pre-update 2?) and definitely an older version of the Azure SDK (1.7 VS 2.0x). We did an unscientific test by setting up a completely new development environment; ensuring that only the latest components were installed, except where the Platform Installer required older dependent components to be installed as well. We saw the same behavior with that development machine as well. Is this normal? - that we must upgrade every LS project (especially if it will be deployed to Azure) before we can utilized the latest LS and Azure features? Is there a way to set/default the preferred behavior for new projects?

    TIA,

    -Eric
    ...burning the LightSwitch @ both ends ;-)


    Thanks, -Eric

    Tuesday, June 11, 2013 4:53 AM

Answers

  • Eric,

    If you use the "LightSwitch Application" project template, that is the same project template as the original release of VS 2012.  So yes, if you want the Update 2 functionality, you'll need to upgrade it.  If you select the "LightSwitch HTML Application", an upgrade won't be needed because it already has the Update 2 functionality (since that was when that project type was first released).

    We did not update the original VS 2012 LS project type to be compatible with the latest Azure SDK (2.0).  The latest version that is compatible with it is 1.8.  So if you want to use Azure SDK 2.0, you'll also need to upgrade your project to Update 2 functionality.  Note that you can have multiple versions of the Azure SDK installed side-by-side.  So you could have 1.8 and 2.0 installed and be able to work with both types of LS projects (original and upgraded) on the same machine.

    There's not a way to automatically default the project type version.  You'll need to manually upgrade it if you want the latest functionality for that project template.

    Hope that helps.

    Tuesday, June 11, 2013 4:46 PM

All replies

  • Eric,

    If you use the "LightSwitch Application" project template, that is the same project template as the original release of VS 2012.  So yes, if you want the Update 2 functionality, you'll need to upgrade it.  If you select the "LightSwitch HTML Application", an upgrade won't be needed because it already has the Update 2 functionality (since that was when that project type was first released).

    We did not update the original VS 2012 LS project type to be compatible with the latest Azure SDK (2.0).  The latest version that is compatible with it is 1.8.  So if you want to use Azure SDK 2.0, you'll also need to upgrade your project to Update 2 functionality.  Note that you can have multiple versions of the Azure SDK installed side-by-side.  So you could have 1.8 and 2.0 installed and be able to work with both types of LS projects (original and upgraded) on the same machine.

    There's not a way to automatically default the project type version.  You'll need to manually upgrade it if you want the latest functionality for that project template.

    Hope that helps.

    Tuesday, June 11, 2013 4:46 PM
  • Thanks Matt. That does help a great deal. I will instead start my projects with the HTML template and then just add the Silverlight client (except where I just want the HTML Client)

    -Eric
    ...burning the LightSwitch @ both ends ;-)


    Thanks, -Eric

    Tuesday, June 11, 2013 7:44 PM