ReSharper 8.2 indicates lots of errors in my Catel 4 viewmodels in VS 2012 Update 4 when targeting .NET 4.5. Catel 4.0.0-unstable0463 is installed.
In every VM, derived from ViewModelBase, Re# gives me "Cannot resolve symbol" on every occurrence of GetValue, SetValue, and RegisterProperty. I get the same error when trying to reference WindowLogic.PropertyChanged.
Re# errors go away when I select .NET 4.5.1.
Project was created for 4.5, and NuGet used to install packages.
.NET 4.0 is also clean after re-installing the proper version of Catel.
Thanks.
-reilly.
Related
I run Linux (Elementary) on my machine and for .NET MVC projects, I use Monodevelop ( 5.4.0.199 version), but I cannot open projects developed using Visual Studio 2017.
Opening the .sln file, the following error will keep appearing: Error while trying to load the project '/home/emma/Documents/My-App/My-App/My-App.csproj': Unknown ToolsVersion '15.0'.
I tried to update the monodevelop version, but with no success. I, also, tried to do what is suggested here: MonoDevelop can't import VS2013/2015 solutions , but, with no success.
Can you, please, help me solving this issue?
You have two choices:
Update MonoDevelop to a version superior to 7
Change ToolsVersion from 15.0 to 14.0 or smaller based on which version of VS is supported by your version of MonoDevelop*
*To check which version of VS is supported for each MonoDevelop version check the history of MonoDevelop requirements Here
How do I remove the last update to my Xamarin ?
I keep getting this error
Error MT0091: This version of Xamarin.iOS requires the iOS 11.0 SDK (shipped with Xcode 9). Either upgrade Xcode to get the required header files or set the managed linker behaviour to Link Framework SDKs Only (to try to avoid the new APIs). (MT0091)
but when I upgrade to Xcode 9, there where too many bugs...
so I need to just go back down.
I am upgrading a solution to Visual Studio 2012 (and 2013, but that's a side issue)
I am encountering the following error (many times) when compiling the test projects:
Error 345 The type 'System.Action'
exists in both 'c:\Users\neil\Documents\Visual Studio 2013\Referenced
Assemblies\Third Party Dlls\Moq\Moq.dll' and 'c:\Program Files
(x86)\Reference
Assemblies\Microsoft\Framework.NETFramework\v4.0\System.Core.dll' .....
We are using Moq 4.0000, and the solution is using .Net 3.5 in all projects. It looks like the .Net framework now has a System.Func<....> implementation (previously only defined in Moq?) Oddly we haven't had this problem with VS2008, also using .Net 3.5.
Does anyone know how to resolve this?
Action and Func with many parameters were added only with .NET 4.0. Was it initially a .NET 2.0 project? In that case, you can try to remove the System.Core.dll from the references and try to see if the project compiles. Despite the name, it is unessential and was added only with .NET 3.5. The cleanest solution would be to upadate your library, Moq, with an updated one that fixes the clash in .NET 4.0. If that is not an option, follow Pratick advice to use assembly extern aliases.
I have a C# Windows Forms application that makes use of SQL Server 2008 R2, .NET Framework 4, .NET Framework 4 Client, and Entity Framework Code First.
SQL Server 2008 R2 Express exists on the machine, and the program does create the database and tables.
[Update]
I tried installing .NET framework 4.5, but I got this message:
Blocking Issues:
The .NET Framework 4.5 is not supported on this operating system.
Warnings:
Setup may not run properly, because the Windows Modules Installer
Service is not available on this computer.
with this link
The operating system is Windows XP 2002 SP3 running inside VMware Player.
[Update 25th May 20xx]: I found a link here that caused me to think the problem is just that ClickOnce won't install on Windows XP. However I recreated the set up in Visual Studio 2010 and have the same error.
[update 26 May 20xx]: I created a test project with Visual Studio 2012 and Entity Framework 5 and was able to successfully install on Windows XP using ClickOnce. Strangely I was then able to publish a version of my big application that worked.
I am not sure what is going on. I also did install a program containing Entity Framework 6 on my test computer - but this would not have been referenced by my big application.
Have you tried installing .NET 4.5?
I know it sounds absurd, but we're seeing the same issue: Entity Framework 5.0 (4.4) targetting .NET 4.0, Code First on SQL Server CE.
Installing .NET 4.5 made the issue go away. We're still investigating, because we also have a couple of Windows XP clients.
Update:
Portions of the Entity Framework 5 code are part of the .NET framework itself (that's why there's a 4.4 version for .NET 4.0 that e.g. doesn't support enums, while the 5.0 for 4.5 does).
It seems this issue is related to that since installing .NET 4.5 inexpliccably solves this.
For Entity Framework 6 those portions were moved to Entity Framework, so Entity Framework 6 doesn't depend on framework specifics anymore. We've updated to Entity Framework 6.0 alpha 3 and everything seems fine.
Now, I don't like running alpha code, but this is the only solution we could find.
I am using .NET 4.0 and Visual Studio 2010 (which I will eventually upgrade, but not quite yet). I ungraded from EF 4.1 to EF 5 via NuGet and ran Enable-Migrations (via the Package Manager Console) but got this error
No context type was found in the assembly 'UI'.
I Googled around and found this SO post.
The scenario described by the poster is slightly different as he is using VS 2012 and .NET 4.5. Either way I'm not sure if this will solve my issues. Do I need to be using VS 2012 and .NET 4.5 to use Migrations? How do I solve my issue?
In order to NuGet commands work correctly, you should specify the default project:
So you should change the dropdown value from UI to Model (I presume). Actions should not depend on VS version.