MSM for AP Crystal Reports, developer version for Microsoft Visual Studio (v.13.0.16.1954)

[Former Member]

From where can I download MSM for AP Crystal Reports, developer version for Microsoft Visual Studio (v.13.0.16.1954).

Instead of MSI we want to integrate MSM.

Please provide the download link.

[former_member11696 · Accepted solution]

Same page you downloaded the VS installer, it has the MSI's, 32 bit MSN and Clickonce packages.

Don

[Former Member · Accepted solution]

Hi Don,

We want 64 bit msn  for Microsoft Visual Studio runtime SP16  (v.13.0.16.1954)

Can I get just 13_0_16.msn for 64 bit ?

Please provide us a download link to download SP16  (v.13.0.16.1954) 64 bit msn.

Thanks.

[former_member183750 · Accepted solution]

Here you go:

- Ludek

Senior Support Engineer Product Support, Global Support Center Canada

Follow me on Twitter

Got Enhancement ideas? Use the SAP Idea Place

[former_member11696 · Accepted solution]

No 64 bit MSN's, use the MSI or click once packages

[Former Member · Accepted solution]

We are based on MSM (.msn)  in our 32 bit setups as easy to integrate with product setup and does not conflict with versions.

Since now we are migrating to 64 bit , we need a 64 bit MSM (.msn) or we have to take additional efforts to implement and verify.

We will also get compatibility issues with thrid party tools if we use crystal report  MSI.

Is there any reason why 64 bit MSM (.msn) are not available?

[former_member183750 · Accepted solution]

Almost nobody has really asked for it since 2010...

You're one of very, very few.

Explain;

We will also get compatibility issues with thrid party tools if we use crystal report  MSI.

- Ludek

Senior Support Engineer Product Support, Global Support Center Canada

Follow me on Twitter

Got Enhancement ideas? Use the SAP Idea Place

[Former Member · Accepted solution]

Since we have integration with many third party tools, We will get compatibility issues if different versions of 64 bit MSI of crystal reports is used by third party tools.

It will be really helpful if you could provide 64 bit MSM (.msn)  for the SP16  (v.13.0.16.1954).

Thanks,

[former_member11696 · Accepted solution]

MSM distribution packaging is OLD technology, we will not provide a 64 bit MSN version.

Use the MSI, it's complete and a lot easier to manage.

It does not matter if you use MSN or MSI for compatibility, it's all the same runtime. Only way to be compatible is to make sure all third party applications uses the same version. Check with them for upgrades.

You can test for the version in your app or installer by checking the GAC:

Here's one way:

foreach (Assembly MyVerison in AppDomain.CurrentDomain.GetAssemblies())

{

    if (MyVerison.FullName.Substring(0, 38) == "CrystalDecisions.CrystalReports.Engine")

    {

        //File:             C:\Windows\assembly\GAC_MSIL\CrystalDecisions.CrystalReports.Engine\13.0.2000.0__692fbea5521e1304\CrystalDecisions.CrystalReports.Engine.dll

        //InternalName:     Crystal Reports

        //OriginalFilename:

        //FileVersion:      13.0.9.1312

        //FileDescription:  Crystal Reports

        //Product:          SBOP Crystal Reports

        //ProductVersion:   13.0.9.1312

        //Debug:            False

        //Patched:          False

        //PreRelease:       False

        //PrivateBuild:     False

        //SpecialBuild:     False

        //Language:         English (United States)

        System.Diagnostics.FileVersionInfo fileVersionInfo = System.Diagnostics.FileVersionInfo.GetVersionInfo(MyVerison.Location);

        txtRuntimeVersion.Text += fileVersionInfo.FileVersion.ToString();

        // check if CrsytalDecisions.Enterprise dll's can be loaded ( Anything but Cortez - managed reporting )

        if (fileVersionInfo.FileVersion.Substring(0, 2) == "13")

        {

            btnRasOpen.Enabled = false;

        }

        CRVer = fileVersionInfo.FileVersion.Substring(0, 2);

        //return;

    }

}

//VB code

//Imports CrystalDecisions.CrystalReports.Engine

//Imports CrystalDecisions.Shared

//Imports System.Reflection

//Imports System.Runtime.InteropServices

//Public Class Form1

//    Private Sub CrystalReportViewer1_Load(sender As Object, e As EventArgs) Handles CrystalReportViewer1.Load

//        For Each MyVerison As Assembly In AppDomain.CurrentDomain.GetAssemblies()

//            If MyVerison.FullName.Substring(0, 38) = "CrystalDecisions.CrystalReports.Engine" Then

//                'File:             C:\Windows\assembly\GAC_MSIL\CrystalDecisions.CrystalReports.Engine\13.0.2000.0__692fbea5521e1304\CrystalDecisions.CrystalReports.Engine.dll

//                'InternalName:     Crystal Reports

//                'OriginalFilename:

//                'FileVersion:      13.0.9.1312

//                'FileDescription:  Crystal Reports

//                'Product:          SBOP Crystal Reports

//                'ProductVersion:   13.0.9.1312

//                'Debug:            False

//                'Patched:          False

//                'PreRelease:       False

//                'PrivateBuild:     False

//                'SpecialBuild:     False

//                'Language:         English (United States)

//                Dim fileVersionInfo As System.Diagnostics.FileVersionInfo = System.Diagnostics.FileVersionInfo.GetVersionInfo(MyVerison.Location)

//                MessageBox.Show(fileVersionInfo.FileVersion.ToString())

//                Return

//            End If

//        Next

//        Dim Report As New CrystalDecisions.CrystalReports.Engine.ReportDocument

//        Report.Load("C:\reports\formulas.rpt")

//        CrystalReportViewer1.ReportSource = Report

//    End Sub

You may have to write a dll to add this to your installer...

Don

[former_member183750 · Accepted solution]

All CR runtimes, be it 32 or 64 bit are side by side compatible. Even if they were not, I don't see what MSM and MSI would give you different runtime behaviors(?).

- Ludek

[Former Member · Accepted solution]

Hi Don and Ludek,

Well, we can't write the above code in installer dll, its a different component altogether.

Also we have integration with many third party tools which also uses crystal reports, so we don't have any control on their versions of crystal reports.

Till now we have been doing the MSM integration with our setup, we found it easy to integrate, hence we were hoping for the same support will continue from SAP team for providing MSM.

Anyways we are also trying for integration of MSI in our setup, but setup team is not very happy with it.

They have to take many extra efforts for integration of the MSI.

[former_member183750 · Accepted solution]

Unfortunately Manini, technology marches on and MSI files are the ting. So the setup tema will need to adjust. There is an additional poin tin favor of the MSI: You do not have to be concerned with dependency runtimes (e.g.; VC++) as these are part of the MSI. The are not part of the MSM due to MS licensing considerations.

There really is nothing we can do. There is no hope of ever getting a 64 bit MSM created.

- Ludek

[Former Member · Accepted solution]

Anyways thanks for the updates.

But its sad that you cannot support MSM for 64 bit, since we were using the MSM integration.

Also MSM amd MSI are both windows installer packages, they both go hand in hand

and have separate target customers.