locked
Upgrade from 2012 to 2013 RRS feed

  • Question

  • This error occurs ...... urgent help needed as I need the new stuff

    Cheers,

    Error      1             An exception occurred when building the database for the application.

    Could not deploy package.

    Error SQL72014: .Net SqlClient Data Provider: Msg 547, Level 16, State 0, Line 17 The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "AssessedObjectRubricCriteriaSc_AssessedObject". The conflict occurred in database "C:\USERS\DWHI045\DOCUMENTS\VISUAL STUDIO 2013\PROJECTS\ASSESSOR\ASSESSOR\BIN\DATA\APPLICATIONDATABASE.MDF", table "dbo.AssessedObjects", column 'Id'.

    Error SQL72045: Script execution error.  The executed script:

    ALTER TABLE [dbo].[ActivityRubrics] WITH CHECK CHECK CONSTRAINT [ActivityRubric_Activity];

    ALTER TABLE [dbo].[Activities] WITH CHECK CHECK CONSTRAINT [wsCourseInstance_Activity];

    ALTER TABLE [dbo].[Activities] WITH CHECK CHECK CONSTRAINT [Activity_Activity];

    ALTER TABLE [dbo].[Activities] WITH CHECK CHECK CONSTRAINT [ActivityType_Activity];

    ALTER TABLE [dbo].[xActivityOutcomes] WITH CHECK CHECK CONSTRAINT [xActivityOutcome_Activity];

    ALTER TABLE [dbo].[StateOfActivities] WITH CHECK CHECK CONSTRAINT [StateOfActivity_Activity];

    ALTER TABLE [dbo].[TagActivities] WITH CHECK CHECK CONSTRAINT [TagActivity_Activity];

    ALTER TABLE [dbo].[xAnythingActivities] WITH CHECK CHECK CONSTRAINT [xAnythingActivity_Activity];

    ALTER TABLE [dbo].[AssessedObjectRubricCriteriaScores] WITH CHECK CHECK CONSTRAINT [AssessedObjectRubricCriteriaSc_AssessedObject];

    ALTER TABLE [dbo].[AssessedObjectRubricCriteriaScores] WITH CHECK CHECK CONSTRAINT [AssessedObjectRubricCriteriaSc_ScaleGradation];

    ALTER TABLE [d

                   C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\LightSwitch\v4.0\Microsoft.LightSwitch.targets       160               10           Assesso

    Sunday, November 17, 2013 9:51 PM

Answers

  • Hi Rapuke

    If you have created a LightSwitch application in Visual Studio 2012, and upgrade it from Visual Studio 2012 to Visual Studio 2013, you will automatically receive a prompt for upgrade on opening the project on a machine with Visual Studio 2013 preview.

    Before Upgrade starts, a backup of the current project is made and stored in Backup folder located at the same level in the project folder as the solution file (.sln). The user file settings (.suo file) is also backed up.

    It is a 1 way project upgrade. This means that after upgrade, the project cannot be opened with previous releases of Visual Studio.

    If you change your mind after upgrade and want to move back to the previous version of the project, you can open the project (not upgraded) in Backup folder using Visual Studio 2012.

    Upgrading your LightSwitch projects (Raghuveer Gopalakrishnan)

    Moreover, many things should be taken into consideration before your upgrading, you can also refer the msdn documents below,

    Upgrading LightSwitch Extension Projects to Visual Studio 2013 - Beth Massi

    Upgrading Projects Created in Earlier Versions of LightSwitch

    Regards


    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. <br/> Click <a href="http://support.microsoft.com/common/survey.aspx?showpage=1&scid=sw%3Ben%3B3559&theme=tech"> HERE</a> to participate the survey.

    • Marked as answer by Angie Xu Monday, November 25, 2013 1:47 AM
    Tuesday, November 19, 2013 2:27 AM

All replies

  • Hi Rapuke

    If you have created a LightSwitch application in Visual Studio 2012, and upgrade it from Visual Studio 2012 to Visual Studio 2013, you will automatically receive a prompt for upgrade on opening the project on a machine with Visual Studio 2013 preview.

    Before Upgrade starts, a backup of the current project is made and stored in Backup folder located at the same level in the project folder as the solution file (.sln). The user file settings (.suo file) is also backed up.

    It is a 1 way project upgrade. This means that after upgrade, the project cannot be opened with previous releases of Visual Studio.

    If you change your mind after upgrade and want to move back to the previous version of the project, you can open the project (not upgraded) in Backup folder using Visual Studio 2012.

    Upgrading your LightSwitch projects (Raghuveer Gopalakrishnan)

    Moreover, many things should be taken into consideration before your upgrading, you can also refer the msdn documents below,

    Upgrading LightSwitch Extension Projects to Visual Studio 2013 - Beth Massi

    Upgrading Projects Created in Earlier Versions of LightSwitch

    Regards


    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. <br/> Click <a href="http://support.microsoft.com/common/survey.aspx?showpage=1&scid=sw%3Ben%3B3559&theme=tech"> HERE</a> to participate the survey.

    • Marked as answer by Angie Xu Monday, November 25, 2013 1:47 AM
    Tuesday, November 19, 2013 2:27 AM
  • The similar behavior observed in my environment. After upgrade (one way of course) my project from 2012 to 2013, Rebuild All in VS 2013 with Update 2 failed with:

    Error 15 An exception occurred when building the database for the application.
    Could not deploy package.
    Warning SQL72030: If this deployment is executed, changes to [dbo].[Zauctovanie] might introduce run-time errors in [dbo].[ExportDoOrange].
    Warning SQL72030: If this deployment is executed, changes to [dbo].[ZeReproHd] might introduce run-time errors in [dbo].[rfZeReproHdLast].
    Warning SQL72030: If this deployment is executed, changes to [dbo].[ZeReproHd] might introduce run-time errors in [dbo].[rfZeReproHdLastPorod20_30Before].

    ...

    Error SQL72014: .Net SqlClient Data Provider: Msg 2627, Level 14, State 1, Line 32 Violation of UNIQUE KEY constraint 'UQ__tmp_ms_x__7DAD2D83EE3909AD'. Cannot insert duplicate key in object 'dbo.tmp_ms_xx_PovolenyPohyb'. The duplicate key value is (<NULL>).
    Error SQL72045: Script execution error.  The executed script:
    BEGIN TRANSACTION;

    SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;

    SET XACT_ABORT ON;

    CREATE TABLE [dbo].[tmp_ms_xx_PovolenyPohyb] (
        [Id]                               INT        IDENTITY (1, 1) NOT NULL,
        [JeUkryte]                         BIT        DEFAULT 0 NOT NULL,
        [RowVersion]                       ROWVERSION NOT NULL,
        [PovolenyPohybItem_KategoriaItem]  INT        NULL,
        [PovolenyPohybItem_KategoriaItem1] INT        NULL,
        [PovolenyPohybItem_PohybItem]      INT        DEFAULT 0 NOT NULL,
        [PovolenyPohybItem_StrediskoItem]  INT        NULL,
        [PovolenyPohybItem_StrediskoItem1] INT        NULL,
        [PovolenyPohybItem_ZakazkaItem]    INT        NULL,
        [PovolenyPohybItem_ZakazkaItem1]   INT        NULL,
        PRIMARY KEY CLUSTERED ([Id] ASC),
        UNIQUE NONCLUSTERED ([PovolenyPohybItem_KategoriaItem] ASC),
        UNIQUE NONCLUSTERED ([PovolenyPohybItem_KategoriaItem1] ASC),
        UNIQUE NONCLUSTERED ([PovolenyPohybItem_PohybItem] ASC),
        UNIQUE NONCLUSTERED ([P
     C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\LightSwitch\v4.0\Microsoft.LightSwitch.targets 160 10 Zvierata

    Note: I do not try to publish something, I only try to rebuild solution.

    Monday, June 9, 2014 3:15 PM
  • Something similar is happend to me too. Error after Upgrade to the Last Version
    Monday, June 9, 2014 3:23 PM