The one I like more is the support for per-project policies. This feature has been planned for long time but other work has been delaying it. Me and Michael Hutchinson had a chance to talk quite a lot about it while I was at Boston a couple of months ago. The policies model allows setting properties at global, solution, folder and project levels. Settings such as tab width can be defined in any of those levels and will cascade down to the lower levels (where it can be overriden if required). Many settings are already available in this way, and many more will be in future releases.
Another new feature, or rather improvement, is the support for multiple frameworks. MD already had support for targeting the 1.1/2.0 CLR for quite a long time, but did not have the concept of 'target framework', which is more generic. For example, .NET 3.0 is based on the 2.0 CLR and it just includes some additional assemblies. What complicates things a bit is that Mono does not follow the .NET releases, so for example Mono 2.0 includes bits from all .NET versions. To simplify all this and to be compatible with MSBuild, it is now possible to select the target .NET framework, which includes 1.1, 2.0, 2.1 (Silverlight), 3.0 and 3.5. The project system is fully aware of the chosen target framework, so for example it won't let you reference a 3.5 project from a 3.0 project.
The source editor keeps improving in many ways. Mike Krueger has spent quite a lot of time fixing issues in code completion, which now works in many more contexts. My contribution on code completion (besides stabilization work in the parser database) is support for completion of generic types with constraints. For example, in the following class code completion is showing the Dispose method because there is a constraint forcing the generic argument to implement it:
There are other improvements, such as the new Go to File dialog I blogged about some time ago, better support for completion in ASP.NET projects, and fixes in the GTK# designer. There is still a lot of work to do, but we are getting close to 2.0.
8 comments:
Any updates on a build for OS X?
I'm also interesting on Mac OS X install package (.dmg).
Thanks a lot, congratulations for your great job!
Did I miss something or the note about the release in MonoDevelop.com is dated Feb 12, 2008, rather 2009?
It made me miss the note...
I'd also love an OS X DMG. Thanks!!
Unfortunately there still aren't any .deb packages that I could get a grip on....
This is something I don't understand: If you create a beta for a software, you probably would like many many many people to test it so I will get many bugreports so you can then bugfix more efficiently. To archive this if you created debian packages as well as packages for red hat based systems you would reach a much bigger audience!
Ok, I do not know the internal structure of the monodevelop development team, maybe there just arent the ressources to get this done, maybe creating packages is also a very lame job that nobody wants to do (I admint I completely lag the knowledge about packaging).
Well, I will patiently wait and search the net until some .deb files get available! I cannot wait to finally be able to write me some of the GUI tools I so desperately want for linux! (I simply refuse to write them in C++ because of too much hassle)
Sorry that I whine at your blog about this, but I do not know (and didnt find) some other place where I could post my frustration :-/
Subscribing to the monodevelop mailing list didnt seem the appropriate solution.
So please excuse that your blog gets to be my psychiatrists couch ;)
Oh and yes: Congratulations to the beta! Keep it up!
I have been using the 2.0 beta for two weeks and I am really impressed.
But there is one issue it's annoying me and really slows productivity: tree views default behavior. For any reason tree views on "debugger watchpoints", "debugger locals", "gui designer properties", etc. collapse when selecting another widget (when designing forms in Stetic) or when debug stepping.
It's really annoying when debugging going through all your watches and uncollapsing them to see their values. And that needs to be done each debug step!. The default behaviour should leave all watches and locals uncollapsed so you can see their values.
The same applies to properties window on Stetic. Leave them uncollapsed by default, so all properties can be viewed at a glance.
On the Mono site there is link to a demo video showing how to build a web browser using Stetic. The link is broken and I was wondering if you could point me in th direction of a copy of the video? or a how to for creating a web browser in MonoDevelop?
To archive this if you created debian packages as well as packages for red hat based systems you would reach a much bigger audience!
Term Paper Help | Thesis Help
Post a Comment