如果你对 SubSonic 有一个愿望，你会是什么？
我知道这个问题看起来很主观，但实际上非常简单。作为长期用户和 SubSonic 的兼职贡献者，我对社区认为的单一内容感兴趣改进它的最好方法。 那么你的意见是什么？你会如何让 SubSonic 变得更好？哪一件事会让您更有可能使用/推荐/传播/停止抱怨它？
正如我所说，我知道这有点主观，可能会被关闭，但由于 SO 是 SubSonic 的主要支持论坛，我认为这可能是征求意见和/或贡献的有用方法。
为了防止这变成一般性讨论，规则如下：
- 没有综合愿望
- 没有重复的愿望
- 对您同意的内容进行投票，而不是重新发布它们
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
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（9）
能够开箱即用地在 MediumTrust 中运行
Ability to run in MediumTrust out of the box
老实说，最大的缺乏是可靠的文档和 HowTo 的
它变得更好，但我认为它需要更多。
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.
能够自动映射其他对象的集合，就像 Fluent NHibernate 所做的那样。
Ability to automatically map collections of other objects, like Fluent NHibernate does.
当 SubSonic 抛出不清楚的异常时，我希望能够使用 Google 或其他一些机制来发现有关如何继续我的开发工作的更多信息。现在很容易陷入必须深入研究 SubSonic 源代码的情况，因为当用户偏离“快乐路径”时，SubSonic 似乎不太主动。
这种批评并不是针对 SubSonic 的。许多（大多数？）软件产品都遇到同样的问题。不过，我在使用 NHibernate 时并没有真正遇到过这个问题，NHibernate 是 SubSonic 最明显的竞争对手。
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
SimpleRepository 的二进制类型（图像）
Binary types for SimpleRepository (Images)
左外连接
Left Outer Joins
支持更多独立于数据库的代码生成...
我的意思是，如果您的应用程序想要与不同的数据库（例如 SQL Server 和 Oracle）通信并且您只想拥有一组生成的 DAL，那么这确实是一个真正的痛苦对象。如果您可以选择指定发送到数据库的任何 SQL 代码都尽可能与大多数引擎兼容，我会很高兴，因为现在如果您生成针对 SQL Server 的对象，那么所有查询都将采用以下形式:
SELECT [schema].[table_name] FROM ....
遗憾的是，这在 Oracle 中不起作用，所以基本上你运气不好。
也许这对你们大多数人来说并不是一个大问题，但我目前正在编写一个商业应用程序，其主要功能之一是只需更改其配置即可在各种数据库引擎上运行，我选择了 SubSonic 因为我认为它可以很容易地处理这项工作，但老实说，我现在正在重新考虑，因为我可能必须跳过所有的障碍才能让它在不同的环境下正常工作。
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.
支持 MS Access、Postgres 和 FireBird 数据库:)....
Support MS Access ,Postgres and FireBird database :)....