You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's related to #244
How do I debug TPDTC external assemblies loading failures when type provider triggered from .NET SDK command line?
Usual type provider technique invoking one VS instance from another simply doesn't work because VS uses it's own F# compiler and things are fine.
I tried
Invoke dotnet ... as debug target
Debugger.Break()
printf
Nothing worked.
So I had to go with a low-tech solution writing to file from AsserblyResolve event which is ok-ish but I wonder if there is a better way.
The text was updated successfully, but these errors were encountered:
Capture output of msbuild -v:n or msbuild -v:d in args.txt and trim out the rubbish leaving just the command line arguments to the F# compiler, usually starting with -o:
It's related to #244
How do I debug TPDTC external assemblies loading failures when type provider triggered from .NET SDK command line?
Usual type provider technique invoking one VS instance from another simply doesn't work because VS uses it's own F# compiler and things are fine.
I tried
dotnet ...
as debug targetDebugger.Break()
printf
Nothing worked.
So I had to go with a low-tech solution writing to file from
AsserblyResolve
event which is ok-ish but I wonder if there is a better way.The text was updated successfully, but these errors were encountered: