On Windows, I installed MonoDevlop and tried compiling the SQLite example which requires the Mono.Data.SQLiteClient reference. I opened up "Edit References" within MonoDevelop and I have absolutely no Mono references available with the exception of Mono.Cairo and Mono.Posix.
I thought perhaps I'd made a mistake by no installing the Mono framework first, so I installed Mono, then did a repair installation on MonoDevelop but the references are still not there?
Can somebody help me please?
Cheers
Sparky
Firstly, I believe Mono.Data.SqliteClient has been deprecated in favour of Mono.Data.Sqlite.
By default, MonoDevelop on Windows targets the .NET runtime for building/running/etc. The libraries available in the "Edit References" dialog are those installed into the target runtime, i.e. .NET.
If you have Mono installed, you also have the choice of targeting Mono. You can change the default target runtime using the Preferences->.NET Runtimes options panel, or change it for only the current solution using the Project->Active Runtime Menu.
Regardless which runtime you build with, you should be able to run/debug with another runtime using the Run->Run With... menu.
You could also install Mono.Data.SQLite into the .NET AssemblyFolders.
Related
When restoring packages via solution's context menu option "Restore NuGet Packages..." the MonoDevelop IDE still marks references to NuGet libraries as invalid and complains about non-existing namespaces. Restarting IDE helps as it clears MonoDevelop's cache, but is there a way to do this automatically? Perhaps some option in some settings that I've missed?
Not currently. Whilst MonoDevelop will detect assemblies that have been removed, and indicates this in the Solution window by marking the reference in red, it does not detect assemblies that been added back.
Debugging MonoDevelop it seems as though MonoDevelop detects changes to the solution file and project file and will reload them. Other changes, such as assemblies being restored, are ignored.
If possible I will have a look at changing the NuGet addin so it asks MonoDevelop to check the references after a package restore.
Good morning.
I am trying to setup haxe development tools in monodevelop as shown in this tutorial.
My problem is i can't find the haxe language binding the in add-in manager.
Does anyone know the solution to this issue?
Best regards
Guilherme Silva
Even the haxe binding dated 14/3/2013 only works for Monodevelop 3.0. I was able to download Monodevelop 3.0.6 from sourceforge. If it still doesn't work through the add-in manager, you can manually download it (link below) and install by file.
resources:
http://addins.monodevelop.com/Project/Index/41
http://sourceforge.net/projects/monodevelop.mirror/files/?source=navbar
I ran into this problem too. I believe it's because the Haxe language binding doesn't currently support (MonoDevelop/Xamarin Studio) version 4. And they don't currently seem to offer trunk builds, so we might be out of luck!
http://monodevelop.com/download/trunk_builds
I'm trying to use Castle Windsor with Log4Net facility. I've installed the packages through Nuget.
The requirement for this to work is to use Full profile Castle.LoggingFacility. Nuget referenced the Client Profile version.
How can I force Nuget to install the Full profile version?
I might be wrong but it sounds like the issue with the target framework setting on your project:
for Castle.Windsor to work it has to be set to .NET Framework 4 rather than to .NET Framework 4 Client Profile.
You can configure it by opening project properties, tab Application (in Visual studio) or just editing the project file.
If that's about the version of the package after all, then usually using NuGet you can append a flag install-package Castle.Windsor -version 2.5.3 to specify which one to install, but I couldn't find any options there when it comes to Castle.LoggingFacility.
I had the same problem earlier and I think you should check your packages.config file. There could be targetFramework="net40-client",
which points NUGet to the packages\Castle.LoggingFacility.3.2.0\lib\net40-client directory.
Simply change it to net40 and all's done.
Is it possible to use the protobuf-net library in an application that targets Windows RT? I tried adding it via NuGet to my project but I receive this error:
Successfully installed 'protobuf-net 2.0.0.480'.
Successfully uninstalled 'protobuf-net 2.0.0.480'.
Install failed. Rolling back...
Could not install package 'protobuf-net 2.0.0.480'. You are trying to install this package into a project that targets '.NETCore,Version=v4.5', but the package does not contain any assembly references that are compatible with that framework. For more information, contact the package author.
You need a newer version. Version 594 has support for 4.5.
In the package manager console (Tools->Library Package Manager->Package Manager Console) run:
PM> Install-Package protobuf-net -Version 2.0.0.594
Or download it from the project web site.
Yes, the more recent builds have full support for .NETCore (aka "WinRT", "Windows Store Applications", or "Metro", or "Modern UI", or whatever they want to call it today). As Eli notes, you can obtain it by specific version, or you can get it from the google-code download.
Note that for the best performance it is recommended to use "precompile", the new precompiler, because .NETCore has no support for meta-programming: without this, it will be using reflection at runtime, and will not be anywhere near as fast as it can be. This is included in the google-code download.
I created an NPAPI plugin that I'm packaging within a Chrome extension. I'm able to successfully install and use the extension in Chrome on Windows 2003 and Windows XP 64-bit.
However, when I install the plugin on Windows 7 (either 32-bit or 64-bit) or Windows XP 32-bit, I'm unable to use the extension within Chrome. The chrome logs reveal the error message "Couldn't initialize plug-in".
I ran the dependency walker in all of my environments and it looks like in the environments where the extension doesn't work, they all have in common the warning message "Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module." (the DLL's in question are SHLWAPI.DLL, IEFRAME.DLL, and MPR.DLL) whereas the environments where the extension does work don't have this warning (although one of them does warn of a delay-load dependency module not being found).
Should these DLL dependencies be different across different versions of Windows? What's the best way to resolve them? Or is the plugin failure most likely not related to these DLL dependencies?
Rebuild your project without dependencies on the runtime libraries by compiling your binaries with the "/MT" compiler flag instead of the default "/MD".
If you depend on open source code, make sure to rebuild each of those projects with the "/MT" flag, otherwise you will be chasing these runtime DLL issues forever.
shlwapi and ieframe are probably unrelated to your issue; seeing those errors is a common issue. not sure about mpr.dll, haven't seen that one.
You might try a FireBreath plugin and compare the dependency walker results and see if you can spot anything you're requiring that firebreath doesn't, since firebreath has no external DLL dependencies.