Environment: Vista, VS2010 SP1
Apologize if I seem to be repeating this but I have spent a day on this. Last ditch attempt before I reinstall VS2010!!
I tried
1. devenv /installvstemplates
2. uninstalled EF 4.1 and installed 4.0 CTP 5 and now it's not even opening VS2010. Asking me to install SP1 again!!
I used Web Platform INstaller to install SP1 and EF.
Most of the posts was on VS2008 and different scenarios. SO really not sure what happened here.
Thanks in advance for your time
-Soni
Related
My existing code work as expected with .net framework 4. But after upgrade to .net 4.6. Its not work
I also ran into this. Had to uninstall all 4.6 frameworks, and then re-install 4.5.2 Framework. And finally re-register in IIS by running aspnet_regiis -i
and then my CR started working again.
So removing 4.6 for Windows 2008 Server is the solution. For Windows 2012 Server, turns out the 4.6 is "hidden" as update KB3102467 that was pushed out around April 2017. Uninstalling that got the Crystal Reports viewer working again on our Windows 2012 servers.
Another answer for anyone... fix is simple but requires a manual change every time their is a patch\update for .NET Framework 4.6
Turns out the problem is that Crystal Reports looks for a folder that matches the version of the Framework including the "build".
The quickest way to manually fix this is go to the web page that has the Viewer and look at the source. You will find a line similar to /aspnet_client/system_web/4_6_xxx/crystalreportviewers13.....
Go to the servers hard drive and rename\copy that folder to the version it is looking for and you are back in business.
Our product needs to be compatible with versions of windows including Server 2003 and XP.
We have code first entity framework projects with various migrations.
We are deploying these migrations to create or update a database using the "migrate.exe", file version 6.0.21211.0, supplied in entity framework 6.0.2 nuget package.
When using XP itself with visual studio 2010 or Windows 7 with visual studio 2013 to install the package every time we run "migrate.exe", on an xp or server 2003 machine, we are getting a "not a valid win32 application" exception.
Is there a good reason why "migrate.exe" will not run on windows xp and windows server 2003 other than the fact they are operating systems that nobody really wants to support any more?
I managed to resolve this issue by downloading the source code for 6.0.2 version of entity framework, un-signing it in properties, then building it through .net 4.0 and not 4.5 by changing the solution configurations to Release40.
Source code can be found here:
http://entityframework.codeplex.com/SourceControl/changeset/7648d33dfb53589d9c32b605c61758a5a6c0b80b
I found it quite difficult to locate it.
You probably don't have .NET Framework installed on the machines where it fails.
(As a side note I believe both XP and 2003 go out of support soon so you may want to upgrade your environment...)
The ADO.NET blog at
http://blogs.msdn.com/b/adonet/archive/2012/04/09/ef-power-tools-beta-2-available.aspx
says:
Compatibility
The Power Tools are compatible with Visual Studio 2010 and Entity Framework 4.2 or later.
You can also install the Power Tools on Visual Studio 11 Beta, but you may receive the error "A constructible type deriving from DbContext could not be found in the selected file." This is caused by a bug in the Visual Studio 11 unit test tools where an older version of EntityFramework.dll is being loaded. We are working closely with that team to resolve the issue. As a workaround, you can delete the HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config\BindingPaths{BFC24BF4-B994-4757-BCDC-1D5D2768BF29} registry key. Be aware, however, that this will cause the Unit Test commands to stop working. Thank you, early adopters, for your superhuman patience with prerelease software.
My question is:
Does anybody know if this issue is resolved on VS2012 Professional RC? I have a pretty stable installation and don't want to mess up with it.
Yes, it is fixed in Visual Studio 2012 RC.
I installed a lot of ado.net entity framework versions and tools. one of them was this one: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26660
Now there are a lot of problems while trying to add a new entity data model, and also can't use any code generation tools such as dbcontext code generator.
What I want to know is how to remove all of these ef versions and reset my Visual studio 10.
Note, I repaired my vs, and reinstalled the SP1 but with no hope, the same errors are there.
here are 2 screen shots that may let you help me better:
installed items in my VS:
error appear after trying to add a new entity data model:
The uninstallation procedure of EF June 2011 CTP is described in this article. As you see in your linked download page there is red text in instructions describing issues with CTP. That CTP should have never been installed on your main development (production) machine because it breaks existing VS functionalities. The instructions directly says that it should be installed in non-production environment (for example virtual machine).
So I installed Entity Framework June CTP day before and all was fine until I went to add POCO's to the EF, that's when I got this error
So I thought to myself 'It must have been the CTP that's causing this, so I went and unloaded it. I restarted Visual Studio and was greeted with this message:
I hit No and Visual Studio finished loading my project. When I once again tried to add the POCO's I was greeted with this error:
So does anyone know what's going on and how I can resolve this issue? I know Entity Framework 4.2 has new items but for the time being I prefer the POCO way of doing things.
EF CTP 2011 is very first preview of EF 4.2. It also shows only subset of features expected in EF 4.2. First of all it is not for developing production code and it should not be installed on the machine where you write a production EF code.
It is expected that CTP can contain bugs - that is why CTPs are published - to collect feedback and find bugs. It is not clear what you actually did to get the error but if you have a technical problem with CTP ask on EF pre-release forum for help.
Why not simply remove EF 4.2 ? Removal guide here: http://blogs.msdn.com/b/adonet/archive/2011/06/30/announcing-the-microsoft-entity-framework-june-2011-ctp.aspx
I had exactly same problem and resolved it by uninstalling "SQL Server Tools for Data Framework June 2011 CTP" - download it at http://www.microsoft.com/download/en/details.aspx?id=26660, run and select the Remove option.
After that I was able to recover the Entity Framework tools to SP1 state using the steps in Uninstall section described at
http://blogs.msdn.com/b/adonet/archive/2011/06/30/announcing-the-microsoft-entity-framework-june-2011-ctp.aspx.