Windows 10: migration from netcore2.2 to netcore3.0 problems

Hi, I follow the guide on line for migration of project in netcore2.2 to netcore3.3

I have IdentityServer too.

but I have different problems so I put my startup.cs

I have this project, in web is my web application that doesn't use razor. AppDB is class DB in AuthProvider there is IdentityServer

Startup.cs of web is





using Microsoft.AspNetCore.Builder;

using Microsoft.AspNetCore.Hosting;

using Microsoft.EntityFrameworkCore;

using Microsoft.Extensions.Configuration;

using Microsoft.Extensions.DependencyInjection;

using System.IO;

using Microsoft.IdentityModel.Tokens;

using Microsoft.AspNetCore.Authorization;

using Newtonsoft.Json;

using KSM.Database.AppDB.Models;

using KSM.IdentityProvider.Interface;

using KSM.IdentityProvider;

using Microsoft.AspNetCore.Mvc.Authorization;

using KSM.Web.Helpers;

using System.Security.Claims;

using Microsoft.AspNetCore.Http.Features;

using System;

using KSM.AuditProvider;

using Microsoft.Extensions.FileProviders;

using Microsoft.AspNetCore.Http;

using Microsoft.AspNetCore.Mvc;

using Microsoft.Extensions.Logging;

using KSM.AuthProvider;

using Microsoft.Extensions.Hosting;







namespace KSM.Web

{

public class Startup

{

//startup

public StartupIConfiguration configuration

{

Configuration = configuration;

}



public IConfiguration Configuration { get; }



public void ConfigureServicesIServiceCollection services

{



services.AddControllersWithViews;

services.Configure<CookiePolicyOptions>options =>

{

// This lambda determines whether user consent for non-essential cookies is needed for a given request.

options.CheckConsentNeeded = context => true;

options.MinimumSameSitePolicy = SameSiteMode.None;

};



//services.AddMvc

// .SetCompatibilityVersionCompatibilityVersion.Version_3_0;



services.Configure<KSMConfiguration>Configuration.GetSection"Configuration";



services.AddTransient<IKSMIdentityProvider, KSMIdentityProvider>;

services.AddTransient<KSMAuditProvider>;






//***************************************************************************************************

//ADDED ALX

services.AddCorsoptions =>

{

options.AddPolicy"AllowAll", p =>

{

p.AllowAnyOrigin

.AllowAnyMethod

.AllowAnyHeader;

};

};



services.AddMvcoptions => options.Filters.Addnew AuthorizeFilternew AuthorizationPolicyBuilder.RequireAuthenticatedUser.Build

.AddJsonOptionsoptions =>

{

//// options.JsonSerializerOptions.DefaultBufferSize = default;

//// options.JsonSerializerOptions.ReadCommentHandling = System.Text.Json.JsonCommentHandling.Allow;

options.JsonSerializerOptions.IgnoreNullValues = true;



//options.SerializerSettings.DefaultValueHandling = DefaultValueHandling.Include;

//options.SerializerSettings.NullValueHandling = NullValueHandling.Ignore;

};



services.AddAuthorizationoptions =>

{



options.AddPolicy"SINGLESESSION", policy =>

{

policy.Requirements.Addnew SingleSessionRequirement;

};

options.AddPolicy"CORPORATE", policyBuilder =>

{

policyBuilder.RequireAuthenticatedUser

.RequireAssertioncontext => context.User.HasClaimClaimTypes.Role, "CORPORATE"

.Build;

};

options.AddPolicy"INSTALLER", policyBuilder =>

{

policyBuilder.RequireAuthenticatedUser

.RequireAssertioncontext => context.User.HasClaimClaimTypes.Role, "INSTALLER"

.Build;

};

options.AddPolicy"OPERATOR", policyBuilder =>

{

policyBuilder.RequireAuthenticatedUser

.RequireAssertioncontext => context.User.HasClaimClaimTypes.Role, "OPERATOR"

.Build;

};

options.AddPolicy"SYSTEMUSER", policyBuilder =>

{

policyBuilder.RequireAuthenticatedUser

.RequireAssertioncontext => context.User.HasClaimClaimTypes.Role, "SYSTEMUSER"

.Build;

};

options.AddPolicy"SUPERUSER", policyBuilder =>

{

policyBuilder.RequireAuthenticatedUser

.RequireAssertioncontext => context.User.HasClaimClaimTypes.Role, "SUPERUSER"

.Build;

};

};





KSMConfiguration configuration = new KSMConfiguration;

Configuration.GetSection"Configuration".Bindconfiguration;

services.Configure<FormOptions>options =>

{

options.MemoryBufferThreshold = Int32.MaxValue;

options.MultipartBodyLengthLimit = Int32.MaxValue;

};

string connectionString = Configuration.GetConnectionString"DefaultConnection";

//services.AddDbContext<DBPLATFORMContext>options => options.UseSqlServerconnectionString;



services.AddDbContext<DBPLATFORMContext>options =>

{

options.UseSqlServerconnectionString,

sqlServerOptionsAction: sqlOptions =>

{

sqlOptions.EnableRetryOnFailuremaxRetryCount: 5,

maxRetryDelay: TimeSpan.FromSeconds30,

errorNumbersToAdd: null;

};

};





services.AddAuthenticationKSMAuthenticationHelper.CookieSchema

.AddCookieKSMAuthenticationHelper.CookieSchema, options =>

{

options.AccessDeniedPath = "/Login";

options.SlidingExpiration = true;

options.LoginPath = "/Login";

}

.AddJwtBearer"KSMApi", options =>

{

options.Authority = configuration.AuthorityHostURL;

options.Audience = "KSMApi";

options.RequireHttpsMetadata = true;

//options.RequireHttpsMetadata = false;

//options.SaveToken = true;



options.TokenValidationParameters = new TokenValidationParameters

{

ValidateIssuer = true,

ValidateAudience = true,

ValidAudience = "KSMApi"

};

options.BackchannelHttpHandler = new KSMHttpClientHandlerconfiguration.ProxyActive, configuration.ProxyHost, configuration.ProxyPort, configuration.ProxyUsername, configuration.ProxyPassword;

};

services.AddSingleton<IAuthorizationHandler, SingleSessionHandler>;

services.AddLoggingbuilder => builder.AddConsole;




}



public void ConfigureIApplicationBuilder app, IWebHostEnvironment env

{



app.UseBrowserLink;

app.UseDeveloperExceptionPage;

app.UseDatabaseErrorPage;



app.UseRouting;

app.UseDefaultFiles;

app.UseAuthentication;

app.UseStaticFiles;

app.UseEndpointsendpoints =>

{

endpoints.MapControllerRoute

name: "default",

pattern: "api/{controller}/{action}"

;

};

app.Useasync context, next => {

await next;

if context.Response.StatusCode == 404 &&

!Path.HasExtensioncontext.Request.Path.Value &&

!context.Request.Path.Value.StartsWith"/api/"

{

context.Request.Path = "/index.html";

await next;

}

};

//************************

app.UseHsts;

app.UseHttpsRedirection;

app.UseCookiePolicy;

//********************************


app.UseCors"AllowAll";

// app.UseMvcWithDefaultRoute;



}

}

}



and when I lunch program from visual studio with F12 I read this error:

1. ERROR Error: Uncaught in promise: Error Error at KSMHttpClient.prototype.onCatch http://localhost:49658/main.js:16022:9 at CatchSubscriber.prototype.error http://localhost:49658/vendor.js:222859:17 at Subscriber.prototype._error http://localhost:49658/vendor.js:218920:9 at Subscriber.prototype.error http://localhost:49658/vendor.js:218900:13 at onLoad http://localhost:49658/vendor.js:85664:17 at ZoneDelegate.prototype.invokeTask http://localhost:49658/polyfills.js:9854:13 at onInvokeTask http://localhost:49658/vendor.js:63437:17 at ZoneDelegate.prototype.invokeTask http://localhost:49658/polyfills.js:9854:13 at Zone.prototype.runTask http://localhost:49658/polyfills.js:9623:21 at ZoneTask.invokeTask http://localhost:49658/polyfills.js:9931:17
2. HTTP500: ERRORE DEL SERVER - Il server ha rilevato una condizione imprevista che ha impedito l'esecuzione della richiesta. XHRGET - http://localhost:49658/api/identity/isloggedin

:)

 

Raid 0 help

Hi all, I've followed the IRST raid installation directions and I have created myself a Raid 0 volume. Rapid storage confirms my successful migration from a system disc to a raid 0 array. I'm also able to select it as my boot device in BIOS, but what I don't understand is why it is not listed in my Drives under my computer

In fact, my computer still lists my original C: drive with the original capacity. I feel as if I've miss an important step here and I'm unsure how to proceed.

 

Intel Updates Core 2 Quad Q9550 to E-0 Stepping

We continue our Monday news list with another Intel story that brings to our attention information concerning the company and more specificly its 2.83GHz Core 2 Quad Q9550 chips that will move from the current C-1 to the newer E-0 stepping. The updated chips will start selling on August 22nd, featuring the following changes:

• New SSpec and MM numbers for the converting products
• CPUID will change from 0x10677 to 0x1067A
• Package change to Halide free package

Apart from that, the new stepping CPUs will not include any other changes. Of course, like most new stepping parts a BIOS update will be needed.


Product Change Notification 108663 - 00

Source: TechConnect Magazine

 

Windows 10 1709 System Restore problems...


That seems to be an attempt at Option 2 in the tutorial, which requires you to
a. Boot to a command prompt (Did you?)
b. You then seem to be mixing steps 3,4 and 5, thus your command is incorrect.

I suggest Option 1 is easier.

If you still have problems, please repost listing each specific step and saying which option from the tutorial you are using. Thanks.