fix: include libraries

[keithlogan94]

• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for your PR that you are making. Please open an issue to dicuss changes or new features.

PR Title
Added include libraries

PR Description
Added include libraries

Fixes #7

[babanfaraj]

LGTM

[andrewbabbittdev]

Looks like a bug in Rider. Code compiles without these meaning they aren't needed.

I'll double check this when I hop on in about an hour.

[andrewbabbittdev]

Definitely a bug in rider, this should be brought to their attention I'm just not sure what channels/how we go about doing so.

[andrewbabbittdev]

@keithlogan94

Fully confirmed, this is indeed a rider bug.

C# 10 / .NET 6 added a new global usings feature. You can read up on it here.

As for how this is causing rider to detect this as an error, .NET 6 Preview 7 (the latest preview release) added commonly used namespaces as global using's in web projects. You can see the tracking item at dotnet/aspnetcore#32451 and the implementation in dotnet/sdk#18459.

After a build you can open the file src/Medulla.Frontend/Server/obj/Debug/net60/Medulla.Frontend.Server.ImplicitNamespaceImports.cs which has the following content:

// <autogenerated />
global using global::System;
global using global::System.Collections.Generic;
global using global::System.IO;
global using global::System.Linq;
global using global::System.Net.Http;
global using global::System.Threading;
global using global::System.Threading.Tasks;
global using global::System.Net.Http.Json;
global using global::Microsoft.AspNetCore.Builder;
global using global::Microsoft.AspNetCore.Hosting;
global using global::Microsoft.AspNetCore.Http;
global using global::Microsoft.AspNetCore.Routing;
global using global::Microsoft.Extensions.Configuration;
global using global::Microsoft.Extensions.DependencyInjection;
global using global::Microsoft.Extensions.Hosting;
global using global::Microsoft.Extensions.Logging;

Rider does not appear to be analyzing this file for whatever reason while Visual Studio and VS Code both do. This should get fixed in a future rider update. Keep in mind Rider does not fully support .NET 6 yet, can check out their post on it here. This is actually a nice new feature in .NET 6, so would really like to embrace it.

Visual Studio 2022 & VS Code are fully supported and updated every month to support the latest preview sdk updates. This should be less of an issue as we get closer to the GA release of .NET 6 in November. RC1 will be out on the 14th.

Until a fix is added to rider we could either just have you guys ignore the bug in rider or we could add <DisableImplicitNamespaceImports>true</DisableImplicitNamespaceImports> into all csproj files and add all the usings manually.

Ideas/thoughts?

[andrewbabbittdev]

Resolved with latest rider versions.