GitXplorerGitXplorer
l

monodevelop-windows

public
47 stars
10 forks
1 issues

Commits

List of commits on branch master.
Verified
9ae38ee17641626cf3d7e0a086927f1461b4bfe8

Update README.md

llextm committed 5 years ago
Unverified
cbb16713d3fa0a2b78ba40af898be55b397ab1e7

Bumped to latest.

llextm committed 6 years ago
Verified
7ccf007880740de085d3c52758369de2d214191a

Fixed badge style.

llextm committed 6 years ago
Verified
03571cd375ba2d592f3a3ad4d8495a7f9d9355c5

Added download link.

llextm committed 6 years ago
Unverified
308b9a312e43bfabfb6b48f83a5145b482aff26b

Fixed the badges.

llextm committed 6 years ago
Unverified
bb32750fed29ef28d0b74da2dd7941d702999728

Fixed Linux version.

llextm committed 6 years ago

README

The README file for this repository.

Test repo to build MonoDevelop on Windows

Windows/Mac Linux
Build status Build status Downloads Build status

Tha artifacts (portable ZIP package, and Windows MSI installer) matching MonoDevelop 7.8 release.

Downloads

Latest builds/installers can be downloaded from

https://github.com/lextm/monodevelop-windows/releases

MonoDevelop 7.x has hard dependency on GTK# and MSBuild 15, so please install GTK# for .NET and Visual Studio 2017 Build Tools (or simply any Visual Studio 2017 edition) before running it.

MonoDevelop 8.x is still in active development and unstable, so there is no plan to ship artifacts for them yet.

Troubleshooting Guide

You might try the steps to see what else we can dig out,

  1. Open a MonoDevelop instance (like C:\Program Files (x86)\MonoDevelop\bin\MonoDevelop.exe).
  2. Instead of creating/opening a project, click Run | Debug Application... menu item.
  3. Set Command to C:\Program Files (x86)\MonoDevelop\bin\MonoDevelop.exe.
  4. Set Working Directory to C:\Program Files (x86)\MonoDevelop\bin.
  5. Click OK.
  6. Wait till the second instance of MonoDevelop launches, switch back to the first instance and click View | Pads | Application Output - MonoDevelop.exe to reveal the tracing.
  7. Switch back to the second instance, and reproduce the issue.

Now the tracing should show what errors happened. From that we can see how the installer can be improved.