I have an existing RDL report that I want to convert to an RDLC report for use in an MVC application.
According the the MSDN Site the way to convert it is to rename the .rdl file to .rdlc, include it in the project and then use a ReportViewer control to select the datasource.
Being MVC I don't have a ReportViewer control on my page, I was using this post to help me render the report into the Response stream.
I've renamed the rdl to rdlc and included it in my project but I get the following error when trying to open it:
The report definition is not valid.
Details: The report definition has an
invalid target namespace
'http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition'
which cannot be upgraded.
Any ideas how I can convert the rdl to rdlc without having to re-write it?
You cannot convert a SQL Server 2008 Reporting Services report .RDL into .RDLC - Microsoft only knows why.....
See Bill Vaughn's Retraction: The ReportViewer Control does NOT support SQL Server 2008 RDL in Local Mode for some expert insight.
In short: right now, Microsoft doesn't have a working story for converting RDL to RDLC in Reporting Services 2008.
To correct the earlier answer: you cannot render an SSRS 2008 RDL file with the VS 2005 or VS 2008 ReportViewer control in local mode, because the schema has changed in SSRS 2008, but the control was not brought up to par. VS 2010 comes with a ReportViewer control that apparently supports the SSRS 2008 schema.
If the schema were supported, no conversion would be necessary (other than renaming the file from RDL to RDLC, which is how it worked in a VS 2005 environment).
See my question on MSDN about this issue.
Actually, you can convert an .RDL to .RDLC. Copy the report to your report folder on your project, rename the extension from .RDL to RDLC. Just make sure you have the Microsoft.ReportViewer.Webforms reference. I have created a ton of reports, using the Report builder, built and tested them there, then copied them to my project (MVC). Just my 2 cents.
Related
I am facing a problem while opening the NopCommerce solution file from Visual studio 2015
The error message is
One or more projects in the solution where not loaded please to see
the output windows for details
Output window error
D:\nopcommerce\Presentation\Nop.Web\Nop.Web.csproj : error : The
default XML namespace of the project must be the MSBuild XML
namespace. If the project is authored in the MSBuild 2003 format,
please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003"
to the element. If the project has been authored in the old
1.0 or 1.2 format, please convert it to MSBuild 2003 format.
I have also shared screenshot please till how to solve errorscreenshot here
NopCommerce 4.0 is built on ASP.NET Core 2.0.
VS 2015 supports only ASP.NET Core <=1.1. You need to install VS 2017 to run NopCommerce 4.0.
Here is the link to official documentation
https://www.nopcommerce.com/boards/t/49380/nopcommerce-400-is-released.aspx
ASP.NET Core support in Visual Studio 2015?
Has anyone had any luck using MSBuild with Delphi 7 as part of a TFS 2008 (Microsoft Team Foundation Server 2008) integration? Curious if it is possible, and if it is, what is necessary to set it up.
Thanks!
Update: I am aware that the later versions of Delphi use MSBuild, but it would appear for right now upgrading isn't an option.
To use MSBuild with Delphi 7, you must first produce a representative .dproj file bearing the correct XML markup (as seen in later versions of Delphi). If you construct them properly, then MSBuild will recognize them, and (as directed in the XML markup) will place the appropriate calls to the Delphi 7 compiler.
It's simple enough, but it takes a lot of effort to manually produce the .dproj markup!
EDIT: This guy offers an apparently-functional automated solution to this problem, available on request!
You may write a MSBuild task that invokes dcc32.exe (delphi 7) and passes to it the appropriated commmand line (dpr file name). I wrote a similiar task for NANT in order to integrate delphi 7 with cc.net
We recently upgraded a major application to Visual Studio 2010.
Unfortunately, we are still using several database servers that are still running SQL Server 2000 (8.0.2055 to be precise).
According to this article (Link), "Since mainstream support for SQL Server 2000 ended on 04/08/2008, Visual Studio 2010 will only support debugging SQL Server 2005 and SQL Server 2008.
We have a lot of stored procedures that we keep in Source Control and execute them from within Visual Studio whenever we need to update them.
Is there any way around this restriction? 3rd-party tool, anything.
While researching this, I saw a few sites that indicate an ODBC connection could be used to get to the SQL2000 box. I was able to create a System DSN and then a Data Connection within VS2010, but am unable to connect to it.
Any help would be greatly appreciated.
Thanks.
Chris
The only way I've found so far is to extract our data library out of the project and keep it in VS 2008 targeted at 3.5 while we're building it. Once it's complete and ready, we open up the primary project in VS 2010, check out the changed files and then use the file system to copy the changed files over.
We then keep the supplementary 3.5 project in source control parallel to the primary project.
They will still build and function in .Net 4.0, but we have found that the IDE will not accept any connections or commands to them.
i did an upgrade and it caused lots of problems. unfortunately i didn't back it up. Is there anyway i can convert a 2010 solution file back into asp.net mvc 2008?
Make a backup of what's left of what you currently have before doing this ...
Create a new solution in Visual Studio 2008. Create new projects for the 2008 solution. Use the project menu or right-click the project and choose "Add Existing Items..." Choose all the code files .cs .vb, etc from your 2010 structure and include them in the 2008 structure.
Basically you're copying all the code back into a 2008 structure with the 2008 formatted project and solution files. The code shouldn't be substantially changed beyond repair. You might have to manually address some issues in the converted code but once you know what they are it will be a repetitive process more than anything.
If you are writing code of any importance you should be using a version control system like as SVN. I haven't tried Visual Studio 2010 yet, but can tell you from experience that the differences between 2005 and 2008 are laughably small. You can down convert a 2008 solution file by manually changing the first two lines from:
Microsoft Visual Studio Solution File, Format Version 10.00
Visual Studio 2008
to
Microsoft Visual Studio Solution File, Format Version 9.00
Visual Studio 2005
the project files are fairly trivial as well with the product tag changing from:
9.0.21022
to
8.0.50727
Please note the changes I have listed for project files may not be 100% accurate and I have not tested for differences between service pack releases. However, creating a new project in an earlier version of Visual studio, making a copy and then doing an upgrade should allow you to run a diff and provide a better answer than what is currently accepted.
i am trying to open my vs 2008 solution in vs 2010 beta 2. it converted the solution file and brings in the unit test project but it can't seem to bring in the main project. it kicks off the vs conversion wizard and says that it completed successfully but the project doesn't show up.
has anyone seen this? any suggestions?
Try this ASP.NET MVC project converter.