locked
VS 2015 Conversion Issue RRS feed

  • Question

  • I just installed the Visual Studio 2015 Community Edition (Update 2) and the most recent Microsoft Office Developer Tools for Visual Studio 2015.  I can create new LightSwitch HTML projects in VS 2015.  However, when I try to open my existing VS 2013 LightSwitch HTML project in VS 2015, I get the following error message:  "This project is incompatible with the current edition of visual studio".   It does not appear that VS 2015 is even trying to convert or upgrade my existing VS 2013 project to VS 2015.  Does the VS 2015 Community Edition lack this upgrade feature?

    Monday, April 18, 2016 2:13 AM

Answers

All replies

  • Hi TaxPro,

    Please check the .NET Framework version of original Visual Studio 2013 LightSwitch project, whether this version of .NET Framework is installed on your Visual Studio 2015 machine.

    Please create a default LightSwitch 2013 project and then open it with Visual Studio 2015, whether it also has this issue.

    If the .NET Framework version is installed on Visual Studio 2015 machine and the same problem doesn't occur with new default project, if possible, please upload a sample project to OneDrive and then share a link here. It can help us find out what happened with your project.

    If the new project also has this issue, please try reset/repair your Visual Studio to check whether this problem can be fixed.

    Best Regards,
    Weiwei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.

    Click HERE to participate the survey.


    Tuesday, April 19, 2016 9:24 AM
    Moderator
  • Weiwei, this is a common problem as I've seen it mentioned on the forum a number of times now. We also have a VS2013 HTML project that exibits the same behavior and we have both VS2015 and VS2013 installed on the same computer, so the .NET frameworks are the same. There are also no extensions installed. I've not had time to really investigate this in depth, but all the reported work rounds for this problem were related to editing the manifest files of extensions, yet we do not have extensions, so wondering whether there is a similar setting in one of the project files that need to be edited manually?

    Regards, Xander. My Blog

    Tuesday, April 19, 2016 7:39 PM
  • Hi Weiwei,

    I have Visual Studio 2013 (Professional Edition) and 2015 (Community Edition) installed on the same machine.  Both target the .NET Framework version 4.5.  I created a new (default) LightSwitch HTML 2013 project (without 3rd party controls) and then tried to open it in Visual Studio 2015.  I received the following error message: 

    Thanks for your assistance.

    Wednesday, April 20, 2016 1:33 AM
  • Can you try installing Office Developer Tools Update 2 (ODT) from the Web Platform Installer.

    If you have installed Update 2 of Visual Studio 2015, you need to install Update 2 of ODT from WebPI.

    This information needs to be a sticky as this is now the third time I have posted this requirement.


    • Edited by Ian E Thursday, April 21, 2016 5:48 AM
    Thursday, April 21, 2016 5:48 AM
  • We have both VS2015 update 2 and ODT update 2 installed and it still won't load/upgrade the VS2013 project.

    Regards, Xander. My Blog

    Thursday, April 21, 2016 6:25 AM
  • Hi Ian,

    Like Xander (and many others), I also have ODT update 2 installed because I received the following message when using your link:

    Thanks for your suggestion anyway.  It may prove helpful to people who have not yet installed the ODT update 2.



    • Edited by TaxPro Thursday, April 21, 2016 7:41 PM
    Thursday, April 21, 2016 7:36 PM
  • Hi TaxPro,

    Please try uninstall the Update 2 and then try open your project again to check whether it can be opened.

    Since I have tried create a Visual Studio 2013 Professional LightSwitch application and open it in both Visual Studio 2015 Community with Update 2 and without Update 2. I found that this project can be opened in Visual Studio Community without Update 2.

    I suggest you submit this issue to Visual Studio Connect and then share the feedback link here, I will vote it. It also can let other communities who has the same problem to vote and add comments for this issue. I think the report team experts will treat it seriously. Thanks for your feedback for Visual Studio product.

    Best Regards,
    Weiwei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.

    Click HERE to participate the survey.



    Monday, April 25, 2016 6:02 AM
    Moderator
  • Hi Weiwei,

    I have posted the problem under the heading "LightSwitch HTML Project Conversion" at https://connect.microsoft.com/VisualStudio/Feedback/Details/2634499

    Thanks for your help. 


    Tuesday, April 26, 2016 3:06 AM
  • Hi TaxPro,

    The feedback link can't be opened. Please check it and edit it, which can let us vote your feedback. Thanks.

    Best Regards,
    Weiwei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, April 26, 2016 3:11 AM
    Moderator
  • Just remove the last dot from the link and it works - I have voted. Thanks for creating the issue.

    Regards, Xander. My Blog

    Tuesday, April 26, 2016 3:16 AM
  • Hi novascape,

    Thanks for your prompt. I also have vote the feedback.

    Please waiting for the response from the report team patiently.

    @TaxPro

    Please mark your reply that provide feedback link as a answer, which can let other communities who has the same problem to vote it.

    Best Regards,
    Weiwei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, April 26, 2016 3:33 AM
    Moderator
  • Hi Weivei,

    we are very patient, but after 3 weeks no news...

    Can you please help us?

    Did someone solve this issue?

    thanks

    Tuesday, May 17, 2016 11:22 AM
  • Hi silva71,

    I have help you add comments for that feedback to hurry them.

    I think they are testing this issue strictly which may spend much time. Thanks for your understanding.

    Best Regards,
    Weiwei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, May 18, 2016 3:04 AM
    Moderator
  • I just hit this one on a really large LightSwitch project that would take me weeks to convert over manually (sigh)...

    Unleash the Power - Get the LightSwitch HTML Client / SharePoint book

    http://LightSwitchHelpWebsite.com

    Thursday, May 19, 2016 11:16 PM
  • This is so annoying since it should just work. Don't know why MS does not address this.

    Michael, I've not tried this yet, but on my list of things to check was to use the information from elsewhere about updating the version in the LS Extension manifest files to see whether there was something similar in any of the relevant LS project files that one could update.


    Regards, Xander. My Blog

    Thursday, May 19, 2016 11:20 PM
  • This is so annoying since it should just work. Don't know why MS does not address this.

    Michael, I've not tried this yet, but on my list of things to check was to use the information from elsewhere about updating the version in the LS Extension manifest files to see whether there was something similar in any of the relevant LS project files that one could update.


    Regards, Xander. My Blog


    I spent about an hour updating the LS project files manually (I compared the settings to a working VS2015 project)  but the structure on many of them has changed significantly so I gave up.

    Unleash the Power - Get the LightSwitch HTML Client / SharePoint book

    http://LightSwitchHelpWebsite.com

    Thursday, May 19, 2016 11:47 PM
  • Hi Weiwei,

    any news on this? Posted another comment on the feedback.

    Another month without any news, but this is really critical.

    We have to change this post to open not answered.

    thanks

    --silvano

    Monday, June 13, 2016 10:10 AM
  • Hi silva71,

    Since the report team need to collect these feedback and verify them, then submit to product team, which will take a long time.

    If you require immediate assistance, please contact product support at http://support.microsoft.com/oas/default.aspx?prid=15825

    Thanks for your understanding.

    Best Regards,
    Weiwei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, June 14, 2016 12:57 AM
    Moderator
  • Hi Weivei,

    thank you for your reply,

    The Report Team Work is not difficult, the issue is very simple to describe and known by Microsoft, why it takes long time???

    Even if I open an incident they cannot help me.

    Any ideas to speed up the process?

    thanks

     

    Thursday, June 16, 2016 9:40 AM
  • Hi Angie and Weivei,

    any news, any update?

    thanks

    Thursday, July 7, 2016 3:35 PM
  • Hi Weiwei,

    I have posted the problem under the heading "LightSwitch HTML Project Conversion" at https://connect.microsoft.com/VisualStudio/Feedback/Details/2634499

    Thanks for your help. 


    I cannot believe the Conversion issue in Microsoft Connect have been deleted...

    Does this mean has been solved?

    Tuesday, July 12, 2016 2:38 PM
  • Hi Weiwei,

    I have posted the problem under the heading "LightSwitch HTML Project Conversion" at https://connect.microsoft.com/VisualStudio/Feedback/Details/2634499

    Thanks for your help. 


    I cannot believe the Conversion issue in Microsoft Connect have been deleted...

    Does this mean has been solved?


    No it is still there and marked "Active"

    http://AIHelpWebsite.com

    http://HoloLensHelpWebsite.com

    http://LightSwitchHelpWebsite.com

    Unleash the Power - Get the LightSwitch HTML Client / SharePoint book

    Tuesday, July 12, 2016 4:42 PM
  • I'm on VS 2013 and dreading an attempt to migrate to VS 2015 based on the comments here, along with my own experience in a quick-test migration back in January that was unsuccessful.

    I saw the connect posting as well, along with its comments thread.  Reading more, it appears that VS 2013 publishing to Azure may also lead to trouble, due to incompatibilities in later versions of the Azure dlls, where the official solution is to go to VS 2015? 

    So it's possible to box yourself in, whereby you can't publish to Azure in VS 2013, but also can't migrate to VS 2015?  Is there a known workaround for the VS 2103--> Azure publication issue? 

    Much as I'd like to go to VS 2015, my own upgrade attempt fizzled out and at the very least I'd like to know how to prevent a VS 2013 publish issue in case Azure requires me to upgrade to its latest NuGet packages.

    Wednesday, July 13, 2016 8:16 PM
  • The problem with staying on VS2013 is that they wont have any bug fixes.

    Right now my desktop computer wont even open VS2013 because I had to re-install SSDT for VS2013 and VS2015 to work on some SSIS packages. When I am done I plan to un-install the SSDT installs and then re-install VS2015 and hopefully that will fix my LightSwitch in VS2013 (see why this works in this thread).

    Right now LightSwitch works in VS2015 and I would upgrade ALL my LightSwitch projects to VS2015... if the VS2013 to VS2015 conversion worked.


    http://AIHelpWebsite.com

    http://HoloLensHelpWebsite.com

    http://LightSwitchHelpWebsite.com

    Unleash the Power - Get the LightSwitch HTML Client / SharePoint book

    Wednesday, July 13, 2016 8:26 PM
  • I agree, it's certainly not ideal to stay on VS 2013, but being able to publish is a must-have.  Sure would like to upgrade to 2015 though...

    If publishing from VS 2013 stopped working, something others have run into with some Azure package updates, would anyone know if building and deploying an LS application to Azure by hand could be a simple matter of running MSBuild and using the Azure Powershell cmdlets to deploy, as outlined for general VS projects here, or do LS projects require special sauce to build and publish?  (I don't have TFS anywhere and am not sure I'd want to introduce it just for this purpose.)


    Wednesday, July 13, 2016 10:32 PM
  • I agree, it's certainly not ideal to stay on VS 2013, but being able to publish is a must-have.  Sure would like to upgrade to 2015 though...

    If publishing from VS 2013 stopped working, something others have run into with some Azure package updates, would anyone know if building and deploying an LS application to Azure by hand could be a simple matter of running MSBuild and using the Azure Powershell cmdlets to deploy, as outlined for general VS projects here, or do LS projects require special sauce to build and publish?  (I don't have TFS anywhere and am not sure I'd want to introduce it just for this purpose.)


    Every time my VS2013 LightSwitch was broken (both opening a LightSwitch project and/or publishing), I have been able to fix it by following this thread, so this is what I recommend.

    Now, I always publish my LightSwitch projects locally and then FTP the result to my production servers (even when that server in on Azure), so my LightSwitch 'direct to Azure' publishing may still be broken when everything else was working...


    http://AIHelpWebsite.com

    http://HoloLensHelpWebsite.com

    http://LightSwitchHelpWebsite.com

    Unleash the Power - Get the LightSwitch HTML Client / SharePoint book

    Wednesday, July 13, 2016 11:02 PM
  • Hey Jim,

    After paying for support on these various issues here is my synopsis:

    1. The SSDT issue is with V12 Azure databases and the VS2013 SSDT after February 2015.

    2. The SSDT publishing issue is caused by the V12 profile trying to put the database in Single User mode which is not supported in Azure. 

    3. The SSDT issue was fixed in VS2015 SP1 and in the VS2015 SSDT after November 2015.

    To use the various versions of VS with Azure:

    1. VS2013 with any SP + SSDT Febuary 2015. The Feb 2015 SSDT package is still available to MSDN Subscribers.

    2. VS2015 + SP1 + latest SSDT works with Azure and will do conversions from 2013. I have a VM that I use to do my 2013 -> 2015 conversions then move them to the dev machines with the latest SP's + updates and everything works fine for me.

    If you have a MSDN subscription, you can download the old versions of VS2015 with no SP or SP1.

    On a side note, I had problems with VS2015 hanging when compiling solutions that had Nuget packages with PCL libraries. It looked like the problem was with the BCL Build NuGet. This was fixed in VS2015 SP2 but I found a work around for SP1.

    Just a note to people that have a problem, If you pay for support and Microsoft find the problem is caused by a product defect, they refund your money. I have little luck using Connect and only pay for a support now. I have not had to pay for any of my calls as all the issues I have raised are product defects.

    If you have MSDN, your get up to 4 paid support calls.

    Note that paying for a support call will not guarantee a speedy resolution as the old LS dev team has been reassigned to a new project and there are new people supporting LS. 

    Good Luck!

    Wednesday, July 13, 2016 11:19 PM
  • ...

    2. VS2015 + SP1 + latest SSDT works with Azure and will do conversions from 2013. I have a VM that I use to do my 2013 -> 2015 conversions then move them to the dev machines with the latest SP's + updates and everything works fine for me.

    If you have a MSDN subscription, you can download the old versions of VS2015 with no SP or SP1.

    ...

    Can you describe how you did this? When I download:

    Visual Studio Professional 2015 (x86 and x64) - DVD (English)" Release Date: 7/20/2015

    from MSDN Subscribers downloads and install it, it still ends up being Update 3 after it is installed :(


    http://AIHelpWebsite.com

    http://HoloLensHelpWebsite.com

    http://LightSwitchHelpWebsite.com

    Unleash the Power - Get the LightSwitch HTML Client / SharePoint book


    Friday, July 15, 2016 1:02 PM
  • Hi Michael,

    I downloaed VS2015 Update 1 Actually in Italian.

    And manage to convert everything!

    Mine are CBA.

    Thank IAN

    --silvano

    Friday, July 15, 2016 1:36 PM
  • I think it has to be on a clean OS that has never had a VS install. It's been a while since I did my conversions from 2013 -> 2015.

    Friday, July 15, 2016 2:46 PM
  • I can confim my machine is Clean!!!

    and it works perfectly!

    • Edited by silva71 Friday, July 15, 2016 3:23 PM
    Friday, July 15, 2016 3:23 PM
  • It is not working for me. Can anyone provide me with the "exact" steps to install Visual Studio 2015 without having it upgrade itself to the latest version?

    I have MSDN but apparently simply trying to install the earliest version didn't work. Perhaps it was the wrong version?

    Thank You


    http://AIHelpWebsite.com

    http://HoloLensHelpWebsite.com

    http://LightSwitchHelpWebsite.com

    Unleash the Power - Get the LightSwitch HTML Client / SharePoint book

    Friday, July 15, 2016 4:14 PM
  • Finally got it working! Thank you for everyone who helped (and those who offered to convert it for me) :)

    1) Make a virtual in Azure using Windows 2012 Datacenter (do not use anything else because it will have components that will make it not work. I lost 6 hours on this)

    2) Download from MSDN downloads and install on the virtual: en_visual_studio_professional_2015_with_update_1_x86_x64_dvd_8234481.iso

    3) You can now open and convert a LightSwitch 2013 project to LightSwitch 2015


    http://AIHelpWebsite.com

    http://HoloLensHelpWebsite.com

    http://LightSwitchHelpWebsite.com

    Unleash the Power - Get the LightSwitch HTML Client / SharePoint book

    Saturday, July 16, 2016 1:44 AM
  • And you have been installed the extensions Michael Before conversion or after ?
    Saturday, July 16, 2016 7:37 AM
  • And you have been installed the extensions Michael Before conversion or after ?

    I had no custom LightSwitch extensions in the project I converted.

    http://AIHelpWebsite.com

    http://HoloLensHelpWebsite.com

    http://LightSwitchHelpWebsite.com

    Unleash the Power - Get the LightSwitch HTML Client / SharePoint book

    Saturday, July 16, 2016 12:08 PM
  • I am glad there is an apparent work around to this issue (although it requires a MSDN subscription).  I guess my bigger concern now is what happens once I purchase a MSDN subscription and convert my VS 2013 LightSwitch HTML project to VS 2015.  Jim Bancroft notes above (Wednesday, July 13, 2016 8:16 PM) that "VS 2013 publishing to Azure may also lead to trouble, due to incompatibilities in later versions of the Azure dlls."  Some developers have concerns that LightSwitch HTML may be discontinued in the next version of Visual Studio "15" (see, https://social.msdn.microsoft.com/Forums/vstudio/en-US/c8fc8c72-cfee-413a-9366-faec8595e22f/discontinued-in-visual-studio-enterprise-15-preview?forum=lightswitch).  If LightSwitch is really discontinued in Visual Studio "15", then I am concerned publishing VS 2015 LightSwitch HTML projects to Azure may also lead to trouble, due to incompatibilities in later versions of the Azure dlls.  If so, VS 2015 LightSwitch HTML projects could have a very short lifespan.  I was hoping LightSwitch HTML projects could be published to Azure for at least another 5 to 7 years.      

    Sunday, July 24, 2016 12:23 PM