If you had one wish for SubSonic what would it be?

I know this question seems subjective but it's really pretty simple. As a long term user, and part time contributor to SubSonic I'm interested in what the community thinks would be the single best way to improve it. So what's your opinion, how would you make SubSonic even better? What one thing would make you more likely to use/recommend/evangelise/stop complaining about it?

As I said I know this is a bit subjective and may get closed but as SO is the main support forum for SubSonic I think this could be a useful way开发者_如何学运维 to solicit opinion and/or contributions.

To keep this from turning into a general discussion here's the rules:

• No omnibus wishes
• No duplicate wishes
• Up-vote those you agree with rather than re-posting them

---

Ability to run in MediumTrust out of the box

---

In all honesty the biggest thing thats lacking is solid documentation and HowTo's

Its got better but I think it needs a lot more.

---

Ability to automatically map collections of other objects, like Fluent NHibernate does.

---

When SubSonic throws an exception that isn't clear, I'd like to be able to use Google or some other mechanism to discover more information about how to keep my development effort moving forward. Right now it's too easy to get into a situation where you have to go spelunking into the SubSonic source code since SubSonic doesn't seem to be very proactive when the user goes off the "happy path".

This critique is hardly specific to SubSonic. Many (most?) software products suffer from this same problem. I have not really had this problem with NHibernate though, which is SubSonic's most clear competitor.

---

Faster and higher quality releases

---

Binary types for SimpleRepository (Images)

---

Left Outer Joins

---

Support more database-independent code generation...

What I mean by this is that it is truly a real pain if your application wants to talk to different databases (e.g. SQL Server and Oracle) and you want to only have one set of generated DAL objects. I would love it if you had the option of specifying that any SQL code that gets sent to the DB would be as compatible with most engines as possible, since right now if you generated your objects targeting SQL Server then all queries will be of the form:

SELECT [schema].[table_name] FROM ....

Sadly, this does not work in Oracle, so basically you're out of luck there.

Perhaps this isn't a huge concern for most of you, but I'm currently writing a commercial app that touts one of its main features as being able to run on various database engines just by changing its configuration and I chose SubSonic because I thought it could handle the job pretty easily, but I'm honestly having second thoughts now because of all the hoops I may have to jump through just to get this to work correctly under different environments.

---

Support MS Access ,Postgres and FireBird database :)....