I am trying to use the Sharp-shooter Silverlight report viewer control.
This control has a server side component that renders the reports as XAML for displaying in the client side control. I have tried manually installing the rendering extension, according to the instructions on their website, and also the instructions on MSDN.
I have basically copied the dll's into the reporting services bin folder and added the following line to rsreportserver.config file:
<Extension Name="XAML" Type="PerpetuumSoft.ReportingService.XamlRendering.XamlRenderer,PerpetuumSoft.ReportingService.XamlRendering"/>
I've also added a line into the rssrvpolicy.config file as specified on their site.
After I made these changes I went into windows services and restarted the Reporting Services services but I get the following error when I try to run reports:
rsRenderingExtensionNotFound: An
attempt has been made to use a
rendering extension that is not
registered for this report server
Is there anything else that I need to do to use a custom rendering extension within SSRS 2005?
Turns out it was a problem with the dll, after much to-ing and fro-ing with the guys at Perpetuum software they figured out the bug and put out another release.
Related
I am working with report in ASP.Net Core using AspNetCore.Reporting to create report. When I executed the report in windows machine it work fine. However if i executed on linux machine I got this error.
An error occurred during local report processing.;The definition of the report '/var/task/Reports/Report.rdlc' is invalid. An unexpected error occurred in Report Processing. Unable to load shared library 'kernel32.dll' or one of its dependencies.
Note: I deploy the application using serverless in AWS and aspnetcore as the runtime.
Can anyone help to solve my problem?
It doesn't work on linux and that package hasn't received an update since 2018.
There are other alternatives such as syncfusion pdf (paid) or Rotativa that creates pdf files from MVC views, rotativa uses wkhtmltopdf (open source and cross-platform).
At the end I use Itext/Itextsharp as alternative to create PDF. The functionality to create PDF is open source
I have a .NET Core MVC app hosted in IIS (development) as well as Azure App Service (production).
When I make a simple HTML change to a Razor View and publish just that view, it does not get updated.
It only gets updated if I publish the entire project.
This happens in both IIS and Azure app service.
Is this the default behavior or am I doing something wrong?
Here is the configuration page from Azure App Service:
When you publish the complete program to iis, iis compiles and runs it. .net core mvc disables runtime compilation by default, so even if the view is updated and released, the program that is already running will not compile the new view.
If you want iis to use the new view after the VS update and release the view, you can add a line of code to the startup to enable the function of compiling and running.
Add Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation Nuget package to the project.
Add following code in startup.cs:
services.AddRazorPages().AddRazorRuntimeCompilation();
Publish entire project.
After all of these, once you update view and publish. IIS will display new view.
Here is my test result.
You don't need to do any operations on the portal.
The article provided by Lex Li talks about the content of Razor when compiling. Simply put, C# server code can be written in the .cshtml file. After compilation, it will become projectname.Views.dll, so when you modify When the .cshtml file is not sure which projects it is associated with, it is recommended to update it globally to avoid bugs caused by version issues.
Regarding your current problem of partial update, it is also easy to solve. First, you need to define the file or folder inclusion options when compiling. You need read offical document first.
Below screenshot is my test project.
After my modification and settings, you can publish your customized files or folders to the azure production environment. (The code setting part is for reference only, coding according to specific projects)
In the post, you said that you want to publish an html file, then you can right-click the file or folder and select publish file or folder.
Right click test folder.
From the screenshot message below, we can see that the partial update was successful, the speed is very fast, the modified content is also prompted, and the global update is not performed.
prompt:
The above steps are all tested and passed, and the answers and code parts given are for reference only.
If you encounter problems during the operation, it is recommended to raise a support ticket on the portal.
I'm trying to publish changes to a .NET Core 3.1 web app from Visual Studio 2019 using FTP, however the process doesn't update my .cshtml views.
The app works properly on my local machine, I deleted the contents of the 'bin' directory before publishing, and my publish settings delete all of the existing files on the server before copying new ones over, so this process appears to be somehow copying over views which are no longer available anywhere?! I've not changed any of the 'build action' properties and most of the configuration in Startup is the default MVC template.
Microsoft docs reference a NuGet package (Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation) and using AddRazorRuntimeCompilation() in Startup, but this didn't seem to have any effect.
I find it incredibly bizarre that views aren't updated during a publish by default. I also find it bizarre that in this day and age SFTP appears to be unsupported (wth). Hopefully I'm just doing something wrong rather than this process being silly. Any ideas?
Restarting the Kestrel service used by my server seems to have resolved it...there has to be a more obvious solution though as this method requires shell access.
Using SQL Server 2016 CTP3.2 Report Viewer (13.0.800.111), only the toolbar is shown.
It looks like a Power BI method is missing.
Also, will there be a NuGet for Report Viewer?
Just ran across this thread. The question: "will there be a NuGet for Report Viewer?" -- Yes, look out for a NuGet version of 2016 based report viewer controls this month (September).
Note that the controls will not expose the PowerBI method described here.
To overcome broken report viewer you have to purge its files v.13.0.1601.5 from GAC and use updated ones from nuget package: Microsoft.ReportingServices.ReportViewerControl.WebForms.Preview (version 130.1700.305, published 2016-09-20).
Make sure you have the latest version of SQL Server Data Tools installed. Earlier versions incorrectly GAC'ed certain libraries that will cause issues.
The Report Viewer Control is designed to be included in projects via nuget. It's not a good idea to add the libraries to the GAC.
If deploying the control on an intranet site make sure that the page is targeting HTML5.
More info at this page: https://github.com/Microsoft/Reporting-Services/blob/master/Docs/Get-Started-With-RVC.md#next-steps---read
It works:
Sample of the missing javascript method "OnPowerBIFeaturesRelease" in localmode
Was able to avoid this script error with the 2016 Report Viewer. Try adding these missing references before the Report Viewer definition.
Note: This will only work if your Report Server is on the same domain as your Website. You can also manually copy the files into your project and then serve them locally if your on a separate domain.
While deploying the webpart into the site collection using central administration wizard ,I am receiving the error like this.
Error: Cannot add the specified assembly to the global assembly cache: System.Web.DataVisualization.dll.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 0faee23c-f6f0-4frr-8463-2ef5fdc8bfc4
can anyone tell me how to solve the problem?
That assembly is part of the MS Chart Controls. They may not be installed on your server. Try installing them first and then re-deploy your webpart. The controls can be downloaded here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=14422
You may also need to do an IISRESET to release open handles to the assembly.