Deployment of app

[John]

I'm trying to deploy a wpf app to a computer but it started showing error of syncfusion dll not found and I realized there was no syncfusion dll in bin folder. I had to manually copy the entire folder of 687MB to make it work. This is not good. Is there any other way that VS copies the dll other than manually marking every referenced assembly's "Copy Local" to true ?

Also, my app is still working fine without adding any license info ? is that a bug ?

[Vadivel Natarajan]

Hi Xmen, 

 

Greetings from Syncfusion.  

 

By default, Copy Local set to True when dragging and dropping a Syncfusion control from Visual Studio toolbox to the designer page. If manually referred the Syncfusion assembly, it is must to set Copy Local as True to move the referenced assembly to the bin folder when compile. Please refer to the following KB article for more information.  

 

https://www.syncfusion.com/kb/2110/issues-in-deploying-an-application-on-a-client-machine-that-uses-syncfusion-controls 

 

Regarding the license, we suspect that you may install the Syncfusion licensed setup and referring the Syncfusion assemblies from the installed location as you have the Syncfusion Community license. Syncfusion providing two types of setup which are Licensed setup for the paid customer and Community customer, and another one is trail setup for trail customer.   

  

The Licensed setup built without license validation. So, it does not require to refer to the Syncfusion.Licensing assembly and does not require to register the license key (RegisterLicense method) in your application. Also, it will not cause any issue if Syncfusion.Licensing assembly referred or License key registered in your application when using Syncfusion licensed setup assemblies.  

  

Those who are using the trail setup or Syncfusion NuGet package, they should have to refer the Syncfusion.Licensing assembly and register the license key (using Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense(“”) ) in their application as specified in the below help documentation.   

 

 https://help.syncfusion.com/common/essential-studio/licensing/license-key   

 

Also, please refer this blog post for understanding the licensing changes introduced in Essential Studio.     

  

Please let us know if this helps you.  

 

Regards, 

Vadivel Natarajan  

[John]

Copy Local is not set True by default. I did dragged it from toolbox. Also if assemblies are inbuilt licensed, then any body can use it. Then whats the point of license.

[Vadivel Natarajan]

Hi Xmen, 

  

Greetings from Syncfusion. 

  

We are afraid that we are unable to reproduce the reported Copy Local set to True issue and suspect that issue might be related to the Visual Studio. 

  

We have implemented this licensing (key) validation system to avoid using our products inadvertently. Syncfusion providing two types of setup which are  

  

·           Licensed setup for the paid customer and Community customer, and  

·           Trail setup for trail customer.   

  

As you own the "Essential Studio Enterprise Edition - Community license", it is not required to register the license key in your application when using Syncfusion licensed setup assemblies. Also, it will not cause any issue if Syncfusion.Licensing assembly referred or License key registered in your application. 

  

Starting with v16.2.0.x, if you reference Syncfusion assemblies from evaluation builds or from the NuGet feed, then it is must to register a license key in your projects as defined in below help documents. 

  

https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-register-the-syncfusion-license-key 

  

Also, please refer this blog post for understanding the licensing changes introduced in Essential Studio.     

  

Regards, 

Vadivel Natarajan 

[John]

I marked every synfusion referenced assembly to CopyLocal to True. And even after that, when running on a separate pc, that doesn't have synfustion installed, it shows this error

The invocation of the constructor on type 'Syncfusion.UI.Xaml.Grid.SfDataGrid' that matches the specified binding constraints threw an exception.
The type initializer for 'Syncfusion.UI.Xaml.Grid.SfDataGrid' threw an exception.

I had to copy entire directory of synfusion dlls to make it work.

[Deivaselvan Y]

HI Xmen, 

Thanks for the update. 

We have checked with the copy local true with the SfDataGrid WPF application. And it’s working fine at our end. Can you provide the list of assembly references which you are used for the Sample? If possible please provide sample to reproduce the reported issue at our end. So that we can able to check and provide the solution at the earliest. 

Regards, 

Deivaselvan 

[John]

Here is the list of all Syncfusion referenced assemblies in project

 <Reference Include="Syncfusion.Data.WPF, Version=16.4460.0.42, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89, processorArchitecture=MSIL">
      <HintPath>X:\Program Files (x86)\Syncfusion\Essential Studio\WPF\16.4.0.42\Assemblies\4.6\Syncfusion.Data.WPF.dll</HintPath>
      <HintPath>X:\Program Files (x86)\Syncfusion\Essential Studio\WPF\16.4.0.42\precompiledassemblies\4.6\Syncfusion.Data.WPF.dll</HintPath>
      <Private>True</Private>
    </Reference>
    <Reference Include="syncfusion.sfchart.wpf, Version=16.4450.0.42, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89, processorArchitecture=MSIL">
      <Private>True</Private>
    </Reference>
    <Reference Include="syncfusion.sfgauge.wpf, Version=16.4450.0.42, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89, processorArchitecture=MSIL">
      <Private>True</Private>
    </Reference>
    <Reference Include="syncfusion.sfgrid.wpf, Version=16.4450.0.42, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89, processorArchitecture=MSIL">
      <Private>True</Private>
    </Reference>
    <Reference Include="syncfusion.sfinput.wpf, Version=16.4450.0.42, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89, processorArchitecture=MSIL">
      <Private>True</Private>
    </Reference>
    <Reference Include="Syncfusion.SfShared.Wpf, Version=16.4460.0.42, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89, processorArchitecture=MSIL">
      <HintPath>X:\Program Files (x86)\Syncfusion\Essential Studio\WPF\16.4.0.42\Assemblies\4.6\Syncfusion.SfShared.Wpf.dll</HintPath>
      <HintPath>X:\Program Files (x86)\Syncfusion\Essential Studio\WPF\16.4.0.42\precompiledassemblies\4.6\Syncfusion.SfShared.Wpf.dll</HintPath>
      <Private>True</Private>
    </Reference>
    <Reference Include="Syncfusion.Shared.Wpf, Version=16.4460.0.42, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89, processorArchitecture=MSIL">
      <HintPath>X:\Program Files (x86)\Syncfusion\Essential Studio\WPF\16.4.0.42\Assemblies\4.6\Syncfusion.Shared.Wpf.dll</HintPath>
      <HintPath>X:\Program Files (x86)\Syncfusion\Essential Studio\WPF\16.4.0.42\precompiledassemblies\4.6\Syncfusion.Shared.Wpf.dll</HintPath>
      <Private>True</Private>
    </Reference>
    <Reference Include="syncfusion.tools.wpf, Version=16.4450.0.42, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89, processorArchitecture=MSIL">
      <Private>True</Private>
    </Reference>

[Deivaselvan Y]

Hi John, 

Thanks for the update. 

We have analyzed through the assembly list that you have shared. It seems that you are referring assemblies from different frameworks. From the provided assembly list, “Syncfusion.Data.WPF, Syncfusion.SfShared.WPF, Syncfusion.Shared.WPF” refers 4.6 framework (16.4460.0.42) whereas “Syncfusion.sfchart.wpf, Syncfusion.SfGauge.wpf, Syncfusion.SfGrid.WPF, Syncfusion.SfInput.WPF, Syncfusion.Tools.WPF” refers 4.5 framework (16.4450.0.42). Please refer all the Syncfusion assemblies in your project with the same framework as the project framework. 

If still issue exists at your end, please revert us with the sample to reproduce issue from our end. It will help us to investigate further and provide better solution at earliest. 

Regards
Deivaselvan 

[Evip Lews]

Please tell me how to make a progressive web application for https://errorcode0x.com/error-code-0x80070002/ as i want the users to post their queries over there

[John]

Hi John, 

Thanks for the update. 

We have analyzed through the assembly list that you have shared. It seems that you are referring assemblies from different frameworks. From the provided assembly list, “Syncfusion.Data.WPF, Syncfusion.SfShared.WPF, Syncfusion.Shared.WPF” refers 4.6 framework (16.4460.0.42) whereas “Syncfusion.sfchart.wpf, Syncfusion.SfGauge.wpf, Syncfusion.SfGrid.WPF, Syncfusion.SfInput.WPF, Syncfusion.Tools.WPF” refers 4.5 framework (16.4450.0.42). Please refer all the Syncfusion assemblies in your project with the same framework as the project framework. 

If still issue exists at your end, please revert us with the sample to reproduce issue from our end. It will help us to investigate further and provide better solution at earliest. 

Regards
Deivaselvan 

I did not add any reference, it was auto added after dragging the components from toolbox. Seems like bug in toolbox setup from syncfusion.

[Vadivel Natarajan]

Hi John, 

 

Greetings from Syncfusion.  

 

We are unable to reproduce the reported issue in our toolbox utility. Please make sure that Syncfusion controls in Visual Studio toolbox is configured with the required framework version as the application target framework version. If not, please reconfigure the required framework version Syncfusion controls in Visual Studio toolbox and check.  

 

Refer to the below help document to know about configuring Syncfusion controls in toolbox.    

 

https://help.syncfusion.com/common/essential-studio/utilities#configuring-toolbox  

 

If you have still face the same issue, then please share us the below mentioned details which will be very helpful for us to investigate the reported issue and provide you the solution at the earliest.  

 

    1. Application target framework.  

    2. Visual Studio about window screenshot (Open Visual Studio -> Click Help -> About Microsoft Visual Studio) 

 

Regards, 

Vadivel Natarajan