Once we have an updated Feature Pack, you’ll have the usual way to get the assembly, and as I said, we’re considering adding it to the NuGet package as well. Again, I agree you shouldn’t need to install the full SQL Server product just to get this assembly merely as a workaround for now, you can install it (on any server, not necessarily your production server) to get a copy. We’re including all the assemblies you need, including, in the NuGet package – with SqlServerSpatial the outstanding exception. We could reference v14 of this but currently that would require installation of SQL Server vNext/CTP onto Production servers which isn’t ideal and I can’t find a Feature Pack which might have a standalone CLR Types install for it.I guess if the NuGet package was updated to v14 (currently v11) and included native assemblies and a utility to load them it would provide a workable solution although it would still include beta SQL Server assemblies? Our aim is to deliver a single Report Viewer control that supports multiple versions of SSRS (currently, SSRS 2008 through 2016 and now vNext too), not just SSRS 2016. Im building a Web Site (Visual Studio Version 2013 in TFVC ) using ASP.NET task group my source have Microsoft.ReportViewer Package.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |