VS2005 Project support MonoDevelop now has native support for Visual Studio.NET 2005 solutions/projects. You can directly load VS2005 solutions/projects and work with them. Any changes made are written back to the project files. Currently it supports loading C# (.csproj) and VB.NET (.vbproj) projects. This support is limited to Files, References, Configurations and Compiler options. No custom msbuild tasks are supported. Limited Makefile Integration MonoDevelop now supports limited integration with Makefiles for projects. This is limited to : - Delegating build, clean and/or execute operations to Makefiles - Keeping the monodevelop project in sync with the Makefile wrt : - List of files (Code, Resources, Deployable files and Others) - List of References (only for .net projects) - This can correctly handle package references also - The addin looks in configure.in to find referenced packages (it specifically looks for PKG_CHECK_MODULE and AC_SUBST entries) It uses this to resolve references of the form $(GTK_SHARP_LIBS) Rules for Makefile variables : You can specify the makefile variable which contains the values for the various lists. The values obtained from the variable cannot have local makefile variables (they are not resolved, simply ignored). You can specify a 'prefix' which MD can remove from the value to get the usable value. Eg. for references, the values might be of the form -r:System then '-r:' should be used as the prefix. The following autoconf variables are supported : srcdir, top_srcdir, top_builddir. So, for eg. FILES = $(srcdir)/Foo.cs is valid and will be handled by the addin. These variables are supported only when a corresponding configure.in is specified in the options. Sync'ing Resources - Resource Id is appended to the resource filename if it is different from the filename (Eg. in case of a VS2005 project) Sync'ing References - Distinct variables can be specified for Package, Assembly and Project references. - Package references like -pkg:foo are supported. The addin will add all the assemblies from such a reference to the project, so you can get Code completion for them. When adding a new reference to the project which belongs to a package, the Makefile will get a package reference instead of a assembly reference. The regular expression used for parsing compiler messages (errors and warnings) can be specified by the user also. This can be useful for non-.net projects.