Recently, I downloaded mono. I can not use:
using System.Drawing
It just shows me an error. Are there any additional packages that i need to download, or is it just a bug ? Went to add-in manager and i have all packages installed.
this is what i got from error list:
Error CS0234: The type or namespace name Drawing' does not exist in
the namespaceSystem'. Are you missing `System.Drawing' assembly
reference? (CS0234)
You need to add a reference to the System.Drawing libraries. If you're using MonoDevelop, right click Preferences -> Edit References, and under Packages make sure that "System.Drawing" is checked.
Related
I recently registered Mysql.Data.dll assembly in GAC on 64bit Ubuntu 14.4 to use it following this example with an ASP.NET Mono project and verified.
I realized that although it is registered in GAC, it's not directly usable from Edit references dialogue on Monodevelop.
I tried to see how can this be made possible, the possibilities exists for Visual Studio which is something I don't need.
Doubts:
If the assembly is un-usable what is the concept of registering it in GAC?
How can this assembly be provided by a package (and advertised through a .pc file?
How can this assembly be bundled together with the application?
Are the steps I followed incorrect?
I'm having a issue with a Visual Basic 2013 program I made (in vb.net) and the issue is with MySQL.data.dll, I've tried changing copy local to true in the GAC, I've tried upgrading my MySQL.data.dll to the most recent version but whatever I do it only works if the MySQL.data.dll folder is in the same folder as the executable when running it.
(Do note that this error only occurs on other machines, not my machine)
This is the error exactly:
[Could not load file or assembly 'MySql.data, Version=6.9.5.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d' or one of its dependencies. The system cannot find the file specified.]
Please help, I don't want to have my users have to put MySQL.data.dll in a file with the exe just to be able to run it (for obvious reasons.)
Check the version of the MySQL assembly against the versions appearing in the compiler output.
Do not use the error list look at the Output window and select Build from the drop down and look for errors.
The most probable cause is your application is linked to specific (possibly multiple) versions of MySQL, and there is a conflict on the specific version of MySQL referenced. You might also want to change the specific version property of the assembly reference...
How exactly does the "Specific Version" property of an assembly reference work in Visual Studio?
asp server error ' Could not load file or assembly ' but the assembly is definitely there.
It's pretty simple. You need to make sure the reference to the assembly is correct. I'd avoid installing MySQL into the GAC. Don't install the MSI, if you have uninstall it, then download the zip archive
mysql-connector-net-6.9.5-noinstall.zip
Extract the files to a folder reference those assemblies in your solution. If you're using source control check the folder containing the MySQL assemblies into source control, with the rest of the solution.
If you have more than one assembly referencing MySQL you should check that they are all referencing the same version, from the same location and/or have the "Specific Version" property set to false and "Copy Local" set to true.
We've got a project using Ormlite.MySql built for .NET 4.0.
Ormlite and its dependencies are loaded via NuGet (it's ServiceStack.Ormlite.MySql 3.9.54), including MySql.Data 6.6.5.
When we try to run the code, however, we get a dependency error:
Could not load file or assembly 'MySql.Data, Version=6.6.4.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d' or one of its dependencies. The system cannot find the file specified.
The ServiceStack.OrmLite.MySql package in NuGet lists MySql.Data as a dependency, but doesn't list any specific version. In reflector, I can see that ServiceStack.OrmLite.MySql.dll is, in fact, referencing 6.6.4.0 of MySql.Data.dll.
Has anyone encountered this issue? I hate to hack the config file to redirect assmbly binding in general (always feels like a kludge).
I've just encountered the same problem. I solved it by downloading the Mysql.data.dll version 6.6.4.0 from servicestack on github: https://github.com/ServiceStack/ServiceStack.OrmLite/blob/master/lib/MySql.Data.dll
I had the same error. Just install with nuget : Mysql.data (it work for me)
nuget install the right version : "6.6.4"
(you could verify the version number in the nuget description)
I am trying to add a dll reference to my SSIS package (2012) with a script Component. The IntelliSense is working for me and I don't see error when coding. However, I get the following error:
Could not load file or assembly 'XYZ, Version=1.0.0.0, Culture=neutral, PublicKeyToken=XYZ' or one of its dependencies. The system cannot find the file specified.
Please help.
If this is a custom DLL, then you will need to install it into the GAC (global assembly cache) for it to run outside of SSDT.
An assembly cannot be installed into the GAC unless it's strongly signed. Once it's signed, from a Visual Studio command prompt, registration would look like gacutil -if MyRadAssembly.dll
After adding the latest version of FluentValidation.MVC3 to a NopCommerce aplication i am receiving the following error,
[Exception: Could not load file or assembly 'FluentValidation,
Version=3.2.0.0,Culture=neutral, PublicKeyToken=a82054b837897c66' or one
of its dependencies. The located assembly's manifest definition does not
match the assembly reference. (Exception from HRESULT: 0x80131040)
]
Nop.Core.Plugins.PluginManager.Initialize()
in C:\Nop 2.2 Source -Copy\just4fashion2.2source\Libraries\Nop.Core\
Plugins\PluginManager.cs:144
I think this is due to the project referencing an older version of the fluent validation dll
but im not sure how to fix this, is there a way to pinpoint the error further?
Any advice you can offer will be much appreciated.
You might find this post helpful on how to track down dependencies in your application. I think you're absolutely right that either your project or a dependency your project is taking references an older version of FluentValidation.
Another thought is if you add the dependency to FluentValidation.MVC3 via NuGet, NuGet tends to place assembly binding redirects in the web.config. This will tell any assemblies with a hard dependency on an older version of an assembly to "redirect" to the latest version.