I have converted an .rdlc rerort from SSRS 2005 to SSRS 2008. Now when I am going to build that project I have got error.
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.
Please give me solution for this.
Just stumbled upon this question since I was having the same problem. In my case, I had a reference to an older version of ReportViewer.WinForms. When I switched versions, everything worked fine. Might not be the same case as yours, but just thought I'd chime in in case anyone else finds this page.
I faced an almost similar problem but in another version of visual studio ( 2012) and i found out that the problem was from the version of Microsoft.ReportViewer.WebForms.dll or winforms. You may be still referencing the old one related to your current version of visual studio so check the dll version and if so remove it and add the latest one
I encountered this same problem, and the solution for me was to edit the file:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0
\ReportingServices\Microsoft.ReportingServices.targets
And change line #2, which previously said this:
<UsingTask TaskName="Microsoft.Reporting.RdlCompile"
AssemblyName="Microsoft.ReportViewer.Common, Version=9.0.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
To this:
<UsingTask TaskName="Microsoft.Reporting.RdlCompile"
AssemblyName="Microsoft.ReportViewer.WebForms, Version=10.0.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Once that was done, my program started compiling again.
I had exacty the same problem.
For me the solution was to exclude the report from the project and to add it again. After that it compiled successfully.
I'm not entirely sure why #user2702793's answer got down voted, because that suggestion just saved my career:
Consider
Creating a blank SSRS 2008 report and copying all the content out of the SSRS 2005 report into the new one
copy the name of the SSRS 2005 report if you want to keep the name of the report intact
delete that report (SSRS 2005 one you just copied the content from into your new report)
rename your new SSRS 2008 (with the deleted SSRS 2005 report's content in it) and paste the report name in.
I had a very similar situation mentioned above except I wanted to retain my SSRS old versions instead of upgrading it. Which basically had me making a copy of the old version, copying the content out of the accidentally upgraded report and pasting it into the copied report, and copying the name of the upgraded report, deleting it and renaming my copied report to retain the same name of the report that just got deleted.
Edit: Of course in my case I also wanted changes done to the old report which was all in the upgraded report hence my lengthy work around to keep from losing my current changes.
The solution that worked for me was to run the .NET cleanup tool, I tried the .NET framework repair tool first and it did not work. I read the suggestions here
In ReportViewer properties in webform expand LocalReport/Path in the field put the correct path of report
This works for me...
It might be a conversion problem. Recreate a new 2008 report.
And I suggest using VS2010. I have the same problem when editing a report with VS2012.
Related
I have vs2017 my colleague has vs2015,
he installed report viewer by vs studio installer. we are working on same project when he creates new report(.rdlc) file, his report schema defination url is like;
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
So do mine, but when I add parameter from toolbox, it changes to below magicly;
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition"xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
Yeah I understood my external report viewer version is diffirent from vs integrated, its all behind this.
if I remove some unnecessary tags that I awere of via this post it works, but If I add any param or change the position of existing paremeter 2016 stuff comes in with its xml elements back.
So I need to tell VS
"Forget 2016. please continue using 2008 version"
Edited: They say "you should set to the correct Target Server Version". What does and how can I do this please elaborate the steps of this action?
removing vs 2017 and install vs2015 looks like certain solution but I dont want to chnage my ide just because of few unnecessary xml elements.
You need to change the TargetServerVersion to SQL Server 2008. This can be found in the Properties of you Visual Studio Project on the General tab.
There is a workaround. If you remove all the parameters directly in the xml you can change anything in the report viewer that it wont update to 2016. Do everything that you need to do and add the parameters back directly in the xml as your last step.
Heres an example how to add parameter in the xml
<ReportParameters>
<ReportParameter Name="YourParamName">
<DataType>Integer</DataType>
<Prompt>ReportParameter1</Prompt>
</ReportParameter>
</ReportParameters>
I had the same problem and well, I didn't can changue the TargetServerVersion,
I just installed Microsoft.ReportingServices.ReportViewerControl.WebForms from Nugget and it solved my problem.
Hopefully it can work for you
I installed VS.2017 Enterprise and start a web performance project. When I try to add a Web performance test to the project I receive the error:
"The Web test could not be loaded: Could not load the type
'Microsoft.VisualStudio.TestTools.WebTesting.SharepointInformation'
from assembly 'Microsoft.VisualStudio.QualityTools.WebTestFramework'
Version=10.0.0.0, .."
TL;DR:
Check installed prerequisites in the latter part of Create a web performance and load test project
In my case, replacing original file
C:\windows\assembly\GAC_MSIL\Microsoft.VisualStudio.QualityTools.WebTestFramework\10.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.QualityTools.WebTestFramework.dll
with
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\Microsoft.VisualStudio.QualityTools.WebTestFramework.dll solved the problem.
I tackled the same issue. Every time I created Web Performance and Load Test Project in Visual Studio 2017 Enterprise (with arbitrary .NET framework version) I got the same error when I tried to open *.webtest file. VS's user interface seemed incomplete and clicking on toolbars sometimes shown null exceptions.
At first, I thought I have incomplete installation, according to Create a web performance and load test project. I have even tried to completely uninstall and reinstall mentioned packages. Unfortunately, this did not help. I have also experimented with adding and removing reference to Microsoft.VisualStudio.QualityTools.WebTestFramework as there are several options in my reference browser, but without success.
There is not much information about WebTesting.SharepointInformation namespace. After a while, I discovered the existence of Microsoft.VisualStudio.QualityTools.WebTest.SharePoint.dll and after closer inspection, I have noticed that it references QualityTools.WebTestFramework assembly in C:\Windows\assembly\... that has the same assembly version and public key token, yet smaller in size compared to the one that is contained in VS 2017 installation. I have replaced it with VS2017's one and voila, *.webtest can be successfully opened.
The above answer is correct but the problem is the directory isn't accessible in my case due to some reasons so I just open my cmd and run this command. Just run, it will copy the file, but first turn of the vs.
copy "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\Microsoft.VisualStudio.QualityTools.WebTestFramework.dll" "C:\windows\assembly\GAC_MSIL\Microsoft.VisualStudio.QualityTools.WebTestFramework\10.0.0.0__b03f5f7f11d50a3a"
I am adding the RDLC (report wizard) to my asp.net web application. I am using visual studio 2010 and have installed the AJAX control tool-kit using Nuget package manager.
Problem is arising at the point when I am adding a new item and then opting a new item as rdlc. then as I click over rdlc, instead of adding an rdlc to my project I am getting following error.
"could not load file or assembly 'AjaxControlToolkit' version=4.1.7.1213, Culture=neutral.... or one of its dependency."
I am unable to understand why i m getting this error. Kindly suggest some ways to add the rdlc smoothly.
Thanks!!
Try copying the AJAXCONTROLTOOLKIT.DLL file to the following folder.
C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies
Hope this works.
It worked for me.
May be you get this problem again while adding Report Data also, if you are referencing to another business/ data layer project in the solution. Then also copy the dll of those projects to same folder as mentioned above.
After searching the SO forum, I cannot find a working solution for my question. If you find one, I would really appreciate it.
In Visual Studio 2012, I am building a C# project. I get the following error:
Source file 'Properties\Assemblyinfo.cs' could not be found.
I have this solution:
Source file 'Properties\AssemblyInfo.cs' could not be found
But, it does not work for me.
Actually, I have the 'Assemblyinfo.cs' in working directory, I can see it in VS solution explorer.
Have you tried deleting the assemblyinfo.cs files and then trying Clean and Rebuild solution? If you don't need versioning this might help you.
Have you tried a Clean Solution, followed by a Rebuild Solution?
The AssemblyInfo.cs file should be recreated on a build.
I got this error even after I tried to Clean and Build. I could also could see the AssemblyInfo.cs file. I found out that the build was interacting with a power shell script(not entirely sure how) in the solution directory.
Long story short, Every project, except the one I had added(where the problem was), was mentioned in that script. I added the missing info to that script and I could build again.
I doubt your case will be exactly the same, but I imagine there could be some script or something similar that handles/references all the projects, except the one where your problem persist. Try searching the files for the text of project names.
I have encountered this situation.
I find out why. It is usually due to confusion between mscorlib.dll versions.
There are two ways:
Change assemblyinfo version from 1.0.0.0 to 1.* (change value to *). See link:
MSBuild extensions AssemblyInfo fails with version number not valid
Get an error when trying to set the build version with the AssemblyInfo Task
The second way is simple, I have applied it successfully, that is reinstalling .Net Framework 3.5.
Clean and Rebuild did not help for me.
What helped was manually deleting ALL /obj and /bin files and then using Clean and Rebuild.
I am trying to run a solution which has entity model included but I am getting weird error which someone already had in the past and can help me solve this. My colleague says that the solution is running fine on his comp and on other computers too, but on mine comp doesn't want to work for some reason. Please let me know if I am missing something, he checked too, and it looks pretty much the same.
Here is the screenshot:
Every advice is welcome.
Thanks, Laziale
It seems you do not have OpenAccess ORM installed on your machine. You can refer this article, which demonstrates how to use OpenAccess ORM without installing.
If this is not the case and you have the product installed, you need to verify whether the OpenAccess.targets file is deployed under the MSBuild folder [C:\Program Files (x86)\MSBuild] and it tries to resolve the enhancer from the correct location. Additionally the Build Action for the rlinq file should be set to OpenAccessDeploy.
if telerik 2015 q1 is used, this issue comes. first check whether openaccess.target.dll is present in the path c:/program files(86)/msbuild. if not, place the one. then install telerik q1 installer. I got the installer from my team mate as it is not available in telerik site(deprecated)
.
I had the same issue this Offical Telerik post helped me.
TLDR:
In Solution Explorer right-click the project containing the rlinq and select Unload Project.
Right-click on the unloaded project and select Edit ProjectName.csproj (vbproj).
Add this to the end of your file:
<Import Condition="Exists('$(MSBuildExtensionsPath)\OpenAccess.targets')" Project="$(MSBuildExtensionsPath)\OpenAccess.targets" />