I wanted to try WebKit by following this tutorial, but gmcs compiler was't able to find "webkit-sharp-1.0" package. Where can i get it and how to install it?
The original Webkit# no longer seems under development (latest commit is from 2009) and I have never encountered any windows packages for it but you can use open-webkit-sharp which is working on Windows.
Related
Just downloaded and installed SDK Net 7.0.100 and it broke existing applications and they won't load any more in VS 2022 or Rider.
Copied the follwing error:
error : SDK Resolver Failure: "The SDK resolver "Microsoft.DotNet.MSBuildSdkResolver"
failed while attempting to resolve the SDK "Microsoft.NET.Sdk". Exception: "Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadManifestCompositionException: Workload definition 'wasm-tools' in manifest 'microsoft.net.workload.mono.toolchain.net7' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain.net7\WorkloadManifest.json] conflicts with manifest 'microsoft.net.workload.mono.toolchain' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain\WorkloadManifest.json]
at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.ComposeWorkloadManifests()
at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.Create(IWorkloadManifestProvider manifestProvider, String dotnetRootPath, String sdkVersion, String userProfileDir)
at Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver.CachingWorkloadResolver.Resolve(String sdkReferenceName, String dotnetRootPath, String sdkVersion, String userProfileDir)
at Microsoft.DotNet.MSBuildSdkResolver.DotNetMSBuildSdkResolver.Resolve(SdkReference sdkReference, SdkResolverContext context, SdkResultFactory factory)
at Microsoft.Build.BackEnd.SdkResolution.SdkResolverService.TryResolveSdkUsingSpecifiedResolvers(IList`1 resolvers, Int32 submissionId, SdkReference
I experienced a similar problem.
I uninstalled the 7.0.100-preview.5.22307.18 sdk using add remove programs and then changed the TargetFramework in the project file to use 7.0 and then I was able to load the projects.
EDIT: This is officially documented in the release notes known issues.
I'm from the .NET SDK team. Sorry you're going through this. I would love to comment on the other answers, but I don't have the reputation to do so.
What Tim Farley suggested is an officially endorsed workaround; uninstalling any preview 7 SDKs with add/remove programs should resolve the problem.
As for why this happened and why uninstalling preview SDKs will fix the issue, there's a bit of an explanation I put here: https://github.com/dotnet/sdk/issues/28947#issuecomment-1307987337.
TLDR: Some workloads were renamed in the middle of .NET 7 preview development to support things like multitargeting, and when you download the new RTM old preview files interfere can with it.
Updating the TargetFramework is recommended but it's unrelated to this issue. Usually breaking changes for each .NET version and related new features are gated behind your TargetFramework (TFM), so things don't break until you update the TFM, not when you update the SDK. (Unfortunately, not true in this case.)
In response to whether this will happen again or not when upgrading to .NET 8, per Scott: with how workloads are currently structured this issue would happen again. We're discussing how to make changes to prevent this from happening again though as it's not ideal. We're also considering adding dotnet workload clean or something to repair this for you. Communicating with us on the SDK GH thread, or with me here, is a good way to send us feedback about this.
Repairing Visual Studio installation did not help me. Neither did uninstalling .net 7 faulty workload ('wasm-tools'), since any attempt to uninstall or repair it ended up in the same error message.
Being ran out of conventional options to address the issue, I just went ahead and physically deleted the conflicting folder: microsoft.net.workload.mono.toolchain, leaving second one microsoft.net.workload.mono.toolchain.net7 intact. It luckily solved problems on my machine. From now on I'll be more cautious on installing Ms RC packages
I had a similar problem, even on new .Net projects. I uninstalled the 7.0.100-preview.2.22153.17 SDK using add remove programs and I was able to create a new project again. I am now left with only one .Net 7.0 SDK (from Visual Studio) as shown below.
Uninstall Microsoft .Net SDK 7.0 preview
I had the same issue as above except on my M1 mac. I followed the following guide and manually removed all the directories for all the .net 7 runtimes and sdks. Then reinstalled .net7 and all seems to be well now. rider can open my projects and the dotnet cli no longer complains
Not sure if a similar scorched earth approach will work for the windows folks.
https://devkimchi.com/2021/11/24/removing-dotnet-sdks-from-macos-manually/
I had the same issue, except that no preview version of .NET 7 was currently installed on my system, but the preview artifacts were still in the C:\Program Files\dotnet\sdk-manifests\7.0.100 directory. My solution was to uninstall the stable version of .NET 7 (not the version from VS 2022), then install and uninstall 7.0.100-preview.7. Doing so resulted in the preview artifacts being removed and this error being resolved.
I had same problem, but i think the problem because M1 mac
Had the same problem. Deleted manually installed net 7 sdks in windows uninstaller.
I found out that I needed to rm -rf **/obj
(delete all folders named obj) in the solution root folder after upgrading from net 6 to net 7, in addition to dotnet clean
I've searched for solutions on this but found no one getting this error and it is never very descriptive. Wanted to see if someone has a solution or point me to a resource that covers it.
Basically, I have a .Net Standard 2.0 Project that I'm installing Selenium WebDriver and ChromeDriver to. However, when I try to install them from Nuget Manager in VS2017 (either via Nuget.org or locally), I get the error below:
"The local source 'C:\Users\ME\Desktop\dist' doesn't exist."
I've tried placing ChromeDriver on the desktop thinking that was the cause but no change. Also tried command line install of the Nuget package but it fails as well.
Any assistance would be very helpful.
When you bring up the NuGet manager, make sure that your package source is set to nuget.org. It sounds like you've got it pointed to some local path that doesn't exist.
All,
I am writing a Powershell cmdlet. Got everything working for the cmdlet on my local machine. Looked at what is needed to access remote machines and it seems I need a reference to Microsoft.Management.Infrastructure.dll in my project. I have search my system to no avail.
So I hit Google. I verified I am running Windows 7 SP1. Downloaded and installed the Windows Management Framework (WMF) 4.0. No luck. Still no DLL. I verified I met the minimum requirements.
I then found a Microsoft page that said version 5 required WMF 4.0 as a prerequisite to the install. So I upgraded my .Net Framework to 4.6.2. Then installed WMF 5.0. Still no .DLL anywhere on my system.
Has anyone experienced this before? Can anyone shed some light as to what I may be doing wrong? I am using Visual Studio 2010. Is this the cause of the problem?
I have continued to search the web and found articles that stated the Microsoft.Management.Infrastructure dll was part of the Windows 7 SDK. Tried installing the SDK with no effect. Still cannot get the dll load on my system.
Continuing to look for a fix.
The easiest way I found to get this dll - and reference it automatically within my VS 2017 Project was via packet Manager console:
Install-Package Microsoft.Management.Infrastructure -Version 4.0.0
As stated here on this Microsoft page: Nuget Gallery
No Need to install any SDK or so only to get this dll.
could you check C:\Program Files (x86)\Reference Assemblies\Microsoft\WMI\v1.0 to see whether can find it there ?
The best resolution I was able to find to this issue after repeated attempts with numerous combinations of .Net frameworks, WMF versions, and Windows 7 SDK's was to install the Windows 8 SDK.
According to the official website, Mono now supports System.Speech (in 5.0) . However, I am unable to reach a linux build of version 5.0
"Packages for MonoDevelop 5.0.0.878 not yet available. The latest available version is MonoDevelop 4.2.1"
Is there any way of achieving this? (tarballs, git?)
Notes
I am using ArchLinux
The best way to use the last monodevelop on Linux is to get it from git (it's very fast and very easy :)
Now I'm using it (5.1) on Ubuntu 14.04.
You can get the source code from here:
git clone git://github.com/mono/monodevelop.git
and then compile it: http://monodevelop.com/developers/building_monodevelop
Remember that you must have installed Mono runtime 3.x.
I am answering this a little earlier but i think it applies right now too because Xamarin have already provided Mono 3.6.0 builds(technical preview) for Debian and derivatives.And with in a few months the best way to get anything latest related to mono will be from Xamarin official builds.They will provide Mono and some important applications including Monodevelop for every Debian and Centos derived Linux distributions.
See this link......
mono builds for many Linux distributions
Having just built Monodevelop the hard way, I would recommend downloading a tarball from http://download.mono-project.com/sources/monodevelop/ as everything is already included and requires no additional downloads except the some apt-get installs.
If you really want to use the git repo here is how to fix the two major issues I had.
1) I'm behind a proxy so I had to edit git module files to not use the git protocol as described in this post https://stackoverflow.com/a/11410074/1516326
2) You have to Import the Mozilla LXR certificates for Mono, so NuGet can update correctly, using:
mozroots --import --sync
For the entire process follow these instructions: http://www.monodevelop.com/developers/building-monodevelop/
I start using Ubuntu 9.04 on my laptop. What I really want is to be able to write my C# projects on Ubuntu, including unit testing. Could anyone guide me how to setup it?
In addition to the basic packages Matthew suggested, you'll also want the monodevelop-nunit package, which allows you to run and debug unit tests from within the IDE. For the debugger, you'll want monodevelop-debugger-mdb. You probably also want monodevelop-versioncontrol for SVN support, mono-xsp2 for running ASP.NET apps, and monodoc-browser for the docs viewer.
Maybe you're best off just installing all of the packages 'suggested' by the MonoDevelop package -- I believe the Ubuntu package manager has a way to do this easily from its GUI.
Beware that Ubuntu splits up Mono into many, many small packages, so if something's missing, use the apt-file tool or similar to find which package you need to install.
Ubuntu doesn't have Mono 2.4 packages yet; if you require 100% up-to-date packages, your best bet is to use openSUSE. The only way to get 2.4 on Ubuntu right now is to build from source -- and if you decide to do that, please read How not to break Mono installations first.
You probably already updated to 10.04 in the meanwhile. For 10.04 (and 8.04) you can use the badgerports. I didn't try it (yet), but it looks reliable.
I would suggest using 2.4 as it has all the latest .net goodness.
There are two guides I would suggest using:
http://blog.ruski.co.za/page/Install-Mono-on-Ubuntu.aspx
http://www.centriment.com/2009/04/01/building-mono-24-from-source-on-ubuntu-810/
The latter lets you keep the mono install that comes with ubuntu so you can still install apps from synaptic. I would suggest using this. Both guides however are really clear about what is required to install it. It looks menacing at first but if you take a couple of hours to follow it then you will see it is actually quite easy.
Good luck
EDIT: Added mono-devel
I use Ubuntu 8.04, but what do you really need to setup? Doing (if you haven't already):
sudo apt-get install monodevelop nunit mono-devel
should give you what you need. And there are plenty of tutorials for both monodevelop (e.g. http://monodevelop.com/Documentation/Creating_A_Simple_Solution) and NUnit (e.g. http://www.nunit.org/index.php?p=quickStart&r=2.4.8)