Carry over from social.msdn.microsoft.com...
http://social.msdn.microsoft.com/Forums/en-US/adodotnetentityframework/thread/4993d0bf-94e8-4d14-aff1-3458b4ad467f?prof=required
Original Post
I try to migrate a project from 2010 EF 4.3.1 (modified EntityObject generator template) up to vs 2012 rc, ef 5.0 rc and .Net 45 rc.
Painfully, my old T4 template doesnt work any longer. Where can I get the correct template to migrate it to EF 5.0 ?
I can compile the old project, but after starting the app I receive an exception with "different scheme detected".
My contribution, still unresolved
The EntityObject code generation template was available in VS 11 Beta on a "clean" machine, so I would imagine it's an upgrade issue/conflict, possibly related to having EF 4.2 June 2011 CTP installed prior (despite uninstalling).
VS 2012 Repair - did not fix the problem
VS 2010/2012 RC Uninstall/Reinstall - did not fix the problem
VS 2012 RC install on a clean machine - don't have time atm
Screenshots
What I'm expecting to see when adding a code generation template
What I see when adding a code generation template
Only DbContext in Extension Gallery
We are finishing verifying VSIX versions of the EntityObject and Self-Tracking Entities code-gen templates. These should be available in the Visual Studio Gallery (or the online tab of the "Add code generation item" menu) shortly if verification goes well. I will reply here as soon as they are uploaded.
Sorry for the long wait on these ones. The templates are now available on Visual Studio Gallery. See this page for details - http://msdn.microsoft.com/en-US/data/JJ613116#EntityObject
~Rowan
Related
I've inherited an old project which uses Devexpress 8.2.4 - so i went and installed an appropriate DXperience Subscription v8.2.4. Now, when I try to open the designer through Visual Studio 2019, I get a:
"This method explicitly uses CM policy, which has been obsoleted by the .NET Framework. In order to enable CAS policy for compatibility reasons, please use the NetFx40/LegacySecurtyPolicy configuration switch. Please see http://go.microsoft.com/fwlink/?LinkID=155570 for more information."
Then I tried to open the project in VS 2010, and upon attempt at opening the designer, same CAS policy error happens.
After editing the VS2010 DevEnv configuration file (and respective config file for VS 2019), as Thomas suggested in his answer here, my Visual Studio 2019 just started crashing during start, and my Visual Studio 2010 successfully started but it then crashed upon trying to select the designer object.
Yes, I'm trying to get this designer for Devexpress 8.2 to run in either IDE - I just need to get it to work so I can hopefully add a QR Code(is this even possible in v8.2.4???).
I just don't know how to access designer to actually graphically update the report. I did some Devexpress projects myself but using v19 and newer, but I'm having trouble now, opening this designer for old Devexpress 8.21.
Any help would be appreciated as this HAS to be done by tomorrow.
Also, if v8.2.4 doesn't support QR Code (an XRBarCode object), what would be an alternative for adding that QR Code functionality? Would I have to upgrade to newer versions - would that break something?
Thanks!
enter image description hereTrying to use SSRS in Visual Studio 2019 Community.
I am able to create a new "Report Server Project" Project in VS. However, when I try to "Add New Item" in the Project, I get the Error message:
Member not found. (Exception from HRESULT: 0x80020003 (DISP_E_MEMBERNOTFOUND))
I did install Data Server and Processing when downloading VS and also added the Extensions:
Microsoft Analysis Services Projects
Microsoft Reporting Services Projects
SQL Server Integration Services Projects
Which all seem to be active. I should also note that the "Add New Report" Wizard does work, it's the "Add New Item" that is throwing the error.
Any advice on how to correct?
Thanks to anyone helping!
I got this error and i solved it by adding the references for report viewer libraries in my current project, so basically when you create a new report project those dll are not included by default and visual studio can't find them.. Do a right click on your project and select Manage Nuget packages and install those two packages:
Corrected.Microsoft.ReportingServices.ReportViewerControl.Winforms (Current version = 150.1358.0)
Microsoft.ReportingServices.ReportViewerControl.Webforms (Current version = 150.1427.0)
Note: i am using Visual Studio Enterprise 2019 but i think the solution will work for 2017 too
So I hit the exact same error and got blocked. After googling for some time, seems MS has accepted that it's a bug, and they have this solution bundled as part of the new Preview ( Visual Studio 2019 version 16.9 Preview 3) and yes this is pretty new, like was release 3 days back when I'm writing this. Once I install and test I'll comment on this thread, but by the release notes (https://learn.microsoft.com/en-us/visualstudio/releases/2019/release-notes-preview#16.9.0.pre.3.0) looks like they've fixed this. I can't wait for the 16.9 to be release (16.9 is still not out), hence installing Preview to continue.
Update: So I installed Udpdate, and then i had to install the reporting service extension again(else it was saying reporting service project to be non-compatible), but post that I'm now able to add a report.
As of 3/8/2021 - I was running Visual Studio Professional 16.8.6 and was experiencing this issue. I upgraded to 16.9.0 (release data of 3/2/2021). Unlike ssethi11, it did not require the reinstallation of the SSRS extension.
The Official 16.9.1 is released.
Update visual studio and it should work now
I have a project in Visual Studio 2017 with .NET Framework 4. For reports I use the RDLC designer, but I have a problem. The designer creates the reports using RDL 2016 and I need you to use the 2010 definition.
Can I configure this?
I need it since the program has to be compatible with Windows XP and there is no ReportViewer Runtime that supports RDL 2016 for Windows XP.
I had the same problem, but if a did a new report it was all right, the new report was created and saved with the old schema:
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition". (report viewed with a text editor)
When I added a parameters and re-saved, VS turned the schema in
new schema:
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition"
But I found a solution that work also with Windows XP:
I install all necessary to manipulate the report with VS 2017 (in Visual studio 2017 are all external plug-in), then change the reference of my project e take 2 new referenze to this DLL:
1)
..\project\packages\Microsoft.ReportingServices.ReportViewerControl.Winforms.140.340.80\lib\net40\Microsoft.ReportViewer.WinForms.dll
2)
..\project\packages\Microsoft.ReportingServices.ReportViewerControl.Winforms.140.340.80\lib\net40\Microsoft.ReportViewer.Common.dll
After that all work.
This new version of DLL handle both "old schema" and "new schema"
You can check ReportViewer version and installed in your Visual Studio 2017 using PM>
(Before doing this you have to delete previous Report viewer references )
https://www.nuget.org/packages/Microsoft.ReportingServices.ReportViewerControl.Winforms/140.1.291.2731477-rc
This package Manager work for me.
PM>Install-Package Microsoft.ReportingServices.ReportViewerControl.Winforms -Version 140.1.291.2731477-rc
Reporting solutions in VS have always been tied to the version of SSDT that is current at the time of release. e.g. VS 2015 only supported the Sql Server 2016 report schema.
I think the answer is that you might be able to do something to change the schema it uses by editing the XML directly, as suggested by Ricky A, but for proper, designer support this isn't going to work.
Article from Microsoft on schema versions supported here doesn't mention anything other than schema v2016 support in VS 2017: https://learn.microsoft.com/en-us/sql/reporting-services/plan-for-report-design-and-report-deployment-reporting-services
I am fairly sure that your VS licence will cover old versions, and different versions live happily side by side, so install whichever other version you need for the reporting project you are editing (along with the correct version of SSDT/BIDS etc).
Although too late, but I have fixed this issue by installing this package :
Microsoft RDLC Report Designer
Install-Package Microsoft.ReportingServices.ReportViewerControl.Winforms -Version 140.1.291.2731477-rc this saved my ass
For a couple of weeks now I have been unable to merge Views within Visual Studio 2013 in response to conflicts when getting Source Code from Visual Studio Team Services. I am sure I used to be able to this (we recently moved from Visual Studio Professional 2012 so I cannot be one hundred percent certain - automerging may have been sufficient in the early days of the project).
The "Accept Merge" and move to next change/conflict buttons are all greyed out and inoperable. See screenshot snippet-
This originally only happened with Views, but now seems to affect some other classes. Changes are highlighted and indicated on the scroll bar so the diff tool otherwise appears to be functioning. This only originally affected me, but now affects a new colleague into the team.
I can still either Keep Local Version or Take Server Version but this is rarely sufficient. This leaves me manually altering the local copy to apply changes highlighted by the merge tool. (Edit - See a better workaround in "Second Update" below).
Has anyone come across this before?
Visual Studio 2013 Premium (patch RTM/Update 1/Update 2 - all with the same problem), with Resharper 8.2 (originally 8.0.2) C# and Web Essentials installed. Running on Windows 7 Professional x64.
Project is ASP.NET 4.5 using MVC 5.1.2 (now additionally updated from MVC 5 where the problem first occurred) (upgraded from MVC 4 following the upgrade instructions on the ASP.NET website) in C#, using latest versions of Razor (3.1.2) and Entity Framework (6.1.0 RTM).
Edit: Initially a repair install of Visual Studio 2013 appeared to have fixed the issue. It has now however returned exactly as it was before. Since it took an hour to do the repair I cannot repeatedly do this in order to merge views. I am currently able to round trip the solution between Visual Studio 2012 Update 4 and Visual Studio 2013 in order to do merges in Visual Studio 2012 where it is working normally.
Second Edit: I am currently manually resolving conflicts by selecting the desired code (local/server), saving the merge window and then closing it which will prompt to accept the merge result. This seems to function but is obviously sub-optimal. It may however be helpful for other users.
In the event, installing Resharper 8.1 on top of 8.02 appears to have fixed it fixed it briefly before the problem returned yet again. I had previously completed a repair install of Visual Studio Premium 2013 as well - which briefly seemed to have fixed it before it broke again. I only mention it in case the fix is cumulative.
I am unclear if it was a bug in Resharper that was somehow preventing the merge, or a persistent problem with the installation that the upgrade cleaned up (Resharper removes previous versions and then installs updates, rather than attempting to install over the top). Update - I am extremely confident that this is not related to ReSharper and that it was the configuration of Visual Studio as a result of re-installing the extension and not the extension itself that fixed the issue.
In either case, the issue (for now) seems to have disappeared and this seems to be related to the upgrade, or is an extremely strong co-incidence.
Colleagues with the same versions of Visual Studio and Resharper, working on the same project, the same version of Windows and (in one case) the same hardware were not affected, so it seems likely it is an edge case niche issue caused by corrupted data somewhere.
I have a current working theory that this is related to different patch versions of Visual Studio (for example Visual Studio 2012 Update 2, Visual Studio 2013 RTM, Visual Studio 2013 Update 1, Visual Studio 2013 Update 2. This only affects Visual Studio 2013 for us.
Simple solution I use is carry on with your manual merge process once you are done simply Close the Merge-* tab (the one you are using to merge files) this will bring up a prompt for confirming if you want to Save the changes made (this is the merge changes you made to your local file) click 'yes' Now it comes back to Resolve Conflicts tab and brings up another prompt asking if you want to Accept Merge Result, click 'yes'(this is same as the button Accept Merge)
Since you have VS2012 installed and merge is working there, you can create a link to its TF.exe in VS2013, similar to one on the picture below, and fix the issues there. Set Command to c:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\TF.exe and Arguments to resolve.
You do that in Tools->External Tools.
I'm trying to open a TFS Build Process Template (DefaultTemplate.11.1.xaml) file, incorporating an activity from Community TFS Build Extensions. I'm following instractions from here, section Get the custom activities into Visual Studio. I had no problems with that back in the RC version of Visual Studio 2012 but now, after upgrading to the release version, an attempt to open the file ends up in an error:
System.Xaml.XamlException: 'The type ‘InArgument(mtbwa:BuildSettings)’ of property ‘BuildSettings’ could not be resolved.'
TFS itself doesn't seem to have any problems running builds based on this template.
I am able to open the file without the trick, but then of course the custom activities are not displayed properly.
Check this out:
http://blogs.blackmarble.co.uk/blogs/rfennell/post/2012/08/30/Type-InArgument(mtbwaBuildSettings)-of-property-BuildSettings-errors-in-TFS-2012-RTM-builds.aspx
Quote:
"if the Visual Studio class library project you were using to manage the process template editing was targeting .NET 4.5, it needed to be 4.0. Well with Visual Studio 2012 RTM this is no longer the case, in fact it is the other way around."
I don't really think this is a great answer but I don't have enough rep to comment...
Build action on the xaml file is set to None?
I had a similar issue when opening build templates in VS 2012 RTM, but I was able to open the xaml "a little," meaning that I could open it in the workflow designer, but a lot of it was just the error activity. I found some errors to the effect that I should add references which I had not needed before (neither in VS 2010 or VS 11), such as PresentationCore and PresentationFramework. I wish I remembered more detail to pass on to you on this point.