SfSpreadSheet - Error - Not Working

None of the samples or Demos for your SfSpreadSheet will compile or run
Im Using .Net Framework 4.6 but also tried NetCore... on Visual Studio 2019 none will work

Using latest version of syncfusion

The SfSpreadSheetRibbon control seems to work by itself but as soon as you add a SfSpreadSheet an error will occur

 the System.windows.interactivity.dll referenced also gave me problems

Any Updates that will fix this?
Or is it me?

16 Replies

AR Arulpriya Ramalingam Syncfusion Team April 13, 2020 03:14 PM UTC

Hi Eric, 
 
Greetings from Syncfusion support. 
 
In the Spreadsheet demos, we have used behaviors for code reusability and the reported use case occurred due to the System.Windows.Interactivity.dll assembly is not installed in your local machine. We would request you to install the assembly in GAC or nuget package for the assembly to overcome the issue. Please make use of the blog to know more about the functionalities of Behaviors. 
 
 
Please get back to us, if you need any further assistance. 
 
Regards, 
Arulpriya 



EH Eric Hinkle April 14, 2020 05:31 AM UTC

Thank you very much for your time, but...
I just trying to get through your GetStarted sample or even just pasting a simple spreadsheet control over to a new Project.

I tried using the Create NEW PROJECT and selecting from the SyncFusion Templates for Spreadsheet and I get same problem.
I added .dll to GAC just in case also installed from nuget.

Heres is a pic a the error by just dragging a spreadsheet control over to a new window. (pic included)
I just want to compile ANY of your samples/demos, Im not changing a thing. Just tryng to Learn by following your samples.

Could you include a sample solution of a simple spreadsheet with ribbon that compiles in VS2019 C# .Net 4.6?
Thanks Again!


Attachment: SpreadSheetGetting_Started_8e4b58de.zip


AR Arulpriya Ramalingam Syncfusion Team April 15, 2020 04:25 PM UTC

Hi Eric, 
 
Thank you for the update. 
 
We have created a simple sample with our latest version as per your requirement and the SfSpreadsheet with ribbon is working fine at our end. Please make use of the below sample. 
 
 
Please get back to us, if you need any further assistance. 
 
Regards, 
Arulpriya 



EH Eric Hinkle April 16, 2020 06:00 AM UTC

Thanks Arulpriya ,

That code compiled just fine.
Other then the same QAT problem as the other ribbons its seems to be all working.

Thanks Again..

I Still cant create a SfSpreadsheet on a window without errors, Im going to try to reinstall the syncfusion software an try to clean Visual Studio
Before this I had version 17 installed, maybe some remenants of this old install is the cause of my problems.

Update****
I un installed the Synfusion Essentials 18....42  and created a test Project using NUGET 18.44 libraries and the spreadsheet control was applied to window just fine...
 
will now re install syncfusion esentials 18...42 software and try to create spreadsheet from installed libraries instead of NUGET libraries
after installation of syncfusion esentieals 18.1.0.42 and draging a spreadsheet control to a WPF Window I get the same error as before
NullReferenceException: Object reference not set to an instance of an object.

SO I beleive there is a problem with the distributed syncfusion essentials 18.1.0.42 package.

Using Visual Studio 2019, WPF, .net 4.6

This is the only control in the installation that I have found so far with this problem


Note: 
The QAT problem occurs when minimizing ribbon, its been reported.. here https://www.syncfusion.com/forums/153173/sfrichtextribbon-quickaccesstool-error



RY Ryan April 16, 2020 05:27 PM UTC

I am having the exact same issue with the same setup as Eric.


AR Arulpriya Ramalingam Syncfusion Team April 19, 2020 06:04 PM UTC

Hi Eric/ Ryan, 
 
Thank you for the update. 
 
We could understand the scenario and suspect that the issue might be occurred due to Ribbon control and forwarded the query to our development team for further validation and update you with further dtails on 21st April. 
 
Regards, 
Arulpriya 



AR Arulpriya Ramalingam Syncfusion Team April 21, 2020 03:26 PM UTC

Hi Eric/ Ryan, 
 
Thank you for your patience. 
 
The reported issue is related to Ribbon control as mentioned in the forum #153173. We will update the fix details on 28th April that forum as we promised and we appreciate your patience till then. 
 
Please get back to us, if you have any other queries. 
 
Regards, 
Arulpriya 



EH Eric Hinkle April 21, 2020 05:47 PM UTC

Hi Arulpriya,

Thanks for the quick response, you guys are doing a great job with your support!

Eric


AR Arulpriya Ramalingam Syncfusion Team April 22, 2020 04:36 PM UTC

Hi Eric, 
 
Thank you for your appreciation and please get back to us, if you need any further assistance. 
 
Regards, 
Arulpriya 



EH Eric Hinkle May 1, 2020 05:57 PM UTC

Any updates on this problem?

Thanks
Eric


PM Piruthiviraj Malaimelraj Syncfusion Team May 5, 2020 10:05 AM UTC

Hi Eric, 

Sorry for the delay reply. 

We have checked the same issue reported in #153173 with SfSpreadsheetRibbon and tried the same solution given in that forum #153173 and it resolves that NullReference exception issue when minimize the SfSpreadsheetRibbon. We request you to use the solution provided in that forum and please let us know if you faced any other issues. 

Regards, 
Piruthiviraj 



EH Eric Hinkle May 9, 2020 03:15 PM UTC

Hi Piruthiviraj 

That solution offered in case  reported in #153173 doesn't seem to solve this problem.
I can add the sfSpreadSheetRibbon control to a window by dragging over the control with no problems, 
but when I try to add the sfSpreadSheet control I still get the same error reported.

I'm NOT using the RibbonControl at this time, Im just trying to ADD a spreadsheet control to a blank window... from you SyncFusion essentials installed software.


As stated before this only happens when using your controls from an installed version of your SyncFussion Esentials,
 if I use the Nugget Package version and I dont have the Syncfusion Essentials installed  this error does not occur.




AR Arulpriya Ramalingam Syncfusion Team May 11, 2020 07:47 PM UTC

Hi Eric, 
 
Thank you for the update. 
 
Adding SfSpreadshet for .Net core compiled properly at our end regarding the nuget and essential studio issues, we suspect that the fix for that specific case might be included after the 18.1.0.42 is released. So, please confirm us that whether the, nuget for 18.1.0.42 version also compiles the project without any error. If not, the fix for the reported version will be included in our upcoming release. Also, let us know, if you need patch for the issue with the version 18.1.0.42 which will be better for us to assist you further. 
 
Regards, 
Arulpriya 



EH Eric Hinkle May 12, 2020 10:42 AM UTC

Hi Arulpriya ,

After further testing. 
1. While having Syncfusion Essentials 18.1.0.42 installed
     a. used Nuget Spreadsheet 18.1.0.42  Got Same Problem
     b. used Nuget SpreadSheet 18.1.0.43 Problem Fixed

2. After Removing installed Syncfusion Essentials 18.1.0.42 from computer
     a. used Nuget Spreadsheet 18.1.0.42  Got Same Problem
     b. used Nuget SpreadSheet 18.1.0.43 Problem Fixed

Conclusion all WPF version 18.1.0.42 sfSpreadSheet Controls have some type of problems
Versions 18.1.0.43 and above seem to work fine

If you have  Patch to fix my registered 18.1.0.42 version it would be great, if not I could always use the .43 version with a registration number (trying to avoid that) for simplicity

Thanks!

Eric


AR Arulpriya Ramalingam Syncfusion Team May 13, 2020 09:09 PM UTC

Hi Eric, 
 
Thank you for the update.  
 
We need to check the fix details that we have moved after our main release with development team. So, we will check and update you the patch details on 15th May, 2020 and request you to use the nuget version v18.1.0.43 in the meantime. 
 
Arulpriya 



AR Arulpriya Ramalingam Syncfusion Team May 17, 2020 09:43 PM UTC

Hi Eric, 
 
Thank you for your patience. 
 
We have validated the bug details of SfSpreadsheet that was released in 18.1.0.43 nuget package and we have not fixed any issues related to the reported case. So, we suspect that it might be resolved through the solution on the forum #153173 or any other dependent assemblies’ fixes. So, would request you to use the nuget package while our next main (2020 volume 2 planned to deliver by end of July) release rolled out. 
 
Please let us know, if you have any other queries. 
 
Regards, 
Arulpriya 


Loader.
Up arrow icon