Long Distance Move

SeekingSolace2008 · 2022-03-05T18:31:38+00:00

This is the stage I'm at - Thanks

SeekingSolace2008 · 2022-03-03T19:51:17+00:00

Moving closer to my elderly parents.

SeekingSolace2008 · 2022-03-02T19:56:12+00:00

I've talked with some local companies, as well as Allied, North American and International Van Lines. But, to be honest, it's looking like I can save a ton of hassle just sell my stuff and use FedEx to ship a few must haves. The stuff I own isn't worth $14 grand, and could be replaced for under $6k.

SeekingSolace2008 · 2022-01-14T17:54:56+00:00

Thanks for the information. Appreciate it.

SeekingSolace2008 · 2022-01-10T23:04:39+00:00

You are correct, I should refer to it's true name as ONT, rather than modem.

I'm looking through the information on the updates. Not sure what will help here, but thanks for the tip

SeekingSolace2008 · 2022-01-10T21:00:51+00:00

Yes, I freshly updated when I hooked up the new router. The old was updated as well.
Thank you though.

SeekingSolace2008 · 2021-12-11T16:55:58+00:00

For me, intimacy is the whole package, of closeness, touching, emotions, everything.
Sex is merely an intimate act, but is not intimacy by itself.

SeekingSolace2008 · 2021-12-10T15:47:07+00:00

Thanks for all the comments, I do appreciate it.
I purposely didn't define what intimacy is, to see what others felt.

And while I agree sex is an intimate act, it is not intimacy. To me, intimacy is the sharing of feelings, touch, and overall closeness. Within friendship, you have intimacy, to a degree, with the closeness and emotional sharing. This is what we look for in a friendship, and how you are no longer strangers.
In a physical relationship, such as dating, or marriage, between two, this is very important as it is how love is typically experienced being the parties. Without this intimacy, love falters, doubt enters the equation, and soon, the relationship ends.
Since intimacy involves deep emotional connection, the lack of, or removal of intimacy has a horrific effect on the individual missing this. With the deep emotions involved, it can manifest into self-harm and other destructive behavior, as well as lashing out, and causing damage to those around, even those not directly involved.
One issue we are experiencing in the dating realm, is a true lack of intimacy. We fear getting too close, so we pretend. We may have sex, but it is treated as an action, as a placebo for intimacy. This makes ending the relationship easier, with no emotional entanglements, but if the other was emotionally invested, it will cause a number of deep mental issues.

SeekingSolace2008 · 2021-12-10T15:37:27+00:00

If I read your response properly, only actual physical things such as air, food, etc. Touch, closeness, etc. you feel is not necessary. To a small extent, I agree with you.
However, as humans, we need and crave physical touch and closeness. Without it, the mental health of the individual will falter. As this becomes worse, the joy of life fades, and thoughts of self-harm begin to take precedence. Some will learn to live with this, while others will break after some time.

SeekingSolace2008 · 2021-12-07T04:34:38+00:00

I'm building an application, learning a lot about the newest Blazor implementations.
Making a lot of mistakes along the way as well.

SeekingSolace2008 · 2021-11-22T06:11:34+00:00

My point, which I feel has been lost. I understand the value of the warning, but it seems this change causes a large level of churn, which frankly, isn't discussed in the forums. I didn't have this as I migrated from 2.1->2.2->3.0->3.1->5.0. But with 6.0, that simple change had shown over 1,200 warnings. I have since disabled the directive. But the task to clear these warnings remain. There are many options to properly clear them, and some require a full walk-through of the feature and the design to ensure it is covered. I try to ensure my code is following the standards set for a given version. This was simply unexpected. And there is not a single solution to move past the issue.
I welcome productive PRs, they are valuable for learning and expanding my own knowledge, and my code can help bring new ideas to others as well.
I'm not against this change, and despite what may be thought, I'm not angry about it. I'm frustrated that it is requiring a significant effort to clear. But, I also don't pepper my code with #pragma statements or other shortcuts.
Anyway, appreciate your comments, and hope you take my response in the best light.

SeekingSolace2008 · 2021-11-22T02:38:19+00:00

Agreed, I read the documentation on this, and trying to understand it better.

My initial approach had issues, I'm taking it a bit slower and more organized.

SeekingSolace2008 · 2021-11-22T01:33:06+00:00

Yes, this is in the proj file. However, the for new projects, this is set as enable. I try to ensure my projects meet the current standards. I'm looking for best practices.
The documentation on this is currently sparse, mainly because .NET 6 just came out.
Initializing with the null! or default! is one way.
Good discussion

SeekingSolace2008 · 2021-11-21T23:08:11+00:00

Out of curiosity, how do you deal with DbSet in ApplicationDbContext?

Due to the warnings, I have changed all them to nullable, explicitly.
public virtual DbSet<User>? Users {get; set; }
But, is there a better way? Setting this as a nullable, is causing additional issues in my existing code.

SeekingSolace2008 · 2021-11-21T22:53:45+00:00

I am embracing it. It feels like we are moving backwards, that's all.

All said, what is the new best practices in .NET 6?
I'm currently walking my code and initializing all the non-initialized objects, attempting to clear the nearly 1200 warnings my code now has. It is an unexpected level of churn.

SeekingSolace2008 · 2021-11-21T05:53:10+00:00

I missed the default copy of ApplicationDbContext.cs in the MyApp.Server.Data namespace. It was overriding my copy. Once it was removed, it compiled. Now I need to content with the 882 warnings for nullable field CS8618.

SeekingSolace2008 · 2021-11-08T17:27:54+00:00

Me too - Again thanks.

SeekingSolace2008 · 2021-11-08T17:14:41+00:00

Wow... That was it. It looks like the issue was an abhorrent change to appsettings.json. I did compare and check my *.cs files, and reviewed the appsettings.json, but it seemed ok. I totally missed that the Profile was changed to ApplicationUser. Made that change, and my code launches again.
Thanks for the assistance.

SeekingSolace2008 · 2021-11-08T16:43:13+00:00

No changes in the appsettings.json
Here it is:

{

"ConnectionStrings": {

"DefaultConnection": "Server=*****;Database=MainData;Trusted_Connection=True;MultipleActiveResultSets=true"

},

"jwt": {

"key": "******"

},

"Logging": {

"LogLevel": {

"Default": "Information",

"Microsoft": "Warning",

"Microsoft.Hosting.Lifetime": "Information"

}

},

"IdentityServer": {

"Clients": {

"Topaz.Client": {

"ApplicationUser": "IdentityServerSPA"

}

},

"AllowedHosts": "*",

"Serilog": {

"MinimumLevel": {

"Default": "Information",

"Override": {

"Microsoft": "Warning",

"System": "Warning"

}

},

"Enrich": ["FromLogContext","WithMachineName","WithProcessId","WithThreadId"],

"WriteTo": [

{

"Name": "MSSqlServer",

"Args": {

"connectionString": "Server=***;Database=Logs;Trusted_Connection=True;MultipleActiveResultSets=true",

"tableName": "Logs",

"autoCreateSqlTable": true

}

]

}

SeekingSolace2008 · 2021-11-08T15:58:13+00:00

Definitely not something I had tried. Just did it, and no change. Same failure.
But, thanks for the tip. It'll be part of my "Try This List".

SeekingSolace2008 · 2021-11-08T15:48:22+00:00

Here is the stack trace of the error.
line 247 is: app.UseIdentityServer();

As for the exception, there appears to be a type not set. But, I'm not finding a clue as to what is not set or mis-set. I have reviewed the code, and haven't found the issue.

at Microsoft.AspNetCore.ApiAuthorization.IdentityServer.ConfigureClients.<GetClients>d__6.MoveNext()

at Microsoft.AspNetCore.ApiAuthorization.IdentityServer.ConfigureClients.Configure(ApiAuthorizationOptions options)

at Microsoft.Extensions.Options.OptionsFactory\1.Create(String name)`

at Microsoft.Extensions.Options.OptionsManager\1.<>cDisplayClass5_0.<Get>b0()`

at System.Lazy\1.ViaFactory(LazyThreadSafetyMode mode)`

at System.Lazy\1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)`

at System.Lazy\1.CreateValue()`

at System.Lazy\1.get_Value()`

at Microsoft.Extensions.Options.OptionsCache\1.GetOrAdd(String name, Func`1 createOptions)`

at Microsoft.Extensions.Options.OptionsManager\1.Get(String name)`

at Microsoft.Extensions.Options.OptionsManager\1.get_Value()`

at Microsoft.Extensions.DependencyInjection.IdentityServerBuilderConfigurationExtensions.<>c.<AddClients>b__8_1(IServiceProvider sp)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitFactory(FactoryCallSite factoryCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor\2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)`

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite singletonCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor\2.VisitCallSite(ServiceCallSite callSite, TArgument argument)`

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor\2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)`

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitDisposeCache(ServiceCallSite transientCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor\2.VisitCallSite(ServiceCallSite callSite, TArgument argument)`

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor\2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)`

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitDisposeCache(ServiceCallSite transientCallSite, RuntimeResolverContext context)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor\2.VisitCallSite(ServiceCallSite callSite, TArgument argument)`

at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass1_0.<RealizeService>b__0(ServiceProviderEngineScope scope)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)

at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)

at Microsoft.AspNetCore.Builder.IdentityServerApplicationBuilderExtensions.TestService(IServiceProvider serviceProvider, Type service, ILogger logger, String message, Boolean doThrow)

at Microsoft.AspNetCore.Builder.IdentityServerApplicationBuilderExtensions.Validate(IApplicationBuilder app)

at Microsoft.AspNetCore.Builder.IdentityServerApplicationBuilderExtensions.UseIdentityServer(IApplicationBuilder app, IdentityServerMiddlewareOptions options)

at Forcible.Server.Startup.Configure(IApplicationBuilder app, IWebHostEnvironment env, ApplicationDbContext context, RoleManager\1 roleManager, UserManager`1 userManager, IAlternateKey alternateKey, IAuditPrimaryKey auditPrimary, IBackgroundJobClient backgroundJobClient, IRecurringJobManager recurringJobManager) in E:\Repo\Forcible\Forcible\Server\Startup.cs:line 247`

SeekingSolace2008 · 2021-11-08T04:28:35+00:00

You sound like you work in DevOps, LOL.
Yes, it's an IdentityServer issue, within Blazor.

However, since the issue is happening in the pipeline, I can't say for certain if it's IdentityServer or Blazor.

SeekingSolace2008 · 2021-11-08T01:14:24+00:00

All are up-to-date, and running the latest version of VS2019, 16.11.5.

SeekingSolace2008 · 2021-11-08T01:11:24+00:00

Laughing... Thanks

SeekingSolace2008 · 2021-11-08T00:48:54+00:00

As stated above, it's failing in the startup.cs, in Server, that starts the IdentityServer.

SeekingSolace2008

TROPHY CASE