Crash during install of 2016.1 WPF Trial
Re: Crash during install of 2016.1 WPF Trial
Hi Jan,
I tried adding Stimulsoft.Report.Wpf, but that did not help...
On the other hand, I'm not showing the report. I just want to create the PDF on disk. That's all...
Hope to hear from you!
Patrick
I tried adding Stimulsoft.Report.Wpf, but that did not help...
On the other hand, I'm not showing the report. I just want to create the PDF on disk. That's all...
Hope to hear from you!
Patrick
Re: Crash during install of 2016.1 WPF Trial
Hello, Patrick!
I have checked your code and it absolutely correct. In your case you need only two assemblies: Stimulsoft.Base.dll and Stimulsoft.Report.dll.
Please replace one line of the code:
to
In the second variant report, rendering will be processed without report rendering progress and will be using WPF for report rendering process.
Also, can you say which error message you receive?
Thank you.
I have checked your code and it absolutely correct. In your case you need only two assemblies: Stimulsoft.Base.dll and Stimulsoft.Report.dll.
Please replace one line of the code:
Code: Select all
report.Render();
Code: Select all
report.RenderWithWpf(false);
Also, can you say which error message you receive?
Thank you.
Re: Crash during install of 2016.1 WPF Trial
Hi Jan,
I'm not getting any errors on any machine.
The reports are created, but on my dev-machine the data is not in the report (on my laptop this works OK). The data is missing in the report where the underlying data is not changed AND in the report where the new CSV file is attached...
Using report.RenderWithWpf(false) makes no difference...
I tried the same program in the meantime on another machine and there it works OK. So I think it must be something machine related... But what?
Is there anyway I can see in the debugger if the data from the CSV is loaded before, during or after the Rendering? Because it looks like it isn't... Maybe that would give me some clues...
Thx again for your time and help!
Patrick
I'm not getting any errors on any machine.
The reports are created, but on my dev-machine the data is not in the report (on my laptop this works OK). The data is missing in the report where the underlying data is not changed AND in the report where the new CSV file is attached...
Using report.RenderWithWpf(false) makes no difference...
I tried the same program in the meantime on another machine and there it works OK. So I think it must be something machine related... But what?
Is there anyway I can see in the debugger if the data from the CSV is loaded before, during or after the Rendering? Because it looks like it isn't... Maybe that would give me some clues...
Thx again for your time and help!
Patrick
Re: Crash during install of 2016.1 WPF Trial
Hello, Patrick!
So, the problem in data location. Report engine cannot find csv file or cannot load it. Please check that csv file on problem computer really exists and really have required the name. Also, try to access it from code.
Also, try to move it to something like c:\1.csv with the simple name and try again (maybe some problem with local culture info, some symbols in name or in the path). If report engine cannot load the file it does not generate the error and continue report rendering.
Thank you.
So, the problem in data location. Report engine cannot find csv file or cannot load it. Please check that csv file on problem computer really exists and really have required the name. Also, try to access it from code.
Also, try to move it to something like c:\1.csv with the simple name and try again (maybe some problem with local culture info, some symbols in name or in the path). If report engine cannot load the file it does not generate the error and continue report rendering.
Thank you.
Re: Crash during install of 2016.1 WPF Trial
The official version of 2016.1 installs ok, but when I try to start the designer I get the same error as PatrickV describes!
"Cannot locate resource 'images/toolbox/catinfographics.png'."
"Cannot locate resource 'images/toolbox/catinfographics.png'."
Re: Crash during install of 2016.1 WPF Trial
Hello,
Please try to check the last build 2016.1.9 from 2016.04.22 and let us know about the result.
Thank you.
Please try to check the last build 2016.1.9 from 2016.04.22 and let us know about the result.
Thank you.
Re: Crash during install of 2016.1 WPF Trial
Hi,
I have updated to 2016.1.(because of a potential solution for this problem: viewtopic.php?f=12&t=43331).
I have now the same problem as terjoh has: "Cannot locate resource 'images/toolbox/catinfographics.png" when trying to edit a report.
I have donwloaded a few SWPF_2016.07.01(2016.1.16) and some others, but had new issues. This time the above described error did not occur anymore, but I had issues with reports not being printed/previewed anymore or the application complaining about missing assemblies.
I was able to repair everything, so at least now I can run my app with 2016.1, but, of course, I still have the "Cannot locate resource 'images/toolbox/catinfographics.png" - issue...
How must I proceed to be able to use SWPF_2016.07.01 has this version has no complete installer like 2016.1. In what order must I install/de-install your packages to get this going and have the correct files in the GAC?
Regards,
Pascal
I have updated to 2016.1.(because of a potential solution for this problem: viewtopic.php?f=12&t=43331).
I have now the same problem as terjoh has: "Cannot locate resource 'images/toolbox/catinfographics.png" when trying to edit a report.
I have donwloaded a few SWPF_2016.07.01(2016.1.16) and some others, but had new issues. This time the above described error did not occur anymore, but I had issues with reports not being printed/previewed anymore or the application complaining about missing assemblies.
I was able to repair everything, so at least now I can run my app with 2016.1, but, of course, I still have the "Cannot locate resource 'images/toolbox/catinfographics.png" - issue...
How must I proceed to be able to use SWPF_2016.07.01 has this version has no complete installer like 2016.1. In what order must I install/de-install your packages to get this going and have the correct files in the GAC?
Regards,
Pascal
Re: Crash during install of 2016.1 WPF Trial
Hello,
You can use the Installer.exe utility from the build archive for remove/add all assemblies to the GAC.
Thank you.
You can use the Installer.exe utility from the build archive for remove/add all assemblies to the GAC.
Thank you.
Re: Crash during install of 2016.1 WPF Trial
I Aleksey,Aleksey wrote:Hello,
You can use the Installer.exe utility from the build archive for remove/add all assemblies to the GAC.
Thank you.
I had tried this but this ended up in messing up my libraries. I wasn't able to print anything anymore, preview were always blank and the application complained about an assembly "...editor..." missing.
Must I first use the Installer.exe from 2016.1to remove the corresponding libraries and then use the Installer.exe from the new release to add the new libraries?
Further, in my project, I do reference the libraries directly from the directory in which I have installed the packages. So after using the installer to first de-install from GAC and then re-install to GAC, I go to "references" and then remove the current library-references from the project (that still point to the old directory) and then re-add them from the new directory.
Regards,
Pascal
Re: Crash during install of 2016.1 WPF Trial
Hello, Pascal.
Unfortunately, sometimes the assemblies are stored in cache folders, so it's better to search for old assemblies and remove all of them before installing the newer build.
Thank you.
Yes, if you use Installer.exe utility. You should remove the old libraries with old Installer.exe, than install the new assemblies with new Installer.exe.PJoyeux wrote:Must I first use the Installer.exe from 2016.1to remove the corresponding libraries and then use the Installer.exe from the new release to add the new libraries?
Unfortunately, sometimes the assemblies are stored in cache folders, so it's better to search for old assemblies and remove all of them before installing the newer build.
Thank you.