-
-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Miniblog won't work as IIS application #40
Comments
Hi,
do you have any error or something like that?
…On Sat, Nov 18, 2017 at 9:57 AM, robalexclark ***@***.***> wrote:
I've been trying to work out what is special about the miniblog.core
routing/setup that stops it working as a IIS application (works fine when
published to a root IIS site. Miniblog is unable to find Views and css
files for example, but I'm unable to understand why ¯_(ツ)_/¯ Can anyone
help/give me some pointers? Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#40>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/APctZA-NFqajBTddWyQnCLeggUy3CWexks5s3sYlgaJpZM4Qi-mU>
.
--
Eddy Nakamura
|
ok. found the problem. i will make a pull request with that. the css paths aren't dynamic, so it will go always to root iis website. |
Yes it fails at the first css it finds (which is belowthefold.css). Thanks for looking into this for me. |
Can you send me a picture? I found other errors but I still can't reproduce yours. |
OK, the first error after publish is this (complaining about access to ob folder)j: Content root path: C:\inetpub\wwwroot\MiniBlog Sooo, I manually created an obj directory and granted write access, but still no joy as the next error encountered is: System.IO.FileNotFoundException: No files found matching "/MiniBlog/css/belowthefold.scss" exist in "C:\inetpub\wwwroot\MiniBlog\wwwroot" |
How are you generating this files?
Are you copying / pasting from source folder?
…On Sat, Nov 18, 2017 at 3:02 PM, robalexclark ***@***.***> wrote:
OK, the first error after publish is this (complaining about access to ob
folder)j:
Content root path: C:\inetpub\wwwroot\MiniBlog
Now listening on: http://localhost:33208
Application started. Press Ctrl+C to shut down.
fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[0]
An unhandled exception has occurred: Access to the path
'C:\inetpub\wwwroot\MiniBlog\obj\WebOptimizerCache' is denied.
System.UnauthorizedAccessException: Access to the path
'C:\inetpub\wwwroot\MiniBlog\obj\WebOptimizerCache' is denied.
Sooo, I manually created an obj directory and granted write access, but
still no joy as the next error encountered is:
System.IO.FileNotFoundException: No files found matching
"/MiniBlog/css/belowthefold.scss" exist in "C:\inetpub\wwwroot\MiniBlog\
wwwroot"
at WebOptimizer.Asset.ExpandGlobs(IAsset asset, IHostingEnvironment env)
at WebOptimizer.Asset.GenerateCacheKey(HttpContext context)
at WebOptimizer.Taghelpers.BaseTagHelper.GenerateHash(IAsset asset)
at WebOptimizer.Taghelpers.LinkTagHelper.Process(TagHelperContext
context, TagHelperOutput output)
at Microsoft.AspNetCore.Razor.TagHelpers.TagHelper.ProcessAsync(TagHelperContext
context, TagHelperOutput output)
at Microsoft.AspNetCore.Razor.Runtime.TagHelpers.
TagHelperRunner.d__0.MoveNext()
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APctZISjhfq4XuCxJc34ficWwvd-WN7Eks5s3w29gaJpZM4Qi-mU>
.
--
Eddy Nakamura
|
I'm turning on logging in the web.config - the output is from the stout log files. |
i think you need to do something like
https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-publish?tabs=netcore2x
when you publish it will automatically generate some files.
in my case, using windows, it generated:
[image: Inline image 1]
…On Sat, Nov 18, 2017 at 4:22 PM, robalexclark ***@***.***> wrote:
I'm turning on logging in the web.config - the output is from the stout
log files.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APctZJHtBZAK3tTkVJDey1ZV4PdHJdX7ks5s3yBigaJpZM4Qi-mU>
.
--
Eddy Nakamura
|
I've been using webdeploy to deploy to the IIS server, which runs dotnet publish then copies the output to the IIS application directory. This is the way I've been publishing other netcore 2.0 apps and they work fine. Whatever is stopping miniblog.core working as an IIS application must be due to the way it is setup/configured within the code. I did however run dotnet publish and manually copy the files but the error is the same. |
same here, look to me like this one https://github.com/ligershark/WebOptimizer/blob/master/src/WebOptimizer.Core/Asset.cs |
Did you find any solution ? |
Nope - I didn't. In the end I just rolled my own mini-blog engine, but now I'm in the process of moving all this to Medium.com |
This is really annoying. I'm thinking of going to back MVC. |
My error also different;
|
I've been trying to work out what is special about the miniblog.core routing/setup that stops it working as a IIS application (works fine when published to a root IIS site. Miniblog is unable to find Views and css files for example, but I'm unable to understand why ¯_(ツ)_/¯ Can anyone help/give me some pointers? Thanks.
The text was updated successfully, but these errors were encountered: