When running my code on a machine without Visual Studio, I get an error with the following stack trace. I searched the docs but didn't find anything regarding "Microsoft.CodeAnalysis". How can I fix this issue?
[2021-05-03 16:05:42Z] [FTL] [<s:>] WebApp failed to start.
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.CodeAnalysis, Version=2.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.
File name: 'Microsoft.CodeAnalysis, Version=2.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
at System.ModuleHandle.ResolveType(QCallModule module, Int32 typeToken, IntPtr* typeInstArgs, Int32 typeInstCount, IntPtr* methodInstArgs, Int32 methodInstCount, ObjectHandleOnStack type)
at System.ModuleHandle.ResolveTypeHandleInternal(RuntimeModule module, Int32 typeToken, RuntimeTypeHandle[] typeInstantiationContext, RuntimeTypeHandle[] methodInstantiationContext)
at System.Reflection.RuntimeModule.ResolveType(Int32 metadataToken, Type[] genericTypeArguments, Type[] genericMethodArguments)
at System.Reflection.CustomAttribute.FilterCustomAttributeRecord(MetadataToken caCtorToken, MetadataImport& scope, RuntimeModule decoratedModule, MetadataToken decoratedToken, RuntimeType attributeFilterType, Boolean mustBeInheritable, ListBuilder`1& derivedAttributes, RuntimeType& attributeType, IRuntimeMethodInfo& ctorWithParameters, Boolean& isVarArg)
at System.Reflection.CustomAttribute.IsCustomAttributeDefined(RuntimeModule decoratedModule, Int32 decoratedMetadataToken, RuntimeType attributeFilterType, Int32 attributeCtorToken, Boolean mustBeInheritable)
at System.Reflection.CustomAttribute.IsDefined(RuntimeAssembly assembly, RuntimeType caType)
at System.Reflection.RuntimeAssembly.IsDefined(Type attributeType, Boolean inherit)
at System.Attribute.IsDefined(Assembly element, Type attributeType, Boolean inherit)
at System.Reflection.CustomAttributeExtensions.IsDefined(Assembly element, Type attributeType)
at Baseline.Reflection.ReflectionExtensions.HasAttribute[T](Assembly provider)
at Oakton.CommandFactory.<>c.<RegisterCommandsFromExtensionAssemblies>b__30_0(Assembly a)
This is a staging machine, so it should be cleaner than my local machine where it works without error. One thing I haven't considered, however, is that it is a Production build instead of Debug, which I never really tested locally. Are there any considerations when running in production?
dotnet run ... doesn't even work without the project file.
We could relax the dependency in Baseline to let it float. That could easily be the culprit
the results of dotnet publish?
Or if it writes to a dll, you can run that through
dotnet run [assembly file name]. It’s been awhile since I’ve done that, so it might be a flag of some sort
In dotnet core, dotnet run app.exe or any file produces a response like the following:
Couldn't find a project to run. Ensure a project exists in C:\code\publish\App, or pass the path to the project using --project.
From the dotnet-run docs:
The dotnet run command is used in the context of projects, not built assemblies. If you're trying to run a framework-dependent application DLL instead, you must use dotnet without a command.
Are people only using Oakton on source projects or on release builds as well?
And folks are using Oakton to run .Net Core projects in production, yes. I’ve done that as well
app.exe help should give you the help output
You wouldn’t need the double dash if you’re running from the executable instead of dotnet run
So when it says
FileNotFoundException, it’s unable to load the assembly referenced. You might try making a direct dependency to that nuget package w/ that version
Thanks.
This is super cool, this should be part of Oakton: https://andrewlock.net/viewing-overriden-configuration-values-in-aspnetcore/
After changing the standard
CreateHostBuilder(args).Build().Run() to CreateHostBuilder(args).RunOaktonCommands(args), some of the our middleware get loggers without log sinks configured. All I have to do is change to code back to fix it, so Build().Run(args) does something RunOaktonCommands(args) does not do. Any clue what that might be and whether there is a work around? It's as if Oakton doesn't call IHostBuilder.Build, but it is hard to tell.
In the Oakton codebase, do a find usages on the
NetInput.LogLevelFlag and see where it might be using that too aggressively. I’m inclined to blame Oakton’s special sauce here.
Like it may be clearing logging when it shouldn’t be.
NetCoreInput.cs line 44 would be my guess, but I'm not sure what the intent is behind the code.
I've spent a decent chunk of time on it and found that code in
NetCoreInput never has a logger value and does not do anything out of the ordinary. Something that Oakton does while loading configuration from appsettings.json interferes with how Serilog configures sinks and forces Serilog to use a SilentLogger as described by serilog/serilog#562 and shown below.
I am able to correct this by configuring Serilog with the
preserveStaticLogger: true parameter described here.
Essentially, Oakton and Serilog don't play nice together if your Serilog configuration does something fancy like load sinks from appsettings.