file-based-programs should also support assembly import

[jogibear9988]

if I look at the doc at: https://github.com/dotnet/sdk/blob/main/documentation/general/dotnet-run-file.md

the file based programs support adding nuget packages, but not other assemblies or projects. this should also be supported via #: syntax

[DamianEdwards]

We're being very deliberate about what kinds of references we want to support via the new file-level directives added to support file-based apps and right now that doesn't include referencing loose assemblies. You can workaround this limitation by specifying the reference in a Directory.Build.targets file that's in scope for the app.

[marcominerva]

@jogibear9988, there's an example of Directory.Build.targets usage in @DamianEdwards’s own repo here: https://github.com/DamianEdwards/runfile/tree/main/classlibproject.

[jogibear9988]

The purpose of the file-based-programs was I don't need a csproj, but then I need a "targets" file....
Don't think thats a good solution

[DamianEdwards]

@jogibear9988 indeed, but we do not intend for file-based apps to support all the features and scenarios that projects do. The entire point is to provide a vastly simplified experience and that by its nature is constrained and limited WRT what it can do. Supporting referencing assemblies and projects would require more directives which is more concepts. I'm not 100% ruling it out forever, just not now.

[jogibear9988]

I get this, but find it strange to support nugets but not external assemblies.

If this grews more, will c# script still also be supported?

My problem atm is, I try to replace T4 scripts with something better debuggable (cause I use a forked T4 runtime from Mono, cause the VS one does not use netcore) and thinking what to use...

[paul-hammant]

#49216 relates I think. I can't complete it after many alternate approaches to the writing of the virtual .csproj file. Could be linked "example of Directory.Build.targets" is what I need short term.

I've tried to follow that example code to do the think I'm after, but see errors. I've added an issue: DamianEdwards/runfile#1

[DamianEdwards]

We don't plan on adding first-class support for this in .NET 10 so I'm moving this to .NET 11 for consideration there.

[paul-hammant]

As I was trying many alternate strategies for a modified .csproj generation for #49216 I guessed that might be the outcome - one step at a time.