Bug 17108 - OpenTK and OpenTK-1 broken
Summary: OpenTK and OpenTK-1 broken
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.10.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-01-08 01:26 UTC by Herman
Modified: 2016-12-22 17:35 UTC (History)
7 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Herman 2014-01-08 01:26:35 UTC
This is what happens when referencing those OpenTK and/or OpenTK-1 assemblies:

Error	1	The "MangleLibraryResources" task failed unexpectedly.
Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'monotouch, Version=, Culture=neutral, PublicKeyToken=84e04ff9cfb79065'
   at Mono.Cecil.BaseAssemblyResolver.Resolve(AssemblyNameReference name, ReaderParameters parameters)
   at Mono.Cecil.DefaultAssemblyResolver.Resolve(AssemblyNameReference name)
   at Mono.Cecil.MetadataResolver.Resolve(TypeReference type)
   at Mono.Cecil.TypeReference.Resolve()
   at Mono.Cecil.Mixin.CheckedResolve(TypeReference self)
   at Mono.Cecil.MetadataBuilder.GetConstantType(TypeReference constant_type, Object constant)
   at Mono.Cecil.MetadataBuilder.AddConstant(IConstantProvider owner, TypeReference type)
   at Mono.Cecil.MetadataBuilder.AddParameter(UInt16 sequence, ParameterDefinition parameter, ParamTable table)
   at Mono.Cecil.MetadataBuilder.AddParameters(MethodDefinition method)
   at Mono.Cecil.MetadataBuilder.AddMethod(MethodDefinition method)
   at Mono.Cecil.MetadataBuilder.AddMethods(TypeDefinition type)
   at Mono.Cecil.MetadataBuilder.AddType(TypeDefinition type)
   at Mono.Cecil.MetadataBuilder.AddTypeDefs()
   at Mono.Cecil.MetadataBuilder.BuildTypes()
   at Mono.Cecil.MetadataBuilder.BuildModule()
   at Mono.Cecil.ModuleWriter.<BuildMetadata>b__0(MetadataBuilder builder, MetadataReader _)
   at Mono.Cecil.ModuleDefinition.Read[TItem,TRet](TItem item, Func`3 read)
   at Mono.Cecil.ModuleWriter.BuildMetadata(ModuleDefinition module, MetadataBuilder metadata)
   at Mono.Cecil.ModuleWriter.WriteModuleTo(ModuleDefinition module, Stream stream, WriterParameters parameters)
   at Mono.Cecil.ModuleDefinition.Write(Stream stream, WriterParameters parameters)
   at Mono.Cecil.ModuleDefinition.Write(String fileName, WriterParameters parameters)
   at Xamarin.MonoTouch.Build.Tasks.MangleLibraryResources.EmbedResourcesOnAssembly(String assemblyPath, ITaskItem[] resources, String projectDir, String[] prefixes)
   at Xamarin.MonoTouch.Build.Tasks.MangleLibraryResources.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()	Sphere10.Framework.iOS

Don't ask me to tell you what "version" since it's impossible to find out now in Windows since Xamarin Studio no longer lists Xamarin iOS details there. So figure out the version i'm using by figuring out what your latest stable version is as of Jan 8 2014 - which is what i'm using.

Please note customers are not a good QA team. You're no longer open-source company and if you're going to price a product at a 1000 a pop, you might want to act like a commercial software vendor and test this shit properly. If setbacks and bugs continue, I Will not be recommending Xamarin anymore to clients and will look at alternative solutions.
Comment 1 Marek Habersack 2014-01-08 04:08:49 UTC
Hello Herman,

Your report suggests you're using Xamarin Studio on Windows - if that assumption is correct, then please note that Xamarin Studio for Windows does not support Xamarin.iOS development. You must use Visual Studio Professional (2010 or newer) for this.

Please clarify whether you used Xamarin Studio or Visual Studio when you ran into the above error, thanks!
Comment 2 dean.ellis 2014-01-08 12:36:45 UTC
Hi Herman

I have tested OpenTK and OpenTK-1 on the latest Xamarin.iOS for VS (which I assume you are using) and I and not seeing the same error you are. Are you able to upload a sample project which demonstrates the issue?
Comment 3 Herman 2014-01-08 18:19:59 UTC
It turns out that opentk has nothing to do with it.

The issue can be replicated as follows
-install latest stable release for osx
-install latest stable release for windows
- syncronize assemblies via build host
- observe that no xamarin iOS project builds

The solution for me was to upgrade osx to latest alpha release and sync assemblies again, and it's fine.
Comment 4 Enzo Heredia 2015-07-01 14:02:48 UTC
not reproducible. build
Comment 5 Jose Gallardo 2016-12-22 17:35:15 UTC
Marking as resolved not_reproducible.
Please feel free to reopen the issue if you can still reproduce it with current bits.