Web reporting library which is not SQL ReportViewer - google-chrome

I deal with ReportViewer and RDLC since 2005.
Ever since that I am failing always in new troubles and problems, It most time working okay but also It sometime give me so much headache.
Common stricture for reporviewer for me is that only working as should work in IE.
So I start wondering is there time to look for other library which can replace ReportViewer.
Most of time I developing business apps, so called ERP.
I am looking for library which can be included in project written in C# asp.net web forms, can also use local resources as printer , paper properties and others, reports should be able to develop separately in different layer.
I know that there is Report Bulder for Delphi and I guest that there is other reporting library for asp.net C#. Does Crystal Reports can work on WebForms ?
Are there any other which can bi installed inside Chrome or Firefox as extension.

You can try our SharpShooter Reports. It is optimized for ASP.NET MVC however you can easily add it to any HTML page as it needs only several lines of JS code.

Related

Do HTML5 development using grunt and bower with WebSite project or create HTML5 Web app in Visual Studio 2015?

I want to build a custom PURE HTML5 Web Template, for HTML5/CSS3/JavaScript single page application development, and then use that as a starting place for SPA HTML5 web development.
Microsoft clearly recommends using Web Applications, but provides NO pure HTML5 web application template, thus this task is left to end users.
I am not asking if I should use an ASP.NET Web Site or ASP.NET Web Application instead I am asking, what template configuration can I arrange that will let me use the most modern HTML5 tools and workflows, and is it the Web Application (with .csproj or .xproj project file) or Web Site project (a folder based project)?
For projects where a developer needs to build a pure HTML5 SPA, maybe with ExtJS or maybe with Angular, or something equivalent, the first choice made is between File-> New Web Site and File -> New Web Application.
If it may be that later my HTML5 project may get some ASP.NET added later, it is clear I should choose File -> New Web application, but there is NO HTML5 template provided, so I am looking to build my own Template and use that. But what should it be based on?
For the WebSite option, you click file New Web Site, and you get a folder-based project, but none of the new grunt/bower support.
I am looking for a way to get the best of both choices. Can I get grunt/bower support if I click File New WebSite? Or can I do pure HTML5 work somehow if I click File New Project?
It is possible to crib a pure HTML5 Web Development .csproj + .sln project together myself, starting with some examples that used to be on codeplex and are now on GitHub
It seems to me that the benefits of a .csproj or .xproj based root for pure HTML5 development are:
I can specify only the files I want to see in my project explorer.
I can easily add ASP.NET webapi controllers to my "pure" project without rebuilding the project.
Can I use one of the ASP.NET 5 (DNX) Web Application templates (.xproj), and just delete all the C# stuff, to get a working pure HTML5 development template, and retain all the new javascript grunt/bower tooling? Or do I have to stick with Web Site (folder level) projects, and their visual studio 2005 era website development features, for pure HTML5 html/css/javascript development?
Update: If close voters who voted "opinion" based would be so kind enough as to point out where I call for any opinion, that'd be great. I'm asking for help DEVELOPING a template for Visual Studio, and I believe that is on topic and not at all a call for opinion. To develop a template you must make a choice. Which one will provide the most complete HTML5 tooling including grunt and bower and full javascript syntax highlighting, jslint, bundle, minify, etc?
When developing a template, my research so far shows that:
Patience, grasshopper, it's early days. ASP.NET Core 1.0 just released, but does not include certain elements, including a new .xproj style set of projects for basic pure HTML 5 web project development (name not yet even announced, but let's hypothesize, it might be called Core Pages), whatever it is, the Microsoft "franchise reboot" for Pure HTML5 Development with Microsoft Visual studio either doesn't exist yet, or is in early stages of internal development. Whatever template I could make today might be obsolete in three weeks or three months if Microsoft makes a move here.
For now, for people who can live with it, File -> New Web sites works fine, and I haven't found any technical documented reason why you CAN'T use it for new development, just a caution from Microsoft that it might not be the best choice, if a File -> New Project template can meet your needs. You can see from the way that ASP.NET Core 1.0 today works (just in time automatic-recompile without rebuilding in ASP.NET Core brings a core feature of the WebSite world over into the WebApp world at last) that its new tooling and the new .NET Core features inside dnx and dnvm will finally "restore the Balance of Nature" that I feel has now been divided over the last 10 years by the WebSite/WebApp dichotomy. Not yet, but that's part of the core design elements I have understood from studying the ASP.NET Core architecture.
For ExtJS, the Sencha Ext JS plugin for Visual Studio provides a File -> New Web Site option, and this works fine. I downloaded and tested it yesterday evening and it works fine. If I want to invoke grunt or bower, or bundle and minify, or any other web-dev workflow task, I can do so manually using an external command prompt window as well. So while it might not be as shiny as I was looking for, it's possible to get work done. The Ext JS plugin provides full Ext class hierarchy code-completion, and starter templates for both pure HTML5 (via file New Website) and HTML5+ASP.NET (via File New Project). When evaluating their plugin I initially thought there was NO way to do a pure HTML5 app inside visual studio because I was totally unaware of the File New Website option, and thought (incorrectly) of this area of VS as deprecated.
For Angular SPA development INCLUDING .NET there is this template, and it appears you could use it and just not write any ASP.NET server side stuff if you wanted to do a pure HTML5 SPA.
I would probably suggest starting with the angular SP development template linked above and modifying it to subtract angular and insert ExtJS, or using the ASP.NET 4.6 plus ExtJS template provided by Sencha's IDE plugin, and just subtracting all the ASP.NET code from that template. I don't yet have a starter template suggestion for the ASP.NET Core 1.0 .xproj world yet.
It should be possible, and seems quite easy to use .NET Core and ASP.NET Core as a key part of the tooling for a pure HTML5 development environment. In particular "dnx web" is a useful way of locally developing, as it is even more lightweight than using IIS Express. It should be equally feasible to develop for HTML5 with "DNX web" (kestrel) as the lightweight static server for pure HTML5, and either a full Visual Studio 2015 project (either website or webapp), or using just a modern web-editor like Visual Studio Code.
I hope that other developers who are still confused, as I was about the now-10-years-long split-personality issue in visual Studio with regards to New Web Site and New Web Application, may finally see some light at the end of the tunnel.
Update: Q4/2016: It actually looks like the two way split personality issues in VS 2015 will get worse in VS 2016 (Currently in preview as VS15) because there will be THREE ways to open a project, open solution/csproj via one menu item, open web project via another, and open folder via a third.

SSRS and pentaho alternative

I am using Microsoft Reporting Services to provide users with custom reports. I create them in Business Intelligence studio, deploy them and have a website where users can view those reports.
Now i need i new tool to do almost the same. I need to create reports and users has to be able to view them in PC, Mac, mobile phone, tablet, etc. Microsoft Reporting Services has some problems with Android and iOS, and that is the problem for me. Users cannot scroll the report (if it is longer thant report viewer window), expand does not allways work and etc.
I need a tool, to create same reports and allow to view them anywhere. I was thinking about pentaho, but it is no exactly what i need. Maybe somebody has any solutions?
Pentaho's analyzer tool is good on tablets/mobile but unfortunately it is EE only, not community/open source.
If you're happy with enterprise another option is yellowfin?
Alternatively with the community edition of Pentaho you can make use of CTools and there is a very good dashboarding framework with explicit support for mobile devices - may be worth looking at that?
Why exactly is pentaho "not exactly what you need" ? What are your perceived issues with it?
I have not used pentaho. However, I know any limitations in the web viewer control are based on browser support and interpretation. One workaround to these limitations is to reference the reportexecution2005 interface in your project and call the Render method with HTML40 format and designate HTMLFragment in the device context header, this will return the report html content as a byte[]. However, any custom paging/printing/zooming would have to be re-implemented in your web app :(

Need to convert VB 6 forms to Html forms

We have developed a standalone application using visual basic 6.
Now we are changing the standalone application to web application.
Is there any way to convert VB6 forms into plain HTML forms so that my work will be reduced alot.
please give your suggestions.
Edit: I am new to VB6 and .net technology
Don't even think about "converting". It's not just a "conversion" process. The entire paradigm is different between web applications and desktop applications. They're just totally different.
ASP.NET web forms try to make the differences less apparent. However, the differences are still there, and are still huge.
What you should do is separate your business logic from your forms logic in your VB6 application. You will then be more easily able to convert the business logic into .NET business logic. You'll still need to create equivalent forms, but the logic will be the same.
You cannot simply convert VB6 form to html, there is some website which provides this conversion.. but this will increase your work more
refer - VB to HTML convertor

An HTML 5 only Business-Oriented application

I am planning to create a HTML5 web application. I have a couple of queries though-:
I wished to know if it is possible to create a business oriented application using HTML5 only without a backbone like Asp.Net. I found a lot of articles on google suggesting the use of Asp.Net MVC, or ASP.Net website as a base template but none suggesting a HTML+js alone approach.
Given the web standards update for VS 2010 SP1 and js libraries like Modernizr, is it possible to create an app completely in HTML5 using Visual Studio.
You're eventually going to want to do some server side work, and for that you would need either Java, PHP, or ASP set up to intercept and process commands... you could go ahead and create everything in HTML+JS alone, and use the file writer for "permanent storage" but that's really cutting corners, and can lead to catastrophe down the line depending on where exactly you are trying to take this application of yours.

What is the most common way to integrate reports into a .Net web application?

The following are the 3 ways that I know and would like to know the experiences from SO users.
URL-based
Report Viewer Control from Visual Studio
Web Services
Not sure what you're using as a report generator on the server side, but I've found that serving up reports in PDF format is a relatively pain-free, cross-platform way to go. Almost everybody has Adobe Reader installed.
Update: sorry, I missed the SSRS tags, but you can output SSRS reports to PDF:
http://www.codeproject.com/KB/reporting-services/PDFUsingSQLRepServices.aspx
I still recommend PDF for the delivered report format. Cross-browser and near-universal, two things that make me (and clients) very happy.