Cannot open assembly '/usr/lib/mono/1.0/mcs.exe'

[Medar]

Binary package hint: mono-devel

$ mcs
The program 'mcs' is currently not installed. You can install it by typing:
sudo apt-get install mono-devel
bash: mcs: command not found

$ sudo apt-get install mono-devel
...

$ mcs
Cannot open assembly '/usr/lib/mono/1.0/mcs.exe': No such file or directory.

Fixed by installing mono-mcs package, guess there should depends.

[Jo Shields (directhex)]

This is a known issue in Jaunty, it will be fixed for Karmic

[Jo Shields (directhex)]

This is a known issue in Jaunty, it will be fixed for Karmic. Please note that CLI 1.0 is deprecated in Jaunty - all libs are built against 2.0, and you should use gmcs wherever possible (existing 1.0 apps can be run as 2.0 using mono --runtime=v2.0.50727 program.exe)

[Jo Shields (directhex)]

Confusion regarding the mcs symlink now resolved in Karmic

[Darryl Allardice (duderdice)]

I'm running Karmic and just apt-get upgraded everything available, and --reinstalled the "mono-devel" package and I am getting this error when trying to execute 'mcs' on the command line:

  ~$ mcs
  The program 'mcs' is currently not installed. You can install it by typing:
  sudo apt-get install mono-devel
  bash: mcs: command not found

Previously, it just told me that [Cannot open assembly '/usr/lib/mono/1.0/mcs.exe': No such file or directory.] when the 'mcs' script was exec'ing the mcs.exe file which did not exist. Now it looks like its completely gone now and does not get recreated when installing "mono-devel". Doesn't appear to be fixed correctly.... or am I missing something???

[Darryl Allardice (duderdice)]

Ok, i read the topmost notice more closely and after running 'apt-get install mono-mcs' it is fixed -- "mcs" now executes correctly at the command line. Perhaps that depends would be nice :-)