Base solution for your next web application

Activities of "vermis"

I see. So the problem is outside the scope of your team.

But what does this mean for my application? Will the mobile app work regarding the warnings? What can I do?

And what regarding my second question: What are the proper settings when downloading Net Zero template if I plan do build also a Mobile App? Project type: ASPNet COre & Angular and Framework .Net Core 2?

Best regards, Damir

Dear,

In the Mobile solution many Nuget references have warnings like this: Package 'modernhttpclient 2.4.2' was restored using '.NETPortable,Version=v0.0,Profile=Profile259, .NETFramework,Version=v4.6.1' instead of the project target framework '.NETStandard,Version=v2.0'. This package may not be fully compatible with your project.

Here is the image: <a class="postlink" href="https://gyazo.com/de4f962243427bcba066683c96f87330">https://gyazo.com/de4f962243427bcba066683c96f87330</a>

The projects in VS are set to .NET Standard 2.0. Everything is default as from your template.

Is this normal?

What are the proper settings when downloading Net Zero template if I plan do build also a Mobile App? Project type: ASPNet COre & Angular and Framework .Net Core 2?

Best regards, Damir

It is working now!

I think a permission problem caused the log file not being written. Whit the logs file working I saw the problem was with the connection string in the .production and staging json files.

Thank you for your help.

Best regards, Damir

I tested the whole app also with the template on .Net Framework 4.6.1 and exactly the same issue.

Best regards, Damir

Dear,

I downloaded AspNetZero template v 5.3 and got it work locally on my PC with the DB in Azure. It is working locally on my PC ( running the core app in debug mode in Visual Studio ). It is also working if you move all the source code to the server and run it there in Visual Studio. I use Swagger to login to the API and it is working.

The problem is when I deploy it to IIS. I do the deploy with Visual Studio deploy to a folder and then copy the files to IIS.

The first problem was the missing folder "plugins". I needed to create it manually on the server to get the app working. I get the Swagger page.

When I try to login on the Swagger page I am getting error 500 from API and javascript popup "Login failed!". There are no detailed errors in the API response.

The second problem is how to get the detailed errors returned from the API calls?

I tried to activate the NLog logs but also without luck on the server. Locally it is working. Attached is the Log4Net.config that I am using.

I also tried a deploy to Azure App Services to eliminate the option of a misconfiguration on my server. The same issue. First missing "Plugins" folder, then working Swagger but not possible to login.

To recap: The same app is working in Visual Studio but not deployed on IIS. The app is working but the login not. How to debug this?

Best regards, Damir

<?xml version="1.0" encoding="utf-8" ?> <log4net> <appender name="RollingFileAppender" type="log4net.Appender.RollingFileAppender" > <file value="Logs.txt" /> <appendToFile value="true" /> <rollingStyle value="Size" /> <maxSizeRollBackups value="10" /> <maximumFileSize value="10000KB" /> <staticLogFileName value="true" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%-5level %date [%-5.5thread] %-40.40logger - %message%newline" /> </layout> </appender> <root> <appender-ref ref="RollingFileAppender" /> <level value="ALL" /> </root> </log4net>

Showing 1 to 5 of 5 entries