GitXplorerGitXplorer
l

monodevelop-windows

public
47 stars
10 forks
1 issues

Commits

List of commits on branch master.
Unverified
574b5148766684eb5b2e35a561bf4369d720ec86

Moved Linux to Travis CI.

llextm committed 6 years ago
Unverified
7f7455dcc4f09579298889bae0b8dab2977c7bdf

Bumped Linux.

llextm committed 6 years ago
Unverified
fb10e378acdf6bb9553e7a4e8eae95168daaac47

Bumped Mac.

llextm committed 6 years ago
Unverified
5196a6883bcd342259ccbff90c3cd07b16deaf43

Bumped Mac and Linux.

llextm committed 6 years ago
Unverified
b21b80750e5e7cd2725aa4a7c0f566b568757c50

Revised Linux deps.

llextm committed 6 years ago
Unverified
d768353a7127df708518d3eab3c86a448ee2ebb9

Bumped Mac image.

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.