[MonoDevelop] MonoDevelop on Win32

[Daniel Morgan]

Thanks.

Based on the feedback from you Tak, Alp, latexer, cj, and others, I have 
been able to build and run MonoDevelop on Windows now.

Yeah, disabling the WelcomePage and GtkCore add-ins allows MonoDevelop 
to run. I think this is key.
I also had to find all the .config files and make sure they map to my 
Windows *.dlls instead of the Linux *.so files.
I can create new projects now and new files, but I can not build 
projects. It says specified file not found. Go figure. It created the 
files on the hard drive though.

When building, making sure I had intltool and gettext installed.

I made sure the place to gtkmozembed binaries was in my PATH.

And I used this graphical program to disable those add-ins.
mono mdrun.exe gsetup

Here is part of my output. Notice it has a
System.IO.IOException: Win32 IO returned ERROR_INVALID_NAME. Path: 
G:/G:\cygwin
\home\Administrator\Projects\TestProject2\TestProject2

Administrator at danpc ~/monosvn/monodevelop/build/bin
$ mono --debug MonoDevelop.exe --ipc-tcp

(MonoDevelop:2456): Pango-WARNING **: couldn't load font "fixed 8", 
falling back
to "Sans 8", expect ugly output.
2358 [5676] INFO MonoDevelop.Core.ILoggingService (null) - Initializing 
service:
MonoDevelop.Core.FileUtilityService
2436 [5676] INFO MonoDevelop.Core.ILoggingService (null) - Initializing 
service:
MonoDevelop.Core.PropertyService
3467 [5676] INFO MonoDevelop.Core.ILoggingService (null) - Loaded 
add-in: MonoDe
velop.Core
3655 [5676] INFO MonoDevelop.Core.ILoggingService (null) - Loaded 
add-in: MonoDe
velop.Projects
3671 [5676] INFO MonoDevelop.Core.ILoggingService (null) - Loaded 
add-in: MonoDe
velop.Documentation
3749 [5676] INFO MonoDevelop.Core.ILoggingService (null) - Initializing 
service:
MonoDevelop.Core.SystemAssemblyService
3764 [5676] INFO MonoDevelop.Core.ILoggingService (null) - Initializing 
service:
MonoDevelop.Core.Execution.ProcessService
6827 [5676] DEBUG MonoDevelop.Core.ILoggingService (null) - Reading 
G:\cygwin\ho
me\Administrator\.config\MonoDevelop\CodeCompletionData\mscorlib_2.0.0.0_b77a5c5
61934e089.pidb
8717 [5676] INFO MonoDevelop.Core.ILoggingService (null) - Initializing 
service:
MonoDevelop.Projects.Documentation.IDocumentationService
36905 [5676] DEBUG MonoDevelop.Core.ILoggingService (null) - Writing 
G:\cygwin\h
ome\Administrator\.config\MonoDevelop\CodeCompletionData\mscorlib_1.0.5000.0_b77
a5c561934e089.pidb
2006-06-27 22:27:35,562 [4124] ERROR MonoDevelop.Core.ILoggingService 
[(null)] -
System.IO.IOException: Win32 IO returned ERROR_INVALID_NAME. Path: 
G:/G:\cygwin
\home\Administrator\Projects\TestProject2\TestProject2
in [0x00028] (at 
K:\msys\1.0\download\mono-1.1.13\mcs\class\corlib\System.IO\Dir
ectory.cs:181) System.IO.Directory:Exists (System.String path)
in [0x00147] (at 
K:\msys\1.0\download\mono-1.1.13\mcs\class\corlib\System.IO\Fil
eStream.cs:185) System.IO.FileStream:.ctor (System.String name, FileMode 
mode, F
ileAccess access, FileShare share, Int32 bufferSize, Boolean isAsync, 
Boolean an
onymous)
in [0x0000d] (at 
K:\msys\1.0\download\mono-1.1.13\mcs\class\corlib\System.IO\Fil
eStream.cs:123) System.IO.FileStream:.ctor (System.String name, FileMode 
mode, F
ileAccess access, FileShare share)
in (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor 
(string,Syste
m.IO.FileMode,System.IO.FileAccess,System.IO.FileShare)
in [0x00004] (at 
K:\msys\1.0\download\mono-1.1.13\mcs\class\corlib\System.IO\Fil
e.cs:317) System.IO.File:OpenRead (System.String path)
in [0x000c8] (at 
K:\msys\1.0\download\mono-1.1.13\mcs\class\corlib\System.IO\Str
eamReader.cs:171) System.IO.StreamReader:.ctor (System.String path, 
System.Text.
Encoding encoding, Boolean detect_encoding_from_bytemarks, Int32 
buffer_size)
in [0x0000d] (at 
K:\msys\1.0\download\mono-1.1.13\mcs\class\corlib\System.IO\Str
eamReader.cs:140) System.IO.StreamReader:.ctor (System.String path)
in (wrapper remoting-invoke-with-check) System.IO.StreamReader:.ctor 
(string)
in [0x00001] (at 
K:\msys\1.0\download\mono-1.1.13\mcs\class\corlib\System.IO\Fil
e.cs:322) System.IO.File:OpenText (System.String path)
in [0x0000d] (at 
G:\cygwin\home\Administrator\monosvn\monodevelop\Core\src\MonoD
evelop.Projects\MonoDevelop.Projects\Project.cs:167) 
MonoDevelop.Projects.Projec
t:GetParseableFileContent (System.String fileName)
in [0x000a0] (at 
G:\cygwin\home\Administrator\monosvn\monodevelop\Core\src\MonoD
evelop.Projects\MonoDevelop.Projects.Parser\DefaultParserService.cs:1445) 
MonoDe
velop.Projects.Parser.ParserDatabase:DoParseFile (System.String 
fileName, System
.String fileContent)
in [0x00026] (at 
G:\cygwin\home\Administrator\monosvn\monodevelop\Core\src\MonoD
evelop.Projects\MonoDevelop.Projects.Parser\ProjectCodeCompletionDatabase.cs:219
) MonoDevelop.Projects.Parser.ProjectCodeCompletionDatabase:ParseFile 
(System.St

This is all I can remember for now. So, if I have any other tid-bits, I 
will post them.

Levi Bard wrote:
>> I am trying to build MonoDevelop on Windows.  I am having difficulting.
>>
>> If anyone has gotten it to build and run, can you please email this list
>> explaining what you did to get it to work?  I so much want it to run on
>> Windows.
>>
>> I do know Zac Bowling over a year ago got it to work, but it was
>> un-deployable.  Paco got it to work, but he didn't get past the Splash
>> screen.   I heard someone named Tak got it to load up stetic and such.
>>
>> For me,  I have got it to build, but my mono, gtk#, and cygwin environment
>> is like a big junk yard.  It's not something reproducible nor nothing you
>> would want to deploy.  I did get it to run with the splash screen popping,
>> but it eventually fails.
>>
>> I did notice it still uses unix domain sockets even though there is a
>> --ipc-tcp option when running MonoDevelop.  Once you change that to a TCP
>> InterNetwork socket, it runs the splash screen.
>>
>> The UNMANAGED_DEPENDENCIES_MONO I had earlier was because pkg-config could
>> not find my mono.pc file.  This was resolved by setting PKG_CONFIG_PATH to
>> point where my .pc files are located.  For me this was:
>>
>> export
>> PKG_CONFIG_PATH=/cygdrive/g/MonoX-1.1.13.1/lib/pkgconfig
>>
>> I was able to verify this would work by:
>>
>> pkg-config --cflags --libs mono
>>     
>
> I've gotten it to build, and barely run on win32.  It's not anywhere
> near stable or useful yet, let alone deployable.  It will load through
> the splash screen, to the main window, allow me to create new projects
> and open existing ones (although not edit source or build yet), and
> browse the monodocs.  So far, I can not use Stetic, nor the Welcome
> Page addin.
>
> I started where you did, with paco's installers for mono/gtk# and
> gecko#, as well as the shellter build of evolution-win32.  I built MD
> from anonymous svn rev 62063.
>
> I have:
> GECKOSHILLA_BASEPATH=C:\Program Files\Common Files\gtkmozembed-win32
> LD_LIBRARY_PATH=/cygdrive/c/Program
> Files/Evolution/bin:/cygdrive/c/mono/MonoX-1.1.13.1/bin:/cygdrive/c/GTK/2.8/bin
> PKG_CONFIG_PATH=c:\gtkstuff\lib\pkgconfig:c:\mono\MonoX-1.1.13.1\lib\pkgconfig
>
> I temporarily disabled the code in
> Core/src/MonoDevelop.Ide/MonoDevelop.Ide.Gui/IdeStartup.cs that checks
> for/reconnects to existing instances (UNIX sockets), temporarily
> removed the Stetic (MonoDevelop.GtkCore) and WelcomePage addins (from
> build/AddIns), and ran with --ipc-tcp.
>
> I hope some of this is helpful.
>
>