Developer forum

IIS or Kestrel?

Looks like you are missing a path to /Files

If you are using Kestrel, you need to ensure the filespath in the appsettings:

{
  "FilesPath": "C:\\Data\\dw9.local.dynamicweb.dk\\Files"
}

If you are in IIS you need a web.config something like this:

<?xml version="1.0" encoding="utf-8"?>

<configuration>

 <location path="." inheritInChildApplications="false">

 <system.webServer>

 <handlers>

 <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />

 </handlers>

 <aspNetCore processPath="dotnet" arguments=".\bin\Debug\net6.0\Dynamicweb.CoreUI.Host.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="inprocess">

 <environmentVariables>

 <environmentVariable name="ASPNETCORE_ENVIRONMENT" value="Development" />

 <environmentVariable name="DW_FilesPath" value="C:\Git\Swift\Swift\Files" />

 </environmentVariables>

 </aspNetCore>

 </system.webServer>

 

 </location>

</configuration>

OK, added the "environmentVariables" to web.config and got a different error. 

System.IO.DirectoryNotFoundException: E:\dw10agent\_w\2\s\Dynamicweb.CoreUI.Rendering\wwwroot\
   at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root, ExclusionFilters filters)
   at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root)
   at Microsoft.AspNetCore.Hosting.StaticWebAssets.StaticWebAssetsLoader.<>c.<UseStaticWebAssetsCore>b__1_0(String contentRoot)
   at Microsoft.AspNetCore.StaticWebAssets.ManifestStaticWebAssetFileProvider..ctor(StaticWebAssetManifest manifest, Func`2 fileProviderFactory)
   at Microsoft.AspNetCore.Hosting.StaticWebAssets.StaticWebAssetsLoader.UseStaticWebAssetsCore(IWebHostEnvironment environment, Stream manifest)
   at Microsoft.AspNetCore.Hosting.StaticWebAssets.StaticWebAssetsLoader.UseStaticWebAssets(IWebHostEnvironment environment, IConfiguration configuration)
   at Microsoft.AspNetCore.WebHost.<>c.<ConfigureWebDefaults>b__9_0(WebHostBuilderContext ctx, IConfigurationBuilder cb)
   at Microsoft.AspNetCore.Hosting.GenericWebHostBuilder.<>c__DisplayClass9_0.<ConfigureAppConfiguration>b__0(HostBuilderContext context, IConfigurationBuilder builder)
   at Microsoft.Extensions.Hosting.HostBuilder.BuildAppConfiguration()
   at Microsoft.Extensions.Hosting.HostBuilder.Build()
   at Dynamicweb.CoreUI.Host.Program.Main(String[] args) in E:\dw10agent\_w\2\s\Dynamicweb.CoreUI.Host\Program.cs:line 14

What would be your guess that "System.IO.DirectoryNotFoundException: E:\dw10agent\_w\2\s\Dynamicweb.CoreUI.Rendering\wwwroot\" means :-)

My guess is that line 14 in class "Program" in the dll Dynamicweb.CoreUI.Host expects to find a folder in that path. 

/Aki

Yes, kindof - it is the default directory for static files in asp.net core:

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/static-files?view=aspnetcore-7.0

If missing, Dynamicweb will try to create the wwwroot folder. Maybe missing write permissions for the iisuser? You can try to switch to either using kestrel (dotnet run) directly or change the iisuser to be networkSystem.

We will look into a more solid startup that will try to accomodate missing folders and files.

Are you using the latest nuget package?

No, I'm using the October Beta release. 

This is my IIS with the "wwwroot" folder. On the top folder I have set "Everyone" to Full Control (it on my local machine). Still get the "DirectoryNotFoundException: E:\dw10agent\_w\2\s\Dynamicweb.CoreUI.Rendering\wwwroot\" error. 

I have the FilesPath set in the appsettings.json

And the web.config

If I run it with "Dotnet" I get this : 

Regards / Aki

Got i working now. 

Basically just redid everything from cratch and it worked. Fantastic. :) 

Regards / Aki

Hi Nicolai,

Could you look into this please? https://stackoverflow.com/a/71085842/15136893

We had the same issue which turned out to be a & in our database password which wasn't escaped. All the runtime.json files made finding the issue more time consuming then it kind of needed it to be. After removing the runtime.json files we got the actual error and fixed it quite easily, but it took a bit more time to get there then I'd like to admit.

For those having this error; hope this helps you find to error. :-)