Re: [Mono-list] Cross-Platform GUI Tookit
Xamarin Studio / MonoDevelop is not really going to use MVVM, it will use MVC. El 18/11/2014, a les 21:33, Daniel Hughes tramps...@gmail.com va escriure: Jonathan can you comment on Xamarins plans for MVVM with Xamarin Studio/MonoDevelop, can we expect GTK# support to be added to MVVMCross, or is there some other approach you will be taking. Cheers, Daniel Hughes On Wed, Nov 19, 2014 at 4:46 AM, Jonathan Pryor jonpr...@vt.edu wrote: On Nov 17, 2014, at 10:55 PM, Edward Ned Harvey (mono) edward.harvey.m...@clevertrove.com wrote: The fact that XS/MD is or was based on Xwt is a good sign based on might be a bit strong. It *uses* Xwt. Most of the current Xamarin Studio/MonoDevelop code is based on Gtk#. *Parts* were done in Xwt so that those parts could use the platform-native UI and share code with Visual Studio (e.g. File Open, the Android designer), but most was written in, and continues to be in, Gtk#. - Jon ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] monodevelop perforce addin work
The ids of the CommandItem elements must match the ids of the commands. Also, make sure you define an enum value for each command. See http://monodevelop.com/Developers/Articles/The_Command_System. El 02/07/2013, a las 10:07, Ian Norton inor...@gmail.com escribió: Hiya, I'm trying to add some command extensions for my p4 addin for monodevelop, I've got a bit lost. https://github.com/inorton/XR.Mono.Perforce/blob/master/XR.MonoDevelop.Perforce/XR.MonoDevelop.Perforce.addin.xml The xml results in unknown command menu items rather than Edit file.. or Submit changes.. as I wanted. Any help would be greatly appreciated. Ian ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 2.6 Beta 3 released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.6 Beta 3 (2.5.92). This is the third release of a series of releases that will lead to MonoDevelop 2.6. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. MonoDevelop enables developers to quickly write desktop and ASP.NET Web applications on Linux, Windows and Mac OSX. MonoDevelop makes it easy for developers to port .NET applications created with Visual Studio to Linux and to maintain a single code base for all platforms. This release contains lots of bug fixes. Check the release notes to know more about the changes: http://monodevelop.com/Download/Release_Notes/Release_Notes_for_MonoDevelop_2.6_Beta_3 A more complete description of what's new in MonoDevelop 2.6 is available here: http://monodevelop.com/Download/What%27s_new_in_MonoDevelop_2.6 Sources and packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 2.6 Beta 2 released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.6 Beta 2. This is the second release of a series of releases that will lead to MonoDevelop 2.6. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. MonoDevelop enables developers to quickly write desktop and ASP.NET Web applications on Linux, Windows and Mac OSX. MonoDevelop makes it easy for developers to port .NET applications created with Visual Studio to Linux and to maintain a single code base for all platforms. This release contains lots of new features and improvements. Here is a summary of the new features: * Version Control * Added option for creating a Git repository when creating a new solution * New commands for creating, applying and managing Git stashes * Greatly improved Git log performance * Support for search in log view * Allow overriding the author when committing * Added rebase command * Added support for local repositories * Added wrapping option to the commit message style settings * Project Model * Added commands for importing/exporting policies * Support for external display bindings * Improved compatibility with Visual Studio file formats * Source Editing * Improved performance of the text editor * Improved on-the-fly formatting * Debugger * Improved handling of breakpoints. Breakpoints in invalid locations are not better detected. * Tools * The export-project tool now allows specifying which projects of a solution should be exported. * Mac OSX * The gettext add-in is now supported in Mac * Added support for creating Mac bundles using `mdtool`. * C / C++ * Basic support for the Go-to-declaration command A more complete description of what's new in MonoDevelop 2.6 is available here: http://monodevelop.com/Download/What%27s_new_in_MonoDevelop_2.6 Release notes: http://monodevelop.com/Download/Release_Notes/Release_Notes_for_MonoDevelop_2.6_Beta_2 Sources and packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] GSOC for Interactivre C#/F#/IronPython Console
Hi, Please send your proposal through the official GSoc portal: http://www.google-melange.com/gsoc/homepage/google/gsoc2011 Details of the proposal will be discussed in that portal after it's posted. Thanks! El dc 06 de 04 de 2011 a les 04:05 +0300, en/na Tayfur Yilmaz va escriure: Hi Everyone ı send my aproach for my app Firstly ı write some code for console app for Pardus Project and ı'm experinenced for talking backed application with new app so ı hava some idea for this project and write my proposal this idea. Example for Shell usage my aproach algoritmic analyze with coding Python (it's only example) Firstly for support a lot of language usage in Mono we need same layer and we define it so when we add different language usage for shell in project we have standart class and functions Example base.py class getAssembly(self): def __init__(self): pass def xxx(self): pass def yyy(self): pass class getCultureVersion(self): def __init__(self): pass def xxx(self): pass def yyy(self): pass class EnvironmentPath(self): def __init__(self): pass def xxx(self): pass def yyy(self): pass class ShellScreen(self): def __init__(self): pass def xxx(self): pass def yyy(self): pass IronPython.py,CSharp.py,FSharp.py #some spesific functions #some implementaions #some fields class getAssembly(base.getAssembly): # for IronPython code def __init__(self): pass @override def xxx(self): pass @override def yyy(self): pass class ShellScreen(base.ShellScreen) # for shell graphic designer and you integrated and decorated for IronPython def __init__(self): pass @override def xxx(self): pass @override def yyy(self): pass and so so so. And I solve some problem this approach when calling different attribute program do not make a bug for generally system and ıt's plugin based development and ı want to write some test(TDD) So my second aproach for C#/F#/IronPython ı think some usefeul scripts present to developer example I sometime write Django app ı use django-command-extensions it's very useful for developer with some scripts Example we management commands, additional database field And I think it's a plugin for shell and we add this app plugin repository so when developers need this app people install it.(Mono Plugin Repository) I write some examples code and uml diagram for this project I wii send it with my proposal and Any mentors discuss this approach with me and say some suggestions for me ? Thanks alot Best Regards ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-list] MonoDevelop 2.6 Beta 1 released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.6 Beta 1. This is the first release of a series of releases that will lead to MonoDevelop 2.6. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. MonoDevelop enables developers to quickly write desktop and ASP.NET Web applications on Linux, Windows and Mac OSX. MonoDevelop makes it easy for developers to port .NET applications created with Visual Studio to Linux and to maintain a single code base for all platforms. This release contains lots of new features and improvements. Here is a summary of the new features: * Version Control * Support for GIT * Improved version control views * New conflict resolution window * Project Model * User defined policies * Improved support for xbuild/MSBuild * Support for .NET 4.0 * New Add Folder to Project command * Source Editing * MCS based parser and formatting engine * New C# formatting options dialog * New path bar * VI mode improvements * DocFood add-in * Improved XML editing experience * Debugger * IL disassembly view * Catchpoints and conditional breakpoints in the Win32 debugger * Improved support for debugging anonymous methods and iterators * New Stop Evaluation command * Tools * Improved T4 Templating Engine * Mac OSX * Native file dialogs * C / C++ * Improved symbol navigation and completion using ctags. * Limited navigation and completion support for the default OSX ctags * Rudimentary project support for Objective C has been added. * Add-in management * New add-in manager window A more complete description of what's new in MonoDevelop 2.6 is available here: http://monodevelop.com/Download/What%27s_new_in_MonoDevelop_2.6 Release notes: http://monodevelop.com/Download/Release_Notes/Release_Notes_for_MonoDevelop_2.6_Beta_1 Sources and packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Mono.Addins 0.6 released
Hi, I'm pleased to announce the release of Mono.Addins 0.6. Mono.Addins is a generic framework for creating extensible applications, and for creating libraries which extend applications. The 0.6 release of Mono.Addins includes many improvements, bug fixes and new features: * Add-in engine * Add-in name and description can now be localized. There are new custom attributes for defining them, and can also be specified as xml elements in an add-in manifest instead of attributes. * Support for custom add-in properties. It is now possible to specify arbitrary properties in add-ins, which can be queried at install time (using the Mono.Addins.Setup API) or at run-time. * Custom extension attributes now allow specifying an extension path. In this way it is now possible to use a single custom attribute to define extensions for different extension points. * The default add-in directory and the add-in database directory can now be customized. In previous releases, those directories were always created as a subdirectory of the main registry directory. In this release, the location can be set to any directory. * Improved error reporting when a dependency is missing. * Added support for specifying the type of the content of string node attributes. This information is used for documentation purposes only. * The Cecil based reflector now uses the new Cecil/Light, which is smaller and faster * Add-in management * Added support for enabling/disabling registered repositories. * Added support for downloable support files, to be used for package icons, screenshots, etc. * New and improved add-in manager for GTK#. The user interface has been completely redesigned to make it more usable. Add-in updates are more visible and easy to install. The add-in gallery is integrated in the main window, and can show custom add-in icons and preview images. * Added new API for accessing custom add-in properties, even before installing them. * Included information about download size. * Bug fixes: * Allow overwriting files when installing. * Fixed add-in unloading issues. * Fixed crash when running in .NET 4.0 * AddinRepository.LastModified is always 01.01.1900 00:00:00 * Addin registry access/creation errors when accessed via UNC path * Addin discovery/loading fails when running Visual Studio unit tests * ImportAddinAssemblyAttribute can't be used multiple times * Fix bug in GetAvailableAddin. * Fix add-in database issue when the last add-in of a folder is deleted or upgraded * Don't allow inheriting CustomExtension attributes. The attribute must be explicitly applied to classes to be marked as extensions. If you are interested in knowing more about Mono.Addins, take a look at http://monoaddins.codeplex.com/documentation. You can download the source code from: http://monoaddins.codeplex.com/releases/view/61370 and from GitHub: https://github.com/mono/mono-addins/tree/mono-addins-0.6 Enjoy! Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 2.4.2 released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.4.2. This is a release based on the 2.4 stable branch, and includes several bug fixes and some feature improvements. Release notes: http://monodevelop.com/Download/MonoDevelop_2.4.2_Released Sources and packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Debugger crashes while debugging ASP.NET app
El dj 13 de 01 de 2011 a les 13:21 -0800, en/na passiday va escriure: Hello, I'm experiencing this weird debugger crashing. Spent now about 4 hours trying to work it out, and no luck. I'm really betting on this mailing list... So, this problem is there since I have installed MonoDevelop on my Ubuntu 10.10 64bit. I am trying to debug ASP.NET application - setting breakpoints, checking watches, stepping through the code line by line. So, I can successfully build my app, and run it in debug mode, it hits the first breakpoint, I can check the watches. Bud when I hit the Step over, the app immediately crashes. No info is dumped in Application Output pad. Funny thing is that very rarely it doesn't crash and lets me step over several lines, until the next breakpoint is hit and then crashes again, when trying to step further. Very annoying. Basically I am limited to one breakpoint for debugging, or to use awkward tools like dumping the debug variables to file or database. Does somebody have any clue, what's going on here? I know I am giving very little information on this crash. Maybe you can suggest how I can extract more information to supply to the case. Try running MonoDevelop from a terminal, and see which output you get. Also make sure you have the latest MonoDevelop and Mono. Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] http://go-mono.com/md/ - monodevelop repository site dead
This url is not used anymore. MonoDevelop automatically registers the correct add-in repository, so you don't have to do it manually. Lluis. El dc 13 de 10 de 2010 a les 14:11 +0200, en/na Tomasz Kubacki va escriure: after visiting: http://go-mono.com/md/ i get: Access forbidden! You don't have permission to access the requested directory. There is either no index document or the directory is read-protected. If you think this is a server error, please contact the webmaster. Error 403 go-mono.com Wed Oct 13 08:09:15 2010 Apache ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 2.4 released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.4. MonoDevelop is an IDE primarily designed for C# and other .NET languages. MonoDevelop enables developers to quickly write desktop and ASP.NET Web applications on Linux, Windows and Mac OSX. MonoDevelop makes it easy for developers to port .NET applications created with Visual Studio to Linux and Mac OS maintaining a single code base for all platforms. The official announcement is available here: http://www.monodevelop.com/Download/MonoDevelop_2.4_Released A detailed description of the features included in this release is available here: http://monodevelop.com/Download/What%27s_new_in_MonoDevelop_2.4 Many thanks to everybody that made possible this release. Enjoy! The MonoDevelop Team. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Licencing.
El dc 09 de 06 de 2010 a les 14:17 +0530, en/na Akshar Patel va escriure: I need to know if I use mono and make open source but non-free applications in Linux, do I have to purchase a commercial license? No. See http://mono-project.com/FAQ:_Licensing. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 2.4 Beta 2 released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.4 Beta 2 (2.3.1). This is the second release of a series of releases that will lead to MonoDevelop 2.4. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. MonoDevelop enables developers to quickly write desktop and ASP.NET Web applications on Linux, Windows and Mac OSX. MonoDevelop makes it easy for developers to port .NET applications created with Visual Studio to Linux and to maintain a single code base for all platforms. This release contains lots of bug fixes. Check the release notes to know more about the changes: http://monodevelop.com/Download/Release_Notes/Release_Notes_for_MonoDevelop_2.4_Beta_2 A more complete description of what's new in MonoDevelop 2.4 is available here: http://monodevelop.com/Download/What%27s_new_in_MonoDevelop_2.4 Sources and packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Mono.Addins 0.5 released
Hi, I'm pleased to announce the release of Mono.Addins 0.5. Mono.Addins is a generic framework for creating extensible applications, and for creating libraries which extend applications. The 0.5 release of Mono.Addins comes packed with new features, including: * User defined custom attributes can now be used to declare extensions and add-in metadata. * The new AddinEngine class allows hosting several independent add-in engines in a single application domain. * Improved lazy loading of add-ins. More information is now lazy loaded. * An XML manifest can now be split in several files embedded as resources in an assembly. * More add-in information can be declared using custom attributes instead of an XML manifest: author list, imported files and assemblies, optional modules, localizers. * Added new API based on generic methods and collections. * New MSBuild tasks file and target, which allows using add-in references directly in a build file (still experimental). * Reorganized the samples directory. * New and improved documentation. * Many bug fixes. Another important change is that Mono.Addins is now hosted in CodePlex: http://monoaddins.codeplex.com If you are interested in knowing more about Mono.Addins, take a look at http://monoaddins.codeplex.com/documentation. The new Programming Guide document shows some of the new features of this release. You can download the source code from: http://monoaddins.codeplex.com/releases/view/45628 Enjoy! Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] MonoDevelop 2.4 Beta 1 released
El dj 06 de 05 de 2010 a les 18:06 -0700, en/na Mike Christensen va escriure: This is awesome, I just installed this on my Mac and looks very good. No glaring bugs or anything. I have a few questions about the Immediate window. It seems to be read-only. First off, I cannot declare a new variable: string s = Hello; EOF expected The syntax is: var s = hello although that is also broken in this beta release. I just fixed it. Second, if I change an existing variable in the local scope, it apparently ignores me: y 18 y++; y 18 Fixed. Third, I cannot call methods on local variables: y.ToString() Evaluation failed. Calling methods on primitive values is not currently supported. Other local variables should work. (Note there's also no Autocomplete within the Immediate window which would be a nice to have as well).. Maybe in MD 2.6 ;) When I'm debugging, I use the Immediate window quite a bit to mock up code before I change my program, and some polishing up on the MonoDevelop immediate window would go a long way. The more this could be like Visual Studio, the better. (I'm sure you guys hear that one a lot). Any chance of fixing some of these issues before the final bits? Thanks!! If you find other bugs, please file them through http://monodevelop.com/Bugs. Thanks! Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] MonoDevelop 2.4 Beta 1 released
El dj 06 de 05 de 2010 a les 21:16 -0400, en/na Christopher David Howie va escriure: On 05/06/2010 09:06 PM, Mike Christensen wrote: When I'm debugging, I use the Immediate window quite a bit to mock up code before I change my program, and some polishing up on the MonoDevelop immediate window would go a long way. The more this could be like Visual Studio, the better. (I'm sure you guys hear that one a lot). Any chance of fixing some of these issues before the final bits? Thanks!! Hopefully even support lambdas and loops, neither of which the VS immediate window supports, but that Mono's interactive csharp compiler has supported for a long time... The immediate window is just an expression evaluator, no code generation is involved. I might be able to hack support for loops, but there is no way we can support lambdas. To fully support the interactive csharp compiler, it would have to be loaded in the debugged process, but that would be very intrusive and would do more harm than good. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 2.4 Beta 1 released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.4 Beta 1 (2.3). This is the first release of a series of releases that will lead to MonoDevelop 2.4, hopefully around the end of May. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. MonoDevelop enables developers to quickly write desktop and ASP.NET Web applications on Linux, Windows and Mac OSX. MonoDevelop makes it easy for developers to port .NET applications created with Visual Studio to Linux and to maintain a single code base for all platforms. This release contains lots of new features and improvements. Here is a summary of the new features: * Workbench Usability * Improved look * Improved pad organization * Improved Error Workflow with In-line Error Bubbles * New Project/File dialogs * New Navigate To dialog * Solution and Class pad Zooming * New Options for selecting the user interface language, output pad font and GTK+ theme. * Project Model * Standalone Assembly Projects * External Console Support for Mac and Windows * Support for adding files to solution folders * Proper MSBuild file links in projects * Source Editing * Improved in-line search * Group Mode in Code Completion * Symbol Usage Highlighting * Editing Support in Block Selection Mode * Import Type Command * Code Focus Toggle and Follow-cursor * Quick Fix Command * Scrollable Region Tooltips * Improved Filtering in Completion List * Debugger * Pinned Quick Watches * Debug Value Visualizers * Improved expression evaluation * New Exception Dialog * Tools * New Hex Editor * Integrated T4 Templating * More Code Metrics * ASP.NET * Code completion for C# regions * Web References * Support for WCF Web References * Support for references that require authentication * Improvements in other add-ins: * NUnit * MonoTouch * Mac OS support * Vala A more complete description of what's new in MonoDevelop 2.4 is available here: http://monodevelop.com/Download/What%27s_new_in_MonoDevelop_2.4 Release notes: http://monodevelop.com/Download/Release_Notes/Release_Notes_for_MonoDevelop_2.4_Beta_1 Sources and packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] [MonoDevelop] RPM builder addin - GSOC idea
El dc 24 de 03 de 2010 a les 06:44 +, en/na saf...@gmail.com va escriure: Hi, We have packaging projects in Monodevelop, which let you build source and binary packge. The binary package is in the zip format or we can say portable format not in the installer format. We can have addin which let you create an RPM file that can be used to install on other machines. I don't know how work it need, can put this idea for GSOC? This is a nice to have feature, but I don't think there is enough work for a whole GSOC project. Also, there is also the idea of writing a fronted for the openSUSE build service, which would provide RPM generation and package generation for other distros. We can extend it to make .msi package for windows. Exisitng SharpDevelop code help here. Yes, that would be nice. --- Sharique ___ Monodevelop-list mailing list monodevelop-l...@lists.ximian.com http://lists.ximian.com/mailman/listinfo/monodevelop-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 2.2.2 Released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.2.2. This is a release based on the 2.2 stable branch, and includes many bug fixes and some feature improvements. Release notes: http://monodevelop.com/Download/MonoDevelop_2.2.2_Released Sources and packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 2.2.1 Released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.2.1. This is a release based on the 2.2 stable branch, and includes many bug fixes and some feature improvements. Release notes: http://monodevelop.com/Download/MonoDevelop_2.2.1_Released Sources and packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 2.2 released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.2. MonoDevelop is an IDE primarily designed for C# and other .NET languages. MonoDevelop enables developers to quickly write desktop and ASP.NET Web applications on Linux, Windows and Mac OSX. MonoDevelop makes it easy for developers to port .NET applications created with Visual Studio to Linux and Mac OS maintaining a single code base for all platforms. The official announcement is available here: http://www.monodevelop.com/Download/MonoDevelop_2.2_Released A detailed description of the features included in this release is available here: http://monodevelop.com/Download/What%27s_new_in_MonoDevelop_2.2 Many thanks to everybody that made possible this release. Enjoy! The MonoDevelop Team. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 2.2 RC released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.2 RC (2.1.2). This is the third release of a series of releases that will lead to MonoDevelop 2.2. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. MonoDevelop enables developers to quickly write desktop and ASP.NET Web applications on Linux, Windows and Mac OSX. MonoDevelop makes it easy for developers to port .NET applications created with Visual Studio to Linux and to maintain a single code base for all platforms. This release includes plenty of bug fixes and some new features, including: * A new Soft Debugger add-in (requires the upcoming 2.6 Mono release or trunk) * Improved debugging experience for ASP.NET and Moonlight * New debugging options panel * Some text editor improvements: code focus and caret highlighting. Release notes: http://monodevelop.com/Download/Release_Notes/Release_Notes_for_MonoDevelop_2.2_RC_1 A complete description of what's new in MonoDevelop 2.2 is available here: http://monodevelop.com/Download/What%27s_new_in_MonoDevelop_2.2 Sources and packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] [MonoDevelop] MonoDevelop 2.2 Beta 2 released
El dc 14 de 10 de 2009 a les 12:20 -0700, en/na Mike Christensen va escriure: Will MonoDevelop 2.2 (final release) support the debugging of Mono web applications on OS/X? Or will that remain only supported on Linux? Linux and Windows only. Thanks! Mike On Wed, Oct 14, 2009 at 12:03 PM, Lluis Sanchez Gual ll...@novell.com wrote: The MonoDevelop team is proud to announce the release of MonoDevelop 2.2 Beta 2 (2.1.1). This is the first release of a series of releases that will lead to MonoDevelop 2.2, hopefully around November. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. MonoDevelop enables developers to quickly write desktop and ASP.NET Web applications on Linux, Windows and Mac OSX. MonoDevelop makes it easy for developers to port .NET applications created with Visual Studio to Linux and to maintain a single code base for all platforms. This release includes plenty of bug fixes and an important change: the license of MonoDevelop has been changed from GPL to LGPL 2.1. Release notes: http://monodevelop.com/Download/Release_Notes/Release_Notes_for_MonoDevelop_2.2_Beta_2 A complete description of what's new in MonoDevelop 2.2 is available here: http://monodevelop.com/Download/What%27s_new_in_MonoDevelop_2.2 Sources and packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Monodevelop-list mailing list monodevelop-l...@lists.ximian.com http://lists.ximian.com/mailman/listinfo/monodevelop-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Can not startup Windows version MonoDevelop 2.2 Beta 1
Try using the latest windows installer from: http://monodevelop.com/Download/Trunk_Builds El dj 01 de 10 de 2009 a les 16:02 -0600, en/na chuchieh...@micron.com va escriure: (1) I am trying to use Windows version MonoDevelop. My computer already got .NET framework 3.5 and couple other older version of .NET framework. Downloaded and installed Gtk# for .NET 2.12.9. Downloaded and installed MonoDevelop 2.2 Beta 1 version (MonoDevelop-2.2.b1.msi). From the start button to startup MonoDevelop. The hour glass will show for couple seconds and gone. Nothing else happen. All installation I tried are using default path setting. Actually tried above process twice and same result. What I missed or missing? (BTW: I endup used Xdevelop a little bit which has more success running Windows.Forms managed apps both on Windows and RedHad Linux). (2) I know that Mono version is upto 2.4 now. Do not see a package from mono website for RedHat. What should I do to (or where I can) get a version 2.4 mono framework for Linux RedHat 2.6 version (which should work with MonoDevelop, X-develop Linux version also)? Do I need to checkout Mono source onto my RedHat box and GNU rebuild Mono to get my own RedHat version 2.4 mono? Have anyone done this before? This is my 4th days experience on mono. Thanks for your help. The message may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 2.2 Beta 1 released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.2 Beta 1 (2.1). This is the first release of a series of releases that will lead to MonoDevelop 2.2, hopefully around the end of October. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. MonoDevelop enables developers to quickly write desktop and ASP.NET Web applications on Linux, Windows and Mac OSX. MonoDevelop makes it easy for developers to port .NET applications created with Visual Studio to Linux and to maintain a single code base for all platforms. This release contains lots of new features and improvements. Here is a summary of the new features: * Windows and Mac OSX are now officially supported platforms * Support for multiple target runtimes * Per mime-type formatting settings * Custom execution modes * Text Editor improvements: * Support for auto-save * Improved code templates, which now can have placeholders * Block selection * C# and XML formatters * On-the-fly formatting * Acronym matching in code completion * Dynamic Abbrev command * Code generation window * New code refactoring engine, with plenty of new operations * Resolve namespace, remove and organize 'using' declarations * Rename refactoring with preview. In-line rename for variables and parameters. * Extract method * Declare Local Variable and Integrate Temporary Variable * Introduce constant * Move type to own file * Create/remove the backing store of a property * Debugger improvements: * Immediate window * Win32 debugger * ASP.NET MVS add-in * IPhone add-in for MonoTouch development. * Moonlight add-in * Python binding * Version Control improvements: * Show annotations command * Create patch command * Many other fixes in the C/C++ binding, database support, Vala. A more complete description of what's new in MonoDevelop 2.2 is available here: http://monodevelop.com/Download/What%27s_new_in_MonoDevelop_2.2 Release notes: http://monodevelop.com/Download/Release_Notes/Release_Notes_for_MonoDevelop_2.2_Beta_1 Sources and packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-dev] Debugger not working on trunk?
Hi The debugger from trunk is not working for me at all. I'm trying the mdb command line debugger. It just hangs when doing 'run' on the most simple hello world app. Is anybody else experiencing this problem or am I the only one? Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] Unable to find 'resgen' tool
The problem is that resgen does not come with the default 3.5 framework runtime. You need to install the Framework SDK. El dc 01 de 07 de 2009 a les 14:06 -0700, en/na Darrek va escriure: I am trying to build a program solution from Visual Studio, but I keep getting this error that it cannot find the resgen tool. Any suggestions? I am using Windows. I have searched the forums, but haven't been able to find a solution to this problem. I have the 3.5 framework installed. http://www.nabble.com/file/p24297135/unabletofindresgentool.png ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Use MonoTouch In MonoDevelop for Windows
El dj 02 de 07 de 2009 a les 11:34 +0200, en/na Lennie De Villiers va escriure: Hi, I've the latest Mono and MonoDevelop for Windows, where can I get the templates etc for writing MonoTouch iPhone apps? There are no such templates yet, and even if we had them, I fear you won't be able to develop iPhone apps on windows because the required iPhone build tools are only available for Mac. thanks cheers Lennie -- Lennie De Villiers Blog: http://lenniedevilliers.blogspot.com/ ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Installers
El dl 18 de 05 de 2009 a les 21:13 -0400, en/na Miguel de Icaza va escriure: I could see Mono.Addins going either way. It probably is used by enough Gtk# apps to justify it being in the Gtk# installer. My only concern with Mono.Addins is that once we ship it, it is effectively set in stone (or we have to incrementally add new versions of it, one for each API breakage). The question is whether Mono.Addins API is ready to be frozen or not. Yes, it is. The api has been stable since the first release. All changes have been backward-compatible additions. Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-list] MonoDevelop 2.0 Beta 2 Released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.0 Beta 2 (1.9.3). MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. This release is the last step before the final release of MonoDevelop 2.0. It contains lots of bug fixes, some performance improvements and memory use reductions. Complete release notes are available here: http://www.monodevelop.com/Release_notes_for_MonoDevelop_2.0_Beta_2 Sources and packages are available here: http://www.monodevelop.com/Download_-_Unstable Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Can't debug from monodevelop with 2.2
Looks like your debugger is not in sync with your installed mono. If you compiled the debugger from sources, you should recompile it again. El dj 19 de 02 de 2009 a les 16:57 +0100, en/na pablosantosl...@terra.es va escriure: Hi, I've upgraded my develop machine main mono installation to 2.2 and now I can't debug using monodevelop (ouch!). Whenever it tries to launch a process it says it needs Mono.Cecil 0.6.8.8607 but now what I have is something like 0.6.9.xxx I've tried with the latest monodevelop (just downloaded from the monodevelop site using the 1 click install), but same problem... Any pointers will be welcomed since we're *all* moving to MD today... Thanks, pablo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Can't debug from monodevelop with 2.2
El dj 19 de 02 de 2009 a les 21:19 +0100, en/na pablosantosl...@terra.es va escriure: Hi Lluis, Just installed from the official repositories: mono 2.2 and your last MD. It works with mono 2.0.1 I'm using OpenSuse 11 Another question: it seems the variable inspection does not work with generic collections, does it? Nope, due to limitations in the Mono debugger, inspection of generic collections may not work. Thanks, pablo Lluis Sanchez escribió: Looks like your debugger is not in sync with your installed mono. If you compiled the debugger from sources, you should recompile it again. El dj 19 de 02 de 2009 a les 16:57 +0100, en/na pablosantosl...@terra.es va escriure: Hi, I've upgraded my develop machine main mono installation to 2.2 and now I can't debug using monodevelop (ouch!). Whenever it tries to launch a process it says it needs Mono.Cecil 0.6.8.8607 but now what I have is something like 0.6.9.xxx I've tried with the latest monodevelop (just downloaded from the monodevelop site using the 1 click install), but same problem... Any pointers will be welcomed since we're *all* moving to MD today... Thanks, pablo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] what about debugger in monodevelop
El dt 17 de 02 de 2009 a les 07:23 -0300, en/na Daniel Soto va escriure: Hi List! I've take a look to new features in Monodevelop Beta 1, released few days ago (yesterday to be more exact). But I not see the built-in debugger integration in the feature list. According to Mono roadmap, the future release of Mono 2.4 in March 2009 it will include Monodevelop 2.0 with built-in debugger integration. This will be true? Anyone has test the Beta 1 of Monodevelop? The release notes only describe new features. Debugger integration was included in the previous release. Mono is every day greater!! Thanks! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 2.0 Beta 1 released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.0 Beta 1 (1.9.2). This is the third release of a series of releases that will lead to MonoDevelop 2.0 around the end of March. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. This release contains several new features and improvements, including: * Per-project/solution policies. * Better support for the MSBuild format. * Improved code completion support. * New Go to File/Type dialog with acronym matching support. Complete release notes are available here: http://www.monodevelop.com/Release_notes_for_MonoDevelop_2.0_Beta_1 Sources and packages are available here: http://www.monodevelop.com/Download_-_Unstable Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] mono-find-(provides|requires)
El dv 12 de 12 de 2008 a les 08:56 -0700, en/na Andrew Jorgensen va escriure: There are some significant problems with the mono-find-(provides| requires) scripts as they exist now. Some examples will illustrate the problem best: smuxi requires mono(log4net) which is provided by log4net but it is also provided by mojoportal. If you install mojoportal and then smuxi you will not get log4net and smuxi will not run. As a stop-gap we currently filter the provides to remove things likelog4net from the provides list of mojoportal, for instance, but this is hacky and difficult to maintain. The first logical step is to modify mono-find-provides so that it does not emit a provides for anything which is not in the gac. This has the following problem: monodevelop-boo requires mono(MonoDevelop.Core) but if mono-find-provides does not emit provides for things not installed in the gac then nothing provides mono(MonoDevelop.Core). We could manually say that monodevelop provides mono(MonoDevelop.Core) but this would be error-prone and difficult to maintain, particularly as API versions may change between releases and the packager has no easy way to see that change. What's special about monodevelop-boo is that it is an add-in, and add-ins depend on private (non-gac) assemblies of the applications they extend. I think the best solution is to have a tool which can detect add-ins and extract information about what they provide/require. Add-ins have an ID and a version number, and explicit information about which other add-ins they depend upon (with version numbers too). So it makes sense to use that information when building package dependencies. There is already a tool called mautil which can detect and show information about add-ins. You can run 'mautil info some.dll' and it will print the header of the add-in and some other information. I can implement a new option in that command to show the list of provides/requires in a way that can be easily parsed by mono-find-provides/requires. Mono.Addins supports several ways of declaring add-ins and dependencies. It can be done with an standalone xml manifest, or with an xml manifest embedded as resource, or using custom attributes. mautil would have to be used to check every assembly, but also all .addin and .addin.xml files. Improving mono-find-provides/requires in this way would be useful not only for MD, but also for any application based on Mono.Addins. Perhaps there's a way to check if a particular requirement is going tobe satisfied from the gac or from some other location and not emit arequires if it's not satisfied by the gac? Then packagers would have to manually add a requires on the package that provides the assembly. Also not desirable I think. Another option would be to insist that MonoDevelop installMonoDevelop.Core to the gac but maybe that's undesirable. Or maybe itis? Please let me know if that's a good solution. I don't know how best to solve this issue but it needs to be solved. As more mono-based packages are added to linux distributions the problem will grow. Please share your well-reasoned ideas and / or proposed patches. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-list] MonoDevelop 2.0 Alpha 2 released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.0 alpha 2 (1.9.1). This is the second release of a series of releases that will lead to MonoDevelop 2.0. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. This release contains lots of new features and improvements, including: * Integrated debugger (for managed and native applications) * Better support for the MSBuild format. * A new code completion engine, with basic support for C# 3. * vi modes support in the editor. * Improved support for editing ASP.NET pages. Complete release notes are available here: http://www.monodevelop.com/Release_notes_for_MonoDevelop_2.0_Alpha_2 Sources and packages are available here: http://www.monodevelop.com/Download_-_Unstable Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Ideas for Mono on Windows
El dc 12 de 11 de 2008 a les 10:43 +0100, en/na Rolf Bjarne Kvinge va escriure: Hi, As one of the true maintainers of classlibs I'm completely against ideas to drop cygwin support as it completely destroys my hacking life (note that I don't mean I dislike adding VS build support), but anyways here I agree with jpobst on the part to keep using dll.sources. Here is what I do for adding new source files into svn: - Update *.dll.sources file: ls ../../build/common/*.cs */*.cs | sort System.Foo.Bar.dll.sources make - Collect which files should be mentioned in ChangeLog: svn diff FooBar.dll.sources - copy the rectangle(s) on the console output - Add new files to svn (and svn propdel svn:executable): copypaste those lines in svn add command line. Can these tasks ever easier by switching to your beautiful xml csproj? In MWF land did we create csproj-sources converter? In MWF land there's a sources-csproj converter. In vbnc land there's a vbproj-sources converter. I guess it depends on whoever is maintaining the code. IMHO as a starter it would be nice to have csproj's for all classlibs in svn, generated automatically in the makefiles (they way it's done in MWF), especially now that MD doesn't seem to be able to open the Makefiles anymore I'm not aware of any problem opening Mono's Makefiles. (this isn't only for VS people, it would be useful for MD people too). Rolf ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-list] Mono.Addins 0.4 released
Hi, I'm pleased to announce the release of Mono.Addins 0.4. Mono.Addins is a generic framework for creating extensible applications, and for creating libraries which extend those applications. The 0.4 release includes several improvements and bug fixes: * Added support for specifying paths to exclude from the add-in scan in .addins files [1] and in add-in manifests [2]. * There are several new flags [3] which can be applied to add-ins: * Can't uninstall: the add-in can't be uninstalled. * Can't disable: the add-in can't be disabled. * Hidden: the add-in won't be visible in the setup tools. * Fixes in the add-in scanner. * The new (and optional) Mono.Addins.CecilReflector assembly provides a Cecil-based backend for the add-in scanner. This scanner is more reliable than the reflection based scanner. * When updating the registry, the add-in scanner will only update add-ins belonging to the running application (ignoring directories from other instances of the same or different applications sharing the same registry). * Fixed issue with path length limitation in Windows. * Other bug fixes and API improvements. If you are interested in knowing more about Mono.Addins, take a look at http://www.mono-project.com/Mono.Addins. You can download a tarball from: http://ftp.novell.com/pub/mono/sources/mono-addins/mono-addins-0.4.tar.bz2 Enjoy! Lluis. [1] http://www.mono-project.com/Mono.Addins_Reference_Manual#Add-in_folders [2] http://www.mono-project.com/Mono.Addins_Reference_Manual#Files_included_in_an_add-in [3] http://www.mono-project.com/Mono.Addins_Reference_Manual#The_add-in_header ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Mono.Addins suppress console window showing
Fixed. Thanks! El dv 04 de 07 de 2008 a les 01:11 +0300, en/na Vladimir Dimitrov va escriure: Hello guys, Recently I started using Mono.Addins in my application and it looks very good. But as the application is primary used under windows (should be working fine under Linux too) I get an annoying console window showing when I run: AddinManager.Initialize (); And then another one when I run: AddinManager.Registry.Rebuild (null); I noticed in the code that at some point the .dll executes itself in a separate process ??!?! So if we add the following line: process.StartInfo.CreateNoWindow = true; to the file Mono.Addins/Mono.Addins/Database/SetupProcess.cs this would suppress the window to show under Window and should not cause any other complications. Please let me know what you think. Best regards, Vladimir Dimitrov P.S. I tried compiling my own copy with the change but it didn’t worked because when the process was trying to execute the .dll I compiled an exception was throws saying this is not a valid windows app. Maybe I need to compile it to .exe and just rename it? ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono.Addins suppress console window showing
I'll commit the fix. Thanks!!! El dv 04 de 07 de 2008 a les 10:10 +0300, en/na Vladimir Dimitrov va escriure: Thanks Brad, Yes that worked and I don't see any problems with the line that I talked about being added so if the developer of this library is somewhere around he could add the change to the main source so everybody can get the fix. - Vlad -Original Message- From: Brad Taylor [mailto:[EMAIL PROTECTED] Sent: Friday, July 04, 2008 5:31 AM To: Vladimir Dimitrov Cc: Mono-devel-list@lists.ximian.com Subject: Re: [Mono-dev] Mono.Addins suppress console window showing Hey Vlad, Recently I started using Mono.Addins in my application and it looks very good. But as the application is primary used under windows (should be working fine under Linux too) I get an annoying console window showing when I run: snip You can also compile Mono.Addins as a winexe target to suppress the console. You'll probably have to rename it to a .dll afterwards if you compile under Windows. Hope this helps, -Brad No virus found in this incoming message. Checked by AVG. Version: 8.0.134 / Virus Database: 270.4.4/1531 - Release Date: 02.7.2008 г. 19:02 ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-list] MonoDevelop 2.0 Alpha 1 released
The MonoDevelop team is proud to announce the release of MonoDevelop 2.0 alpha 1 (1.9). This is the first release of a series of releases that will lead to MonoDevelop 2.0, hopefully around the end of the year. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. This release contains lots of new features and improvements, including: * Better support for the MSBuild format. * Support for opening multiple solutions. * Code completion for ASP.NET and XML files. * Improved editor with code folding, incremental search, split view. * New assembly browser. * Basic code metrics add-in. * Vala add-in. Complete release notes are available here: http://www.monodevelop.com/Release_notes_for_MonoDevelop_2.0_Alpha_1 Packages are available here: http://www.monodevelop.com/Download_-_Unstable Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Help! I accidentally deleted Button from my Widgets in the Toolbox
Right click on the toolbox - Add Items - select Gtk.Button El dc 04 de 06 del 2008 a les 07:10 -0700, en/na xt225geo va escriure: I accidentally deleted the Button widget from my toolbox in the IDE, and now I can't find it to restore it. Can someone please walk me through this? I know- really a dumb question... but it's really frustrating when trying to learn a new IDE you have to stop everything to correct a seemingly simple mistake. I am running Mono Develop in Ubuntu Hardy Heron. Thanks in advance for any help. -Chris ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Problem enabling Release Configuration in Monodevelop
You can change the active configuration using the combobox in the build toolbar. El ds 10 de 05 del 2008 a les 14:39 -0700, en/na Travis Miller va escriure: I just freshly installed Ubuntu 8.04 on my desktop (not an upgrade). Mondevelop runs fine except for one problem. When I try to switch from Debug to Release Configuration under options for a project all it says is Rmove or Rename in reference to the configuration. It used to be that right clicking on the Release configuration gave the option of enabling that configuration. Now however it does not. This is pretty much a show stopper as not being able to get a release exe out of the IDE makes it little more than worthless. Travis Miller ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono HEAD eating all CPU
Hmm, looks like I can repro anymore after updating again. El dc 07 de 05 del 2008 a les 04:24 +0200, en/na Lluis Sanchez Gual va escriure: I updated mono to HEAD and now MonoDevelop eats all CPU when running. I think this is caused by the InotifyWatcher code, since if I define MONO_MANAGED_WATCHER=1 everything works fine. This is the managed stack trace of the thread waiting on the watcher: tid=0x0x47432b90 this=0x0x488678: at (wrapper managed-to-native) System.IO.InotifyWatcher.ReadFromFD (intptr,byte[],intptr) 0x4 at (wrapper managed-to-native) System.IO.InotifyWatcher.ReadFromFD (intptr,byte[],intptr) 0x at System.IO.InotifyWatcher.Monitor () [0x00010] in /home/lluis/work/mcs/class/System/System.IO/InotifyWatcher.cs:369 at (wrapper runtime-invoke) System.Object.runtime_invoke_void (object,intptr,intptr,intptr) 0x And this is the stack trace shown by gdb. That mono_thread_interruption_checkpoint_request call looks weird to me. #0 0xe410 in __kernel_vsyscall () #1 0x4020203b in read () from /lib/libc.so.6 #2 0x4639d7fd in ?? () #3 0x in ?? () #4 0x007ae010 in ?? () #5 0x1000 in ?? () #6 0x408b40aa in ?? () #7 0x007ae010 in ?? () #8 0x0943dcf0 in ?? () #9 0x0943dcf0 in ?? () #10 0x081008c3 in mono_thread_interruption_checkpoint_request ( bypass_abort_protection=-9) at threads.c:3449 #11 0x4639d71c in ?? () #12 0x in ?? () #13 0x007ae000 in ?? () Any clue? Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Mono HEAD eating all CPU
I updated mono to HEAD and now MonoDevelop eats all CPU when running. I think this is caused by the InotifyWatcher code, since if I define MONO_MANAGED_WATCHER=1 everything works fine. This is the managed stack trace of the thread waiting on the watcher: tid=0x0x47432b90 this=0x0x488678: at (wrapper managed-to-native) System.IO.InotifyWatcher.ReadFromFD (intptr,byte[],intptr) 0x4 at (wrapper managed-to-native) System.IO.InotifyWatcher.ReadFromFD (intptr,byte[],intptr) 0x at System.IO.InotifyWatcher.Monitor () [0x00010] in /home/lluis/work/mcs/class/System/System.IO/InotifyWatcher.cs:369 at (wrapper runtime-invoke) System.Object.runtime_invoke_void (object,intptr,intptr,intptr) 0x And this is the stack trace shown by gdb. That mono_thread_interruption_checkpoint_request call looks weird to me. #0 0xe410 in __kernel_vsyscall () #1 0x4020203b in read () from /lib/libc.so.6 #2 0x4639d7fd in ?? () #3 0x in ?? () #4 0x007ae010 in ?? () #5 0x1000 in ?? () #6 0x408b40aa in ?? () #7 0x007ae010 in ?? () #8 0x0943dcf0 in ?? () #9 0x0943dcf0 in ?? () #10 0x081008c3 in mono_thread_interruption_checkpoint_request ( bypass_abort_protection=-9) at threads.c:3449 #11 0x4639d71c in ?? () #12 0x in ?? () #13 0x007ae000 in ?? () Any clue? Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] monodevelop
Please use http://lists.ximian.com/mailman/listinfo/monodevelop-list El dt 08 de 04 del 2008 a les 21:54 +1000, en/na Lindsay Mathieson va escriure: Is this the correct list for monodevelop issues? ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] [MonoDevelop] Mono 1.9 / MD Idea
El ds 05 de 04 del 2008 a les 15:13 +0200, en/na Petit Eric va escriure: Hi folk I have folowed this step and have a little trouble. My system is MDV 2008, after a fresh install i had Mono 1.25 and MD , located in /usr/ dir, i think about trying mono 1.9, so uninstall all rpm, download the linux generic install from mono and install it in /opt/ dir. When starting MD in the good environment (/opt/) i have error message about file in /usr/lib/monodevelop Knowing the error message you got would be helpful. So i delete/clean evrything in ~/.config about MD/Mono and then no more problem, so i conclude there is some config file with absolute path and/or environment var. It isn't possible to use the startup path than the one in the config files? Well, I don't know which config path is that. Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono.Addins
El dg 06 de 04 del 2008 a les 12:23 +0200, en/na Steinar Herland va escriure: Please forgive me for not sending this directly to http://groups.google.com/group/mono-addins - Only members can send to the list. The files - Mono.Addins.Database\IAssemblyReflector.cs - Mono.Addins.Database\DefaultAssemblyReflector.cs .. are not included in Mono.Addins.csproj. Can somebode please add them? Done. I need to use the svn-version of Mono.Addins because the TypeExtensionNode now exposes the type - Which can then be used by www.codeplex.com/unity to construct / resolve the object. Btw: Anybody know when the next version of Mono.Addins is scheduled for release? There are a couple of issue I want to fix. Maybe in a month or so. Steinar Herland CTO, www.gecko.no ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] [MonoDevelop] Mono 1.9 / MD Idea
El ds 05 de 04 del 2008 a les 15:13 +0200, en/na Petit Eric va escriure: Hi folk I have folowed this step and have a little trouble. My system is MDV 2008, after a fresh install i had Mono 1.25 and MD , located in /usr/ dir, i think about trying mono 1.9, so uninstall all rpm, download the linux generic install from mono and install it in /opt/ dir. When starting MD in the good environment (/opt/) i have error message about file in /usr/lib/monodevelop Knowing the error message you got would be helpful. So i delete/clean evrything in ~/.config about MD/Mono and then no more problem, so i conclude there is some config file with absolute path and/or environment var. It isn't possible to use the startup path than the one in the config files? Well, I don't know which config path is that. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] [MonoDevelop] Soc 2008 idea: Universal graphical Framwork
A user interface designer is not like a drawing tool. The controls you put in the design surface must look and behave exactly like the controls at run-time. They are not graphical representations of the run-time controls, they are the *real* controls running in a special design mode. To do what you propose you would need to replicate gtk#, winforms and any other widget library you want to support using the designer framework. Even if you do that (which would take several years) it wouldn't work for custom widgets which use custom rendering. MonoDevelop already provides a toolbox and a property grid which can be shared by all designers. There isn't much more you can share. Lluis. El dj 27 de 03 del 2008 a les 12:48 +0100, en/na Gryffus va escriure: Wow this would be great!! Would be possible to implement later winforms designer (someone worked on it, but i dont know why it disappeared) and qt4 designer?? :-)) Gfs Sharique uddin Ahmed Farooqui napsal(a): Hi, We need different types of graphical designers like, xml designer, class designer, xaml designer, moonlight designer, etc. I think we should have a base framework, which will provide basic features like canvas and few controls and Monodevelop addin api. So that one can easily add there desired designer in monodevelop (a PCB designer for example). What are ur views friends? ___ Monodevelop-list mailing list [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/monodevelop-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] Process SOAP without web service
El dj 20 de 03 del 2008 a les 12:56 -0400, en/na Tim Howard va escriure: Can someone help me with this? I want to be able to process SOAP messages without relying on a web service/web server. I've done a lot of research and many searches but can't find the answer. You can setup an HTTP remoting channel using the Soap formatter on your applications. There is plenty of information on the web about how to do it. Obviously all of the pieces are there, but I can't figure it out. I thought using a SoapMessage was the way to go, but I guess that's an abstract class for mainly writing extensions. There's the SoapReader and various things like that but I guess I don't know enough. I can handle receiving the message from the requester, that's no problem. And I don't mind doing a little leg work, like possibly switching on the method name to call the right function. So if someone could point me in the right direction that would be great. P.S. - I love Mono. :) Thanks. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Deprecating some Mono commands, Cecil mono-api-info
El dv 29 de 02 del 2008 a les 00:27 +0100, en/na Robert Jordan va escriure: Jonathan Pryor wrote: On Fri, 2008-02-29 at 00:00 +0100, Mirco Bauer wrote: * prj2make - Use MonoDevelop instead. Hmmm, the only problem I see is that there is no easy known way to use prj2make from command-line only through MonoDevelop. I know that some non-C# developers use prj2make in debian to get some software compiled on their system that only ships visual studio project files. My I introduce you to mdtool? mdtool build --buildfile:FILE --project:PROJECT Someone really needs to write a man page for mdtool. (I'm not volunteering; I have enough man pages to write for mdoc as it is...) IIRC, VS.NET 2003 projects have to be interactively imported prior to being able to build them. I think that's already fixed. It is also possible to use mdtool project-export to convert the format of projects. Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-list] MonoDevelop 1.0 RC1 released
The MonoDevelop team is proud to announce the release of MonoDevelop 1.0 RC1 (0.19). MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. This release is the last step before the final release of MonoDevelop 1.0. It contains lots of bug fixes, some performance improvements and memory use reductions. Complete release notes are available here: http://www.monodevelop.com/Release_notes_for_MonoDevelop_1.0_Release_Candidate_1 Packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] MonoDevelop 1.0 RC1 released
El dj 14 de 02 del 2008 a les 18:30 +0100, en/na Bálint Kardos va escriure: Joseph, thank you for the info! However, on the http://www.monodevelop.com/Download page it is not mentioned anyhow - it just links to old howto page of OS X install. Possibly it would be a good idea to update this page with this information. Done. b. On 14/02/2008, Joseph Hill [EMAIL PROTECTED] wrote: MonoDevelop is included in the installer for Mac OS X as of last week. http://www.mono-project.com/Downloads Ref: http://tirania.org/blog/archive/2008/Feb-07-2.html Enjoy Joseph On Thu, 14 Feb 2008 14:35:49 +0100, Bálint Kardos [EMAIL PROTECTED] said: Dear Lluis Mono Develop Team, when can we expect an OS X (native) version of MonoDevelop? (Or at least an installer with all the required items included) The steps currently required to install it on OS X makes it really hard a trip... within, programs working under X1 are slw and ugly, it's not the real way to use it in the Mac Universe :( üdvözlettel with regards Kardos Bálint On 14/02/2008, Lluis Sanchez [EMAIL PROTECTED] wrote: The MonoDevelop team is proud to announce the release of MonoDevelop 1.0 RC1 (0.19). MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. This release is the last step before the final release of MonoDevelop 1.0. It contains lots of bug fixes, some performance improvements and memory use reductions. Complete release notes are available here: http://www.monodevelop.com/Release_notes_for_MonoDevelop_1.0_Release_Candidate_1 Packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list -- Joseph Hill [EMAIL PROTECTED] -- üdvözlettel with regards Kardos Bálint ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Advice on optimisation in xml deserialisation
Regarding xml serialization performance, you should take into account
that MS.NET and Mono have an important difference. The first time you
try to serialize or deserialize a type, MS.NET generates and compiles an
add-hoc serializer for the required types on the fly. Mono on the other
hand, only generates the add-hoc serializer after a given number
serializations (this threshold can be set using the
MONO_XMLSERIALIZER_THS env var).
In your test case MS.NET will be better because you are deserializing a
lot of data and the overhead of generating the add-hoc serializer, even
for a single deserialization, is worth it.
Mono will be worse in this case, but will be better in other cases. You
can try setting MONO_XMLSERIALIZER_THS=0 to make Mono behave like
MS.NET.
Lluis.
El dj 10 de 01 del 2008 a les 19:11 +, en/na Alan McGovern va
escriure:
Ok, here's an updated patch which caches the method for reuse as long
as both the list type and listitemtype are the same as the previous
invocation.
This gives a modest 13% increase in performance for the testcase i was
using. Let me know if this is good to commit as-is.
Just as a point of style, should i put the variable declarations at
the top of the .cs file with a comment specifying how they are used?
Or should i leave them as they are.
Alan.
On Jan 10, 2008 3:26 AM, Alan McGovern [EMAIL PROTECTED] wrote:
(and to the list again... doh)
On Jan 10, 2008 3:26 AM, Alan McGovern [EMAIL PROTECTED] wrote:
Hi,
Yeah, by reducing the method searchs performance increases by 15% or
so. I'll work that patch up tomorrow at some stage.
Thanks,
Alan.
On Jan 10, 2008 1:07 AM, Robert Jordan [EMAIL PROTECTED] wrote:
Hi,
I've filed it:
https://bugzilla.novell.com/show_bug.cgi?id=352805
BTW, the previousObject check in your patch is still useful,
as it cuts down the type.GetMethod (Add) calls from
collectionLength to 1, if I understand the patch correctly.
Just remove the CreateDelegate stuff and extend the optimization
to cover NET 1.1 as well.
Robert
Alan McGovern wrote:
(and also sending to the list...)
On Jan 10, 2008 12:41 AM, Alan McGovern [EMAIL PROTECTED] wrote:
Hi,
I was wondering about that alright. It did seem a bit weird that it
would work, i would've expected the delegate parameter to be at least
as restrictive as the method i was calling. Bang goes that idea then.
Alan.
On Jan 10, 2008 12:36 AM, Robert Jordan [EMAIL PROTECTED] wrote:
Robert Jordan wrote:
Alan McGovern wrote:
There was a thread a week or two ago called 'Speed difference
Windows
- Linux' which noted there was a big difference in performance
between
.NET and mono. I did a brief bit of profiling and came up with
this
patch which improves performance ~30% for the testcase which was
attached in the email. This reduces runtime memory usage by about
10MB
(80MB - 70MB) and decreases processing time by 30% (3.4s -
2.6s).
Anyone have any ideas on how to tidy this up to make it neater?
Also,
would this optimisation be too specific, or can it be generalised
somewhere higher up in the stack.
I don't think the patch is correct. It is assuming that every
Add method of a collection/list is compatible with
AddDelegate(object).
If the test cases are still working, it could be that
CreateDelegate is buggy: MSDN states:
A parameter of a delegate is compatible with the corresponding
parameter of a method if the type of the delegate parameter is more
restrictive than the type of the method parameter, because this
guarantees that an argument passed to the delegate can be passed
safely
to the method.
It's indeed a bug in Mono's CreateDelegate. The following test case
must fail but it doesn't:
using System;
delegate void Method(object o);
class T
{
static void Main ()
{
T t = new T ();
Method m = (Method) Delegate.CreateDelegate
(typeof(Method), t,
t.GetType ().GetMethod (Test));
m (new Uri (http://mono-project.com;));
}
public void Test (Uri uri)
{
Console.WriteLine (uri);
}
}
Robert
___
Mono-list maillist - Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
___
Mono-list maillist - Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
___
Mono-list maillist - Mono-list@lists.ximian.com
Re: [Mono-dev] error while compiling Monodevelop
Hi, This error usually means that you don't have the -devel packages of mono installed. They are required to compile MD. Lluis. El dg 16 de 12 del 2007 a les 22:36 +0530, en/na Sharique uddin Ahmed Farooqui va escriure: error while compiling Monodevelop 1.0 beta 2 checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for UNMANAGED_DEPENDENCIES_MONO... no checking for UNMANAGED_DEPENDENCIES_MINT... no configure: error: Please install mono version 1.1.10 or later to install MonoDevelop. Please see http://www.mono-project.org/ to download latest mono sources or packages I'm using fedora 8 64 bit, I have mono 1.2.5 / Mono develop0.13 , installed via Add/remove programe -- Sharique uddin Ahmed Farooqui (C++/C# Developer, IT Consultant) A revolution is about to begin. A world is about to change. And you and me are the initiator. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono.Addins in Monodoc
Hi! El dc 19 de 12 del 2007 a les 12:36 -0500, en/na Miguel de Icaza va escriure: * Editing in the ECMA provider is hard, but Mike has a plan for that. Is there any doc or something we could review? No, we only spoke on the phone about it. The idea is that Mike wants to switch to use GtkTextView to render the documentation, and at the same time, this would allow us to implement editing very easily. Even if GtkHtml is very limited, it is much better than GtkTextView in rendering text. At least it can render tables, borders, change background colors, etc. GtkTextView can't do that. Maybe implementing editing would be easier with GtkTextView, but most of people will use MonoDoc for reading rather than writing documentation. So I don't think reducing the text rendering capabilities to make it easier to edit documentation is a good deal. Correct, there are many things that we could do to improve the pipeline for new documentation. Some of those ideas are also required for the Web edition of Monodoc. Having a hammer does not mean that everything is a nail, and for the case of documentation updating we should not start with We have Mono.Addins, now how do we do updates with it. Instead we should be thinking about creating the proper pipeline for documentation: what does it look like, what is the process, and then implement it. If the implementation would benefit from Mono.Addins, that is fine, but it should not be the driving force for it. Fair enough. Just make sure you guys consider Mono.Addins if MonoDoc is going to include any kind of extensibility support (including support for third party libraries to extend MonoDoc with new documentation). Otherwise we'd be reimplementing functionality that M.A. already provides. Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono.Addins in Monodoc
El dj 20 de 12 del 2007 a les 10:15 -0600, en/na Mike Kestner va escriure: On Thu, 2007-12-20 at 14:56 +0100, Lluis Sanchez wrote: The idea is that Mike wants to switch to use GtkTextView to render the documentation, and at the same time, this would allow us to implement editing very easily. Even if GtkHtml is very limited, it is much better than GtkTextView in rendering text. At least it can render tables, borders, change background colors, etc. GtkTextView can't do that. It won't be a TextView, though it may embed one in editing mode if that makes things easier. When Miguel and I talked on the phone, I said Custom Gtk# Widget though I can understand how he could have assumed it would be a TextView subclass. Maybe implementing editing would be easier with GtkTextView, but most of people will use MonoDoc for reading rather than writing documentation. So I don't think reducing the text rendering capabilities to make it easier to edit documentation is a good deal. I don't recall anyone mentioning Reduce Text Rendering Capabilities as a feature for the revisions. I didn't say that's a feature, but it would be a side affect of using GtkTextView instead of GtkHtmlView for rendering. Although it's now clear that you didn't mean to use it in that way, so no problem. I'll try to spend some time developing a plan in the next couple weeks and publish it so everyone can poke holes in it. A couple things are fairly clear to me: 1. Using an HTML widget for monodoc rendering is overkill for the layout we require, and providing Gecko and GtkHTML on all the platforms we want to target with monodoc is a PITA. Then maybe we should define what we expect MonoDoc to be. If MonoDoc will be only a class library documentation browser and editor, a custom widget for rendering class information would be enough. If MonoDoc intends to be a general purpose documentation browser, which includes not only class libraries but also documentation about C#, errors, development tools, user guides, tutorials, etc, then we clearly need something as generic as HTML. 2. Adding WYSIWYG editing to any tool which is based on an HTML widget rendering information already passed through an xslt transformation is going to be problematic. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Remoting performance between two appdomains( plugins) in same process/application
El dc 19 de 12 del 2007 a les 09:03 -0600, en/na Shawn Schaerer va escriure: Hi, I have a question on the performance of remoting between two appdomains running in the same process. We have developed a dynamic dll loading program (plugins) using appdomains and assemblies and need to pass a lot of data between the two plugins. We are passing image data between the two plugins. The size of the data is around 250K Bytes and the transfer happens 15-30 times a second. Question: Is remoting optimized when the appdomains are created in the same process / application ? ( We are passing the objects using MarshalByRefObject) Yes. The cross-app domain channel can send information to the target domain by just copying memory. That's faster than any other IPC method. Also, if the remote methods you call use only primitive types or arrays of primitive types, the cross-app domain channel can avoid the serialization of parameters and can make a direct copy of data, which is much faster. Are the transfers the same as accessing shared memory or is the data still accessed via proxies ? Data is still accessed via proxies, because it is not possible to share managed objects between domains. If you send a MarshalByRef object you'll get a proxy to the object in the source domain. If you send a byte array of 250Kb, the target domain will get a copy of that array. Is there a big performance hit doing this in Mono ? Is there a better solution ? A solution for what? for sending information between appdomains? I don't think there isn't a better solution than remoting. Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Remoting performance between two appdomains( plugins) in same process/application
El dc 19 de 12 del 2007 a les 10:29 -0600, en/na Shawn Schaerer va escriure: Hi, Thanks for the information. I assume that the CrossAppDomainChannel is setup automatically and there is nothing to do to set it up ? Yes, it is setup automatically. When we pass objects between domains it is faster to pass primitive types instead of objects that hold primitives ( image class that holds image data in a byte array) ? Yes. If so, is it a big speed up ? Yes, because the whole object serialization process can be bypassed. Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-list] MonoDevelop 1.0 beta 3 released
The MonoDevelop team is proud to announce the release of MonoDevelop 1.0 beta 3 (0.18). This is the third in a series of beta releases that will lead to MonoDevelop 1.0. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. This release contains lots of bug fixes and some feature improvements. The release highlights include: * An improved dock manager, with support for auto-hide panels. * Better support for Mac OSX. MonoDevelop can now run without X11, using the Gtk+ Quarz driver. * Support for projects targeting the Moonlight runtime. Complete release notes are available here: http://www.monodevelop.com/Release_notes_for_MonoDevelop_1.0_Beta_3 Packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Mono.Addins 0.3 released
Hi, I'm pleased to announce the release of Mono.Addins 0.3. Mono.Addins is a generic framework for creating extensible applications, and for creating libraries which extend those applications. The 0.3 release comes with many bug fixes and some improvements and new features: * Added support for Localization of Add-ins (http://www.mono-project.com/Mono.Addins_Reference_Manual#Localization_of_Add-ins). * Add-in roots can now have dependencies on other add-in roots, and extend extension points defined by those. * Added support for non-shared add-in folders. Add-ins located in such folders won't be visible from other non-shared folders. Folders containing add-in hosts are non-shared by default, which means that different installations of the same application won't interfere each other anymore. * The add-in scanner is now more robust and it is better in reporting scanning errors. * Fixed some issues in the add-in loader, which did not detect add-in changes the first time the host application was started. * New AddinTreeWidget widget in the Mono.Addins.Gui, which can be used by applications to show a tree of add-ins. * Some minor improvements in the API. If you are interested in knowing more about Mono.Addins, take a look at http://www.mono-project.com/Mono.Addins. You can download a tarball from: http://www.go-mono.com/sources/mono-addins/mono-addins-0.3.tar.bz2 Latest from SVN at: svn://anonsvn.mono-project.com/source/trunk/mono-addins Enjoy! Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-dev] Mono.Addins in Monodoc
Hi, For some time I've been thinking about changes required in Monodoc, especially regarding how Monodoc creates the documentation tree and locates the available documentation. I'm posting my ideas here because Mike told me that he is going to spend some time fixing Monodoc, so maybe those ideas are a good starting point for the changes to be made. My idea is to use Mono.Addins to handle all extensibility of Monodoc. There would be at least two extension points: * Documentation providers: classes implementing the Provider class: ecma, man, error, etc. Some abstraction work will be needed, since Provider and HelpSource object creation is hard-coded right now. * Documentation sources: New document nodes to show in the documentation tree. It would replace the existing monodoc.xml file and the sources subdir. The use of add-ins for registering new documentation sources probably requires some more explanation. Here is an example of how the extension point might look like: Addin id=Core namespace=Monodoc version=2.0 isroot=true !-- Declaration of the extension point for help sources -- ExtensionPoint path=/Monodoc/HelpSources ExtensionNode name=Node type=Monodoc.Node / /ExtensionPoint ... Extension path=/Monodoc/HelpSources !-- Some default documentation sources, included in Monodoc -- Node id=classlib label=Class Library provider=ecma file=netdocs / Node id=classlib-mono label=Mono Libraries provider=ecma file=Mono / Node id=ecmaspec label=C# Language Specification provider=ecmaspec file=ecma334 / Node id=dev-tools label=Mono Development Tools / Node id=various label=Various Node id=classlib-nunit label=NUnit Libraries provider=ecma file=nunit-docs / /Node /Extension /Addin So, given this extension point and that set of nodes defined by Monodoc, here are some examples of documentation source add-ins: !-- Add-in which register MonoDevelop api documentation -- Addin id=MonoDevelop namespace=Monodoc.Sources Dependencies Addin id=Core version=2.0 / /Dependencies Runtime !-- Files included in the add-in -- Import file=monodevelop-reference.tree / Import file=monodevelop-reference.zip / /Runtime Extension path=/Monodoc/HelpSources !-- Registers the new node, specifying the provider and source file -- Node id=monodevelop label=MonoDevelop API provider=ecma file=monodevelop-reference / /Extension /Addin Notice that add-ins don't need to be implemented in assemblies. An add-in can just be a set of files. In the example the add-in would be composed by: * Monodoc.Sources.MonoDevelop.addin.xml (with the content above) * monodevelop-reference.tree * monodevelop-reference-zip Another example: Addin id=MonoProfiler namespace=Monodoc.Sources Dependencies Addin id=Core version=2.0 / /Dependencies Runtime Import file=mono-profiler.tree / Import file=mono-profiler.zip / Import file=mono-profiler-man.tree / Import file=mono-profiler-man.zip / /Runtime Extension path=/Monodoc/HelpSources !-- Registers a new node -- Node id=profiler label=Mono Profiler API provider=ecma file=mono-profiler / /Extension Extension path=/Monodoc/HelpSources/dev-tools !-- Register a new child node of dev-tools -- Node id=profiler-tool label=Mono Profiler provider=man file=mono-profiler-man / /Extension /Addin What's nice about using Mono.Addins for all this? * Monodoc can leverage all add-in management functionality that Mono.Addins provides. We could setup an online repository with documentation add-ins and let the user choose which documentation to install. * There would be more flexibility about where to put the documentation sources. Add-ins can be installed at system level or in the user home directory. * Documentation sources can include or pull the documentation providers needed to visualize them. Since all are add-ins, a documentation source add-in can declare dependencies on other source or provider add-ins. * If we share the same add-in space with MonoDevelop, we can publish MD add-ins which include documentation. For example, the MonoDevelop Boo add-in might include documentation about Boo, and that documentation would be visible in Monodoc even if the add-in was installed using the MonoDevelop add-in manager. Lluis. ___ Mono-devel-list mailing
Re: [Mono-dev] Mono.Addins in Monodoc
Adopting Mono.Addins might have some technical advantages, but I think that overall it will get in the way of some required internal work that needs to take place before we start considering more features. The adoption of Mono.Addins is a decision on the application architecture, so it has to be considered from the beginning. By using Mono.Addins you'll get some additional features (for free), but what's more important is that you'll get an application more flexible, easier to maintain and extend. As you say using Mono.Addins will not directly solve any of the big documentation problems we have, but it can indirectly contribute in solution of some of them. Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono.Addins in Monodoc
El dt 18 de 12 del 2007 a les 13:52 -0500, en/na Miguel de Icaza va escriure: The adoption of Mono.Addins is a decision on the application architecture, so it has to be considered from the beginning. By using Mono.Addins you'll get some additional features (for free), but what's more important is that you'll get an application more flexible, easier to maintain and extend. As you say using Mono.Addins will not directly solve any of the big documentation problems we have, but it can indirectly contribute in solution of some of them. I agree, but the extra work to use Mono.Addins, and maintaining the result is much larger than the potential benefits. Well, my opinion on the work needed to use Mono.Addins and the maintenance it requires is obviously biased :) But I'm sure it is much less that people may think. For me the potential benefits are much larger than the extra work, if any, that it requires. In any case, it is not my decision. Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] dead link on mono-project.com/Mono.Addins_Release_Notes
El dj 06 de 12 del 2007 a les 17:02 +0100, en/na Martin Dederer va escriure: Hi, on (1) is a dead link (2). (1) http://www.mono-project.com/Mono.Addins_Release_Notes (2) http://www.go-mono.com/sources/mono-addins/mono-addins-0.3.tar.gz Yes, that's because Mono.Addins 0.3 has not yet been released. Will be soon. Martin Dederer ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] Incompatibility in MONO SelectNodes method
El dg 02 de 12 del 2007 a les 03:29 +0100, en/na Robert Jordan va escriure: Andrus wrote: In bug #343960 https://bugzilla.novell.com/show_bug.cgi?id=343960 I presented code which works OK in .NET but crashes in MONO 1.2.6 pvw2. Probably SelectNodes() in .NET creates new list but in MONO it does not. Atsushi refuses to fix this and marks it INVALID several times. He explained pretty well why he refused to fix it. This is fundamental incompatibility between .NET and MONO XML DOM implementation. MSDN documentation on XmlNodeList: The XmlNodeList collection is live; that is, changes to the children of the node object that it was created from are immediately reflected in the nodes returned by the XmlNodeList properties and methods Which means that if you start iterating on an XmlNodeList and a node included in the list is removed from the parent, the XmlNodeList you are iterating on will change, so you will get an exception if you continue iterating. That's how iterators work. MSDN documentation on SelectNodes(): The XmlNodeList should not be expected to be connected live to the XML document So while an XmlNodeList returned by ChildNodes will always be live, one returned by SelectNodes *may* or *may not* be live. For your specific test case, in Mono the collection is live, in .NET it is not, and both behaviors are correct according to the documentation. So it is not a bug on .NET or Mono, it is a bug in your code. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop user survey: beyond 1.0
Hi, MonoDevelop 1.0 is just around the corner, and it is mostly feature frozen. Now it is time to start thinking beyond 1.0. We have published a survey with the goal of getting a more clear view of what MonoDevelop is being used for, and what features are the most requested. This will help us planning the future directions of the project. This is the url of the survey: http://surveys.mjhutchinson.com/index.php?sid=95822lang=en Thank you for your feedback! The MonoDevelop team. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 1.0 beta 2 released
The MonoDevelop team is proud to announce the release of MonoDevelop 1.0 beta 2 (0.17). This is the second in a series of beta releases that will lead to MonoDevelop 1.0, hopefully around the end of the year. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. This release contains lots of improvements, new features and bug fixes. The release highlights include: * Basic support for ASP.NET web project deployment. * Support for Visual Studio 2005 Web Application projects. * Generation of Satellite Assemblies for localized resources. * Plenty of bug fixes and other improvements. Complete release notes are available here: http://www.monodevelop.com/Release_notes_for_MonoDevelop_1.0_Beta_2 Packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] monodevelop performance
El dg 07 de 10 del 2007 a les 10:51 +0100, en/na Carlos Ble va escriure: Hi guys, For some reason the combination of Beagle and MonoDevelop kills my machine (ubuntu gutsy). The pc is 100% busy reading the disk all the time. It is impossible to use the computer. This could be an entry in the MonoDevelop site FAQs: If the performance is awful kill beagle to see if that is the problem. See http://www.monodevelop.com/Inotify_Watches_Limit. This might fix your problem. By the way, MD 0.16 is very cool!!! Thanks! Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] MonoDevelop 1.0 beta 1 released
The MonoDevelop team is proud to announce the release of MonoDevelop 1.0 beta 1 (0.16). This is the first in a series of beta releases that will lead to MonoDevelop 1.0, hopefully around the end of the year. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. This release contains lots of improvements, new features and bug fixes. The release highlights include: * Support for C/C++ projects. * A new Database Add-in. * Text editor improvements, including on-the-fly error underlining and XML comment tag support. * Plenty of bug fixes and other improvements. Complete release notes are available here: http://www.monodevelop.com/Release_notes_for_MonoDevelop_1.0_Beta_1 Packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] MonoDvelop IDE crash
El dv 14 de 09 del 2007 a les 17:42 +0530, en/na Abir Bhattacharya va escriure: Hi, I have a C# application(usage of extensive graphics) which I am porting to mono . The applications generates runtime images on the OnPaint() method ,however when it runs in mono ,Linux 2.6 the application hangs along with the monodevelop IDE . In some of the instances the images are painted once or twice and then it crashes(the IDE too) . Is it a problem with my mono installation (1.2.3 –JIT version)? Is there any way I can debug my application ? How can I check memory leaks with mono? Without more information like error messages or stack traces it is impossible to know what's the problem. Try starting MonoDevelop from a terminal and see the errors shown there. Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] MonoDevelop Framework
El dv 14 de 09 del 2007 a les 19:08 +0200, en/na José A. Salvador Vanaclocha va escriure: Hi all, I try to use a set of classes/assemblies of monodevelop to get approach of command system architecture. I have been trying for a long set of tests whithout some satisfactory result. I would grateful to you if you can help me in one question about this. Is the command system architecture so loosley coupled to Monodevelop? or Would it be possible, with a little effort, use this structure to get some of their advantages in a third party application?? The command system is implemented in the MonoDevelop.Components assembly, and it is independent from the IDE, so it is not difficult to use it in another application. You'll need Mono.Addins though. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] ToolButton and ToolSeparator xml element at Mono Addins
El dt 11 de 09 del 2007 a les 09:43 +0200, en/na José A. Salvador Vanaclocha va escriure: Hi all, I have been reading all documents about Mono Adddins I find. It seems an excellent framework to acomplish a trully plugeable architecture in an applicattion. However I found some doubts around it. So in the reference manual exists very references to ToolButton and ToolSeparator xml element which are being used at monodevelop too. In fact, the reference manual shows paragraphs like this: The add-in engine ensures that if insertafter is specified... showing a very close relation between these xml attributes and nodes and the framework engine However I can not find these classes at the mono addins assemblies (Mono.Addins, Mono.Addins.Gui, Mono.Addins.Setup) so, where are these classes? Are they at the Mono.Addins Framework? In this case, Are they ready to use out of the box? Mono.Addins does not provide support for ToolButton or ToolSeparator. Those are just examples used in the documentation to show how to create and access to extension nodes. The 'insertafter' and 'insertbefore' attributes are core attributes that can be used in any extension node to specify the relative position of the node in an extension point. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Little Mono Addins documentation errata
El dl 10 de 09 del 2007 a les 18:32 +0200, en/na José A. Salvador Vanaclocha va escriure: Hi, We are studying the mono addins architecture and we have found a little errata in the documentation, we think. Concretely at the host xml ExtensionNode element definition in the Mono Addins Introduction wich displays ... ExtensionPoint path = /TextEditor/TypeExtensions/ICommand ExtensionNode objectType=ICommand/ /ExtensionPoint ... where may be it would say ... ExtensionPoint path = /TextEditor/TypeExtensions/ICommand ExtensionNode NAME=COMMAND objectType=ICommand/ /ExtensionPoint ... We show in uppercase the words we miss. Other way, the sample won't can cut paste to get some mini application works with the mono addins aproach so the xml addin definition shows like this: Addin Runtime Import assembly=SampleAddin.dll/ /Runtime Dependencies Addin id=TextEditor version=1.0 / /Dependencies Extension path = /TextEditor/TypeExtensions/ICommand Command type=HelloWorldExtension / /Extension /Addin This xml structure uses the xml node COMMAND miss at the addin host defintion. You're right, thanks for noticing. It is now fixed. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Sept 14th: MonoDevelop Bug Day
If you found some annoying bugs in MonoDevelop that you'd like to get fixed in the next release. If you reported some bugs which are not yet fixed maybe because we've not been able to reproduce them. If you want to help in tracking down some of the issues that MD has... please join us next friday (September 14th) in the #monodevelop IRC channel (in irc.gimp.org) for an interactive and intense bug hunting effort. MonoDevelop is approaching the beta 1 release, which should happen by the end of the month, so this is a chance for helping the development team in tracking down and fixing MonoDevelop issues. Thanks to all! Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Sept 14th: MonoDevelop Bug Day
El dl 10 de 09 del 2007 a les 12:09 -0700, en/na Daniel Morgan va escriure: I understand this maybe low-priority for you, but I would like to see it fixed - get MonoDevelop to build and run on Win32 - at least console projects building and running out-of-the-box would be nice. I think it would be a stretch to ask for the asp.net and gtk# designers to work too -- however I would not complain if someone did get these to work on Win32 too. :-) Win32 support is down in the priority list, and I don't think we'll have time to spend on it. Another request: improve database support. Remove hard references to the data providers in the MonoQuery add-in. Will the GSoC changes that were done via MonoDevelop.Database be integrated? If so, will MonoDevelop be removed? Just curious. The new MonoDevelop.Database add-in is going to replace MonoQuery, and I hope we can include it in the next release. Data providers are now implemented as add-ins, so there are no hard references anymore. Lluis. --- Lluis Sanchez [EMAIL PROTECTED] wrote: If you found some annoying bugs in MonoDevelop that you'd like to get fixed in the next release. If you reported some bugs which are not yet fixed maybe because we've not been able to reproduce them. If you want to help in tracking down some of the issues that MD has... please join us next friday (September 14th) in the #monodevelop IRC channel (in irc.gimp.org) for an interactive and intense bug hunting effort. MonoDevelop is approaching the beta 1 release, which should happen by the end of the month, so this is a chance for helping the development team in tracking down and fixing MonoDevelop issues. Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/ ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Sept 14th: MonoDevelop Bug Day
El dl 10 de 09 del 2007 a les 15:07 -0500, en/na Austin Winstanley va escriure: How about getting Regions to work? What are the thoughts on this? It would be a great help for organizing large amounts of code... I'm sure it is useful, but that's not a bug, but a missing feature. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Sept 14th: MonoDevelop Bug Day
El dl 10 de 09 del 2007 a les 15:21 -0500, en/na Austin Winstanley va escriure: Ok, well, while I understand it's not going to be in this release, is there any plans to implement Regions at some point? Yes, it's in the plan, but not for MD 1.0. On 9/10/07, Lluis Sanchez [EMAIL PROTECTED] wrote: El dl 10 de 09 del 2007 a les 15:07 -0500, en/na Austin Winstanley va escriure: How about getting Regions to work? What are the thoughts on this? It would be a great help for organizing large amounts of code... I'm sure it is useful, but that's not a bug, but a missing feature. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list -- Thanks, Austin Winstanley Tradelogic Software Group 512.699.6674 ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Compiling monodevelop from SVN
El dl 13 de 08 del 2007 a les 21:06 -0500, en/na Brandon Perry va escriure: I started compiling monodevelop today after I compiled mono/mcs. I keep getting a config error. checking for UNMANAGED_DEPENDENCIES_MONO... no checking for UNMANAGED_DEPENDENCIES_MINT... no configure: error: Please install mono version 1.1.10 or later to install MonoDevelop. Please see http://www.mono-project.org/ to download latest mono sources or packages mono -V says it is 1.2.3.1. Is there something I am missing? I have compiled monodevelop tons of time before, but this is a fresh load and I have no idea what I am missing. You are probably missing some -devel packages. The config.log file has information about the missing packages. Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-list] MonoDevelop 0.15 released
The MonoDevelop team is proud to announce the release of MonoDevelop 0.15. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. This release contains lots of improvements, new features and bug fixes. The release highlights include: * Configurable key bindings, with GNU/Emacs and VisualStudio.NET key binding schemes. * Improved Makefile generation, now supporting generating makefiles which don't require Autotools. * A preview of the Localization add-in. * Text editor improvements (documents can be maximized, more editing commands available). * The designer now supports gtk# 2.8 widgets. * Improved widget toolbox. * Many bug fixes! Complete release notes are available here: http://www.monodevelop.com/Release_notes_for_MonoDevelop_0.15 Packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Mono 1.2.5
El dc 01 de 08 del 2007 a les 13:49 +0300, en/na Szentpali Janos va escriure: Is there a point in complaining (reporting) that monodevelop (included in Mono 1.2.5 preview) doesn't work on other platforms than the officially supported ones (I'm talking Zenwalk)? If it is a packaging problem (e.g. you install the package and it doesn't work at all due to missing dependencies) you should report the problem to whoever created the package. If you find bugs in when running MonoDevelop, you should report them in http://bugzilla.ximian.com. Lluis. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] Monodevelop doesn't start :(
Hi! Every dependency package I have compiled it did so without errors. There were some warnings when compiling monodevelop about variables being declared and not being used. Don't know if it is important, but the gnome-sharp package was not compiled (but installed from a Slack package) because I couldn't find a source for the gnome-sharp-devel package. I couldn't find the sources for any -devel package for that matter. In fact it was very hard to track down the sources for every dependency when compiling mono and monodevelop from source :(. I mean my impression was that mono but especially monodevelop is ment to be used only by people using Ubuntu, SUSE, Debian and Red Hat :(. Is there a repository where one could find the sources for the dependencies too? I would like to compile everything, again, from source but from the same source. As it is now I gathered dependencies from various places. Maybe that is the problem :-?. This might be the source of the problem. Make sure that gnome-sharp and gtkhtml-sharp are properly installed in the GAC. If they are, make sure the versions ob those assemblies installed in the GAC are the same as the ones used to compile MD. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Monodevelop doesn't start :(
El dv 27 de 07 del 2007 a les 17:31 +0300, en/na Szentpali Janos va escriure: Lluis Sanchez wrote: Hi! Every dependency package I have compiled it did so without errors. There were some warnings when compiling monodevelop about variables being declared and not being used. Don't know if it is important, but the gnome-sharp package was not compiled (but installed from a Slack package) because I couldn't find a source for the gnome-sharp-devel package. I couldn't find the sources for any -devel package for that matter. In fact it was very hard to track down the sources for every dependency when compiling mono and monodevelop from source :(. I mean my impression was that mono but especially monodevelop is ment to be used only by people using Ubuntu, SUSE, Debian and Red Hat :(. Is there a repository where one could find the sources for the dependencies too? I would like to compile everything, again, from source but from the same source. As it is now I gathered dependencies from various places. Maybe that is the problem :-?. This might be the source of the problem. Make sure that gnome-sharp and gtkhtml-sharp are properly installed in the GAC. If they are, make sure the versions ob those assemblies installed in the GAC are the same as the ones used to compile MD. Lluis. Hi! Any idea where can I find the source for the !!! -devel !!! packages? My distro is not GNOME based and it doesn't come with the devel packages. I can't find them anywhere on the internet. Sorry, I don't know. The packages that are on the mono-project site do not contain such things and as such mono doesn't compile at all :(. Thank you for the advice! János ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Monodevelop doesn't start :(
Thanks for the reply ... I have checked my configurations; check your Xml manifest. For example for the Monodevelop.MonoQyery: /usr/monodevelop/AddIns/MonoQuery and open the xml file. The Extensionpoints are part of the DLL files which are imported as assembly in the beginning of the file (well I think they are if I think logically :-) ) ... If the extensionpoint can not be traced, than perhaps the DLL-files which are imported aren't correctly compiled. You can try by removing the extensionline (be sure to make a copy of the original first ;-) That won't fix the problem. The problem is that the add-in scanner fails to scan the add-in that defines those extension points. But I don't know yet why it fails. Let me know ... Best regards .. Danny ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Monodevelop doesn't start :(
Hi, Which distro do you use? How did you install MonoDevelop? is it from a package? did you compile it yourself? Which Mono version do you have? Lluis. El dj 26 de 07 del 2007 a les 20:22 +0300, en/na =?UTF-8?Q?Szentp=E1li_J=E1nos?= va escriure: Hi! Thank you for the help, but it didn't... help :D. I did what you said, but the same result. Maybe I should add that when I run monodevelop for the first time it gives a lot of messages like this (but only right after the compilation on first run): --- START --- ... Warning: The add-in 'Monodevelop.CSharpBinding,0.14.0' is trying to extend '/MonoDevelop/FileTemplates', but there isn't any add-in defining this extension point ... Warning: The add-in 'Monodevelop.MonoQuery,0.6.0' is trying to extend '/SharpDevelop/Workbench/Pads', but there isn't any add-in defining this extension point ... --- END --- Any idea what I am not doing right (maybe when compiling some other component)? János Jeffrey Stedfast wrote: rm -rf $prefix/lib/monodevelop and then do another make install afaik, this means that you have old data still in that directory and md gets confused. Jeff On Wed, 2007-07-25 at 14:22 +0300, =?UTF-8?Q?Szentp=E1li_J=E1nos?= wrote: When I try to start monodevelop I get the following error (of course the app quits instantly): --- START --- Unhandled Exception: Mono.Addins.Setup.InstallException: Application not found: IDE at MonoDevelop.Core.ApplicationService.StartApplication (System.String appId, System.String[] parameters) [0x0] at MonoDevelop.Startup.SharpDevelopMain.Main (System.String[] args) [0x0] --- END --- My questions: - does anyone know what is going on? - how can I make it not complain about MOZILLA_FIVE_HOME... for I have no Mozilla installed and I don't intend to. I currently set it to '/' János ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Mono.Addins-0.2 uses {gnome, gtk}-sharp-2.0 even with --disable-gui
El dl 09 de 07 del 2007 a les 19:34 +0200, en/na Jurek Bartuszek va
escriure:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
there seems to be a problem with Mono.Addins: even if I explicitly pass
- --disable-gui to configure script, {gnome,gtk}-sharp libraries are still
being referred to during make:
I fixed it in SVN. Thanks for reporting the problem.
Lluis.
___
Mono-list maillist - Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] ANNOUNCE: Mono.Addins 0.2
Hi, I'm pleased to announce the release of Mono.Addins 0.2. Mono.Addins is a generic framework for creating extensible applications, and for creating libraries which extend those applications. The 0.2 release comes with many bug fixes and some improvements and new features: * Assemblies registered in the GAC can now be referenced from .addins files (http://www.mono-project.com/Mono.Addins_Reference_Manual#Add-ins_in_the_GAC). * Add-ins now have a private data path which can be used by extensions to store arbitrary data files at run time (http://www.mono-project.com/Mono.Addins_Reference_Manual#The_private_data_directory). * Added support for add-ins which are disabled by default. * The core library no longer depends on Mono.Posix. * The assemblies are now signed. * Several improvements in the classes of the Mono.Addins.Description namespace. * Added support for getting resource strings and resource objects from extension nodes. If you are interested in knowing more about Mono.Addins, take a look at http://www.mono-project.com/Mono.Addins. You can download a tarball from: http://www.go-mono.com/sources/mono-addins/mono-addins-0.2.tar.gz Latest from SVN at: svn://anonsvn.mono-project.com/source/trunk/mono-addins Enjoy! Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Philosophical Question - Why .NET on UNIX?
Hi, No offense, but what I thought when I read your mail and your first reply to Alan is that you had no clue about what .NET/Mono is and how it works. I guess that the other people that replied had the same feeling. If you find the answers obvious, then you clearly failed in explaining your message. Let me summarize some of the statements you made that lead me to believe your lack of knowledge of .NET/Mono: What I don't understand is why MONO just *followed* Microsoft down the questionable path of Java. A principal purpose of .Net of course was to defeat Java because Microsoft was losing so many developers to Java, but not because Java was better than other object oriented alternatives such as Delphi or C++Builder My conclusion here was that you didn't know what the Mono project was about. The Mono community *do* believe in the path initiated by Java and later improved by Microsoft (that is, in a managed, language agnostic, portable, object oriented development platform). That's why the Mono project was created. The question of why Mono just *followed* Microsoft doesn't make any sense, since Mono *is* an implementation of Microsoft .NET, for the good and for the bad (of course Mono is not only MS.NET. We embraced, and we extended it). Another reason I believe Microsoft followed Java is that Microsoft doesn't want to abandon it's greatest security risk -- ActiveX -- and, that because they will not do that, they will never understand how to build a secure OS. What sense does it make then for UNIX/Linux to follow this path (...) Adhering to a concept of transmitting only data between web applications wholly eliminates the need to follow the COM/ActiveX pattern My conclusion after those statements is that you have a great confusion, because you are talking about technologies which are not related at all with Mono. Mono has no relation at all with COM/ActiveX. So the question What sense does it make then for UNIX/Linux to follow this path does not make any sense by itself. Assumably, abstracting support for the .Net libraries within an equivalent .Net environment running on Linux/UNIX is approximately the same thing as reorganizing that support so .Net code runs *NATIVE* on Linux/UNIX. In other words, the overhead of supporting native .Net executables running far faster than Windows counterparts running as IL is theoretically little different: Libraries, and their relationship to a compiler, are simply organized somewhat differently. (...) Thus if engineers working with .Net implementations originally intended for Windows .Net could run the same code base, or even a restricted code base or roughly similar code base, as native executables on Linux/UNIX, obviously *that* is a place we *really* want to go today. My first reaction after reading this was to think that you didn't know .NET/Mono compiles IL into native code on the fly, and that there are tools which can convert portable assemblies to native libraries. The sentence running far faster than Windows counterparts running as IL was specially misleading, as IL is never interpreted, but compiled to native code. In fact, when you install .NET on windows, all assemblies of the framework are compiled no native libraries. Maybe you already know all this, but everybody reading that paragraph will believe the contrary. One obvious security vulnerability (assumably of all .Net implementations, because all implementations generate IL), is that the very IL will regularly pave the way to security breaches. Likewise, IL makes it very difficult if not impractical to protect intellectual property. (...) The .Net environment imposes relatively basic security measures. Yet keys can be stolen, signatures can be impersonated, new assemblies can be distributed to impersonate others... etc.. You don't say it, but I assumed here that IL will regularly pave the way to security breaches because it is easy to decompile. It made me smile because you are using the same argument that some people use to attack open source, saying that it is less secure because everybody can read the code. I know that not all code is meant to be read by people, but it made me smile anyway. You then talked about keys being stolen, signature impersonation and so on. This seemed a really poor argument to me, since those security technologies are not specific of .NET, but they are used everywhere. If you don't rely on keys, signatures and certificates, you should stop using SSL, SSH, GPG and many other technologies. All this also made me believe that you didn't know what is CAS, and how it can help running untrusted code in a secure way. Well thanks for the tip, but imho, managed is quite an overstated virtue or advantage. (...) What is the ostensible advantage of ForEach? Underneath your call to ForEach is an iterative process which has to make the well known, routine call to iterate count minus 1. The same thing has to be done. There's nothing
[Mono-list] MonoDevelop 0.14 released
The MonoDevelop team is proud to announce the release of MonoDevelop 0.14. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages. This release contains lots of improvements, new features and bug fixes. The release highlights include: * A new packaging system, which simplifies the process of generating tarballs or other packages. * New code refactory commands (rename, implement interface, encapsulate field). * Improved support for smart indent of C# code. * New command for converting/exporting projects. Complete release notes are available here: http://www.monodevelop.com/Release_notes_for_MonoDevelop_0.14 Packages are available here: http://www.monodevelop.com/Download Enjoy! ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] MonoDevelop 0.14 released // exception after update on FC6
El dc 13 de 06 del 2007 a les 19:37 +0400, en/na Maxim Karavaev va escriure: Thanks a lot for this great IDE! You are doing great work! But I've got got strange exception after updating version 0.13 to 0.14 via yum on Fedora Core 6. #monodevelop Unhandled Exception: Mono.Addins.Setup.InstallException: Application not found: IDE at MonoDevelop.Core.ApplicationService.StartApplication (System.String appId, System.String[] parameters) [0x0] at MonoDevelop.Startup.SharpDevelopMain.Main (System.String[] args) [0x0] This error may be due to some conflict with old assemblies. Try deleting the directory ~/.config/MonoDevelop/addin-db-000 and starting monodevelop again from a terminal. This may fix the problem or show a more specific error message. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] MonoDevelop 0.14 released // exception after updateon FC6
El dc 13 de 06 del 2007 a les 21:39 +0400, en/na Maxim Karavaev va escriure: Hello, This error may be due to some conflict with old assemblies. Try deleting the directory ~/.config/MonoDevelop/addin-db-000 and starting monodevelop again from a terminal. This may fix the problem or show a more specific error message. Should we add a system to catch these kind of conditions? My system is Fedora Core 6 i386, Mono 1.2.4 just updated via yum. Widespread configuration. I should notice only one moment. After installing FC6 on computer, I've tryed to update integrated in FC mono via yum using repo from mono-project web-site. But yum told something like this: Already installed packages are newer than reqursted. After in I've downloaded all mono rpms from web-site and updated it in --force mode. After this operation everything works fine, including next updates via yum. This inconvenience presents in FC5 too. By the way, have anyone any ideas how to avoid this exception after updating MonoDevelop to 0.14? Are you need additional info from me? All I can say is that something seems to be wrong in your setup. Try uninstalling MD, make sure the /usr/lib/monodevelop and ~/.config/MonoDevelop directories are deleted, and install MD again. Maxim Karavaev ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] newbie:installing monodevelop
When you are building a project from source code and you get a 'package not installed' error, and you are pretty sure that package is installed, the most probable cause of the error is that you may need to install the corresponding -devel package. In this case mono-devel. Lluis. El dt 12 de 06 del 2007 a les 05:46 +, en/na rupanu pal va escriure: hello , I am still confused !! I don't understand why monodevelop package wants mintor is it a package i have to install?Here I paste the snippet dump from my terminal screen...Please have a look at it and tell me what's the issue..Thanking in advance.. rupanu /***terminal***/ linux:~ # mono --version Mono JIT compiler version 1.2.4 (tarball) Copyright (C) 2002-2007 Novell, Inc and Contributors. www.mono-project.com TLS: __thread GC:Included Boehm (with typed GC) SIGSEGV: normal Architecture: x86 Disabled: none linux:~ # cd monodevelop-0.13.1/ linux:~/monodevelop-0.13.1 # ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking how to create a ustar tar archive... gnutar checking whether to enable maintainer-specific portions of Makefiles... no checking for intltool = 0.25... 0.33 found checking for perl... /usr/bin/perl checking for XML::Parser... ok checking for iconv... /usr/bin/iconv checking for msgfmt... /usr/bin/msgfmt checking for msgmerge... msgmerge checking for xgettext... xgettext checking for mono... /usr/local/bin/mono checking for gmcs... /usr/local/bin/gmcs checking for update-mime-database... /usr/bin/update-mime-database checking for update-desktop-database... /opt/gnome/bin/update-desktop-database checking for pkg-config... /usr/bin/pkg-config checking for mono = 1.1.10... checking for mint = 1.1.10... configure: error: Please install mono version 1.1.10 or later to install MonoDevelop. Please see http://www.mono-project.org/ to download latest mono sources or packages linux:~/monodevelop-0.13.1 # // office 07 ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Subversion on MonoDevelop
El dv 25 de 05 del 2007 a les 08:04 -0400, en/na Vladimir Giszpenc va escriure: Hi, The subversion add-in has made my MonoDevelop experience nice and smooth. Yesterday, it hit a slight bump when my subversion server certificate expired. SVN from the command line was able to get a nice message: Error validating server certificate for 'https://myhost.myserver.com:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! - The certificate hostname does not match. - The certificate has expired. Certificate information: - Hostname: myhost - Valid: from Tue, 23 May 2006 18:24:13 GMT until Wed, 23 May 2007 18:24:13 GMT - Issuer: IT, My Company, Eatontown, New Jersey, US - Fingerprint: 72:06:72:f4:68:7f:63:e1:f2:93:35:58:df:d4:d5:0f:a1:3b:68:0b (R)eject, accept (t)emporarily or accept (p)ermanently? Is there any way to make the GUI client capable of displaying a similar message? This message is displayed by SSH, and there is no way MD can intercept/replace it. If you are starting MD from a desktop shortcut, the MD process won't have a terminal bound to it and SSH will display a window with the message in this case. The application to run when a prompt has to be shown can be specified in the SSH_ASKPASS env var (set to x11-ssh-askpass by default). But if you start MD from a terminal, SSH will ignore SSH_ASKPASS and will always show prompts in that terminal. AFAIK, there is no way to change this behavior. Thanks, Vlad PS While I am on the subject of Subversion, why is the diff window not editable? Why should it be editable? What should allow you to edit? or do you mean 'selectable'? Lluis. PS: Sigh, I really hate when people ask 'why is feature not implemented' on an open source project. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] Glade Interface Designer and MonoDevelop
El ds 19 de 05 del 2007 a les 17:39 -0600, en/na John Meyer va escriure: I'm getting into developing with mono and I'm having a bit of a time figuring out how the tools relate to each other. Specifically, in terms of GID and MonoDevelop, I'm getting the idea that I do something like this 1. Open GID and design the interface there 2. Save the interface 3. Open up MonoDevelop 4. Create a new project based in the directory that I saved the GID files in. 5. Pull in the interfaces and write the code there. Am I completely off, or just a little off? You don't need to use Glade when developing with MonoDevelop, as it has its own integrated GUI designer. If you really need to use Glade, just create your project in MD and add to it your .glade file as a resource. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] MonoDevelop and Nemerle
Hi, The Nemerle add-in is kind of abandoned right now since it has not been updated by the author for several months, and it depends on a specific Nemerle svn revision. I don't think this situation won't change unless somebody from the Nemerle community takes on the add-in and finishes it. Lluis. El dj 17 de 05 del 2007 a les 05:16 -0300, en/na J. Pablo Fernández va escriure: Hello Stojance, Thank you for your reply. I hope you don't mind that I am posting back to the mono list. I am hoping someone may read this and give some hints. On Wed, 2007-05-16 at 19:04 +0200, Stojance Dimitrovski wrote: On Tue, 2007-05-15 at 16:26 -0300, J. Pablo Fernández wrote: I am running Ubuntu, I've installed Mono from the official install from the web-site to have the lattest MonoDevelop, yet it doesn't offer a way to create a Nemerle project. What path should I take to play with Nemerle on Monodevelop? Install Nemerle from sources and then Monodevelop from sources enabling Nemerle? Hi! I had this problem too... not that it's a problem. :-) When you run configure, pass the argument: --enable-nemerle Already passing --enable-nermerle. But, you should have the very, very latest Nemerle. Probably compiled from SVN. Well, here's the problem. Monodevelop expects nemerle = 0.9.3.99. Latest stable is 0.9.3, so it is not enough. Surprisingly, SVN trunk identifies as 0.9.3 as well. So although it may be enough, it isn't. Only the snapshots are 0.9.3.99. where is some kind of index always incrementing by one. The next step is obvious, go grab the latest snapshot and play with it. I did that several times always getting one of these problems: - Nemerle didn't compile. Probably instability that can be expected of snapshots. - Monodevelop didn't compile *if* --enable-nemerle was passed. Possibly incompatibilities between Monodevelop and the latest Nemerle at that time. I bet there are some snapshots that work and some that doesn't. If anybody knows a bit more about this, I'll be grateful if that information is shared. Thank you. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] COM Interop Remoting Patch
Hello,
Attached is a patch to fix remoting involving COM Interop types.
I had previsouly broken this unintentionally. COM Interop uses
transparent proxies, and there was lots of places that didn't
distinguish between a remoting transparent proxy and a COM Interop
transparent proxy. To distinguish I check to see if the real proxy
associated with the transparent proxy is a COM Interop proxy.
The main cases I needed to handle was the casting of transparent proxy
objects, method calls, and field access. For the casting of
transparent proxies, I added a new field to the MonoRemoteClass for
the COM Interop vtable. I was previously overwriting the
default_vtable. For method calls, and probably the most important
thing to notice, is that I added another check to
mono_marshal_get_remoting_invoke_with_check to see if a transparent
proxy is used for COM Interop. This does add some overhead to
remoting; the overhead should always be emitting a method that simply
loads all the arguments and calls the wrapped method on the underlying
managed object the proxy wraps. No real COM Interop code or
marshalling code should unless the type has a ComImport attribute.
Unless COM is used the method should never be called, only emitted.
The field access was done via checks in mono_load_remote_field,
mono_load_remote_field_new, mono_store_remote_field, and
mono_store_remote_field_new. This avoids emitting any additional
checks or methods for remoting wrappers.
Please make any suggestions if my changes could be done in a better
way; especially if my changes related to methods should be more like
the ones for fields, or vice versa.
The patch looks in general ok to me. I only have a couple of comments:
Index: mono/mono/metadata/object.c
===
--- mono/mono/metadata/object.c (revision 75279)
+++ mono/mono/metadata/object.c (working copy)
@@ -2589,6 +2598,15 @@
return obj;
} else {
/* obj must be already unboxed if needed */
+ if (obj mono_object_class(obj) ==
mono_defaults.transparent_proxy_class) {
+ /* Get wrapper method if object is a
transparent proxy for com interop.
+* There was no check here for a remoting
transparent proxy, so I assume that case does
+* not happen...
+*/
This branch of the condition is executed when calling a method which is
not a constructor. I think that it does happen for remote methods, so it
would be good to really check it. Maybe you are adding this com check in
the wrong place.
+ MonoTransparentProxy* transparent_proxy =
(MonoTransparentProxy*)obj;
+ if
(transparent_proxy-rp-object.vtable-klass ==
mono_defaults.com_interop_proxy_class)
+ method =
mono_marshal_get_cominterop_invoke (method-slot == -1 ? method :
method-klass-vtable [method-slot]);
+ }
return mono_runtime_invoke (method, obj, pa, exc);
}
}
@@ -4103,8 +4121,12 @@
}
if (target target-vtable-klass ==
mono_defaults.transparent_proxy_class) {
+ MonoTransparentProxy* transparent_proxy =
(MonoTransparentProxy*)target;
g_assert (method);
- method = mono_marshal_get_remoting_invoke (method);
+ if (transparent_proxy-rp-object.vtable-klass ==
mono_defaults.com_interop_proxy_class)
+ method = mono_marshal_get_cominterop_invoke
(method);
+ else
+ method = mono_marshal_get_remoting_invoke
(method);
Since this check is done in several places, maybe it would be good to
introduce a new method which takes the proxy and the method as
parameters, and returns the correct wrapper method depending on the
proxy type.
delegate-method_ptr = mono_compile_method (method);
MONO_OBJECT_SETREF (delegate, target, target);
} else if (mono_method_signature (method)-hasthis
method-klass-valuetype) {
@@ -4284,6 +4306,12 @@
g_assert (this-vtable-klass ==
mono_defaults.transparent_proxy_class);
g_assert (res != NULL);
+ if (tp-rp-object.vtable-klass ==
mono_defaults.com_interop_proxy_class) {
Would it make sense to define a macro for checking if a transparent
proxy is a com object? it is being used in several places.
Thanks,
Lluis.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] System.Runtime.Remoting.RemotingConfiguration Configure Patch
Please commit. Thanks! Lluis. El dc 02 de 05 del 2007 a les 13:52 -0400, en/na Jonathan Chambers va escriure: Hello, Attached is patch to add 2.0 overload of Configure method in System.Runtime.Remoting.RemotingConfiguration. This was done the same way as System.Runtime.Remoting.Channels.ChannelServices.RegisterChannel. Thanks, Jonathan ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] ANNOUNCE: Mono.Addins 0.1
El dt 27 de 03 del 2007 a les 01:44 +0200, en/na Antonello Provenzano va escriure: Lluis, I'm not directly interested in contributing to the project (I'm still figuring me out how to implement LINQ support), but a friend of mine (Matthijs) has been working on a similar project called NApf since before MS published AddIn support in the 3.5. You should think about it. There are some similarities between Mono.Addins and NApf, although the focus is different. Mono.Addins is just an add-in engine. It intends to be as small as possible, and avoids imposing an architecture on the host application. All the effort has been focused in building an add-in engine which is fast, memory efficient and scalable (a host can efficiently handle thousands of add-ins). On the other hand NApf is more focused on building an application framework. It has an add-in engine similar to Mono.Addins (since it is based on the SharpDevelop engine), although it isn't probably as optimized as Mono.Adidns (it's just a guess, since I haven't analyzed the code). In addition to add-in engine it offers other modules for managing settings, logging, and other high level UI components. That's not covered in Mono.Addins and never will. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] ANNOUNCE: Mono.Addins 0.1
El dt 27 de 03 del 2007 a les 14:15 +0200, en/na Matthijs ter Woord va escriure: Hi Lluis, On the other hand NApf is more focused on building an application framework. It has an add-in engine similar to Mono.Addins (since it is based on the SharpDevelop engine), although it isn't probably as optimized as Mono.Adidns (it's just a guess, since I haven't analyzed the code). In addition to add-in engine it offers other modules for managing settings, logging, and other high level UI components. That's not covered in Mono.Addins and never will. NApf's modules are just addins providing you with basic/standard functionality common in many applications. Maybe we should have a chat once, about how different NApf's core (the actual addin engine) is with Mono.AddIns, so we can maybe share ideas/merge or what ever. Is this something you would be interested in? Sure, pretty much. I'll take a more detailed look at the NApfs code to see the main differences. Lluis. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
