I suggest you ...

MyExtensions folder (multiple queries). Alternatively: support query to query reference.

LINQPad is growing within my organization.Domain experts are becoming seasoned programmers. However, several projects have started getting very large communal "MyExtensions". This is facing the normal problem of readability, volatility/stability, concurrent work and versioning. It is also an opportunity lost to teach good separation of concerns.

It would be very helpful (and educational) if MyExtensions could be separated into several files, each of which would be "C# program" and concatenated (minus the main() method) in the pre-build step.

Alternatively, it would be even better if a query could reference another query in the same fashion that all queries now refers to "MyExtensions".
The tendency I am witnessing is that each domain/team effort comes with its own "MyExtensions". Even if we could separate this into multiple files, it still draws a lot of dependencies even for lightweight queries.

The combination of LINQPad and git would be even more powerful and scale much better even when efforts starts to resemble medium size development projects.
It would be easy to create a query which visualized the resulting dependency graph and LINQPad would be a great introduction to software architecture.

6 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Tormod Steinsholt shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base