Bug 11807 - path to 3.0.8 vbnc in MDK 3.0.9
Summary: path to 3.0.8 vbnc in MDK 3.0.9
Status: RESOLVED FIXED
Alias: None
Product: MonoMac
Classification: Desktop
Component: Bindings ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Duncan Mak
URL:
: 11854 ()
Depends on:
Blocks:
 
Reported: 2013-04-16 13:16 UTC by D2k
Modified: 2013-05-14 12:32 UTC (History)
3 users (show)

Tags:
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 or GitHub 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:
Status:
RESOLVED FIXED

Description D2k 2013-04-16 13:16:39 UTC
Using MDK 3.0.9 in Xamarin I received this error on attempting to compile

Error open assembly '/Library/Frameworks/Mono.framework/Versions/3.0.8/lib/mono/4.0/vbnc.exe': No such file or directory. (open assembly '/Library/Frameworks/Mono.framework/Versions/3.0.8/lib/mono/4.0/vbnc.exe') (Hello)
Comment 1 Rolf Bjarne Kvinge [MSFT] 2013-04-22 18:32:16 UTC
Duncan, any idea what might have caused this?
Comment 2 Duncan Mak 2013-04-23 13:46:23 UTC
Yeah, please upgraded to 3.0.10.

There were some packaging bugs in 3.0.8 / 3.0.9 that got introduced because we tried to speed up the build by caching the build artifacts. It ended up packaging the wrong files.

it's been fixed in 3.0.10.
Comment 3 Rolf Bjarne Kvinge [MSFT] 2013-05-14 12:32:49 UTC
*** Bug 11854 has been marked as a duplicate of this bug. ***