dotnet-apiport
VsixBlazorMinimalProjectTemplate
| dotnet-apiport | VsixBlazorMinimalProjectTemplate | |
|---|---|---|
| 4 | 1 | |
| 979 | 7 | |
| - | - | |
| 7.3 | 0.0 | |
| over 1 year ago | 27 days ago | |
| C# | C# | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dotnet-apiport
-
.NET MAUI and .NET 6/7 we feel the assembly hell again
There are a few tools that can help in the process. Years back I used a tool named Project2015to2017: https://github.com/hvanbakel/CsprojToVs2017. Since then, Microsoft also released a tool: https://github.com/dotnet/upgrade-assistant. There was also this tool but it looks like it has been discontinued: https://github.com/microsoft/dotnet-apiport
-
Aug 9, 2022 - Microsoft releases .NET Framework 4.8.1 - for Windows 10+ and Windows Server 2022+ only?
Then why does it matter that .NET Framework 4.8.1 doesn't support old servers. You're already on borrowed time. .NET Framework will probably EOL somewhere around 2026-27. If the cost to migrate to .NET 6 isn't worth it, then you might as well start retiring the software because you're basically saying it's not important enough to keep updated. The migration from 4.6+ to .NET 6 really isn't difficult unless you've got some weird obscure dependencies that haven't been updated yet and aren't open source. Have you even tried the portability analyzer? I work in consulting, and we hear this a lot, "oh our code is just too old and it's too much effort to port it to .NET Core", and from what I've seen the last few years, unless your project is still running in VB.NET with Web Forms and ASP, you can most likely upgrade to .NET 6 with way less effort than you expect.
-
Which linters are you using for CI environments?
https://github.com/microsoft/dotnet-apiport for portability issues
- New .NET REST API application needs to utilize .NET Framework 4.0 libraries. What are my options?
VsixBlazorMinimalProjectTemplate
-
Useful Visual Studio Extensions for Working with Blazor
The Blazor Minimal Project Template works effectively in Visual Studio 2017 and 2019, providing users with a project template for a .Net Standard project with a minimal implementation of client-side Blazor (a web UI framework based on C#, Razor, and HTML that runs in the browser using WebAssembly). Access via code on its GitHub repository.
What are some alternatives?
csharpier - CSharpier is an opinionated code formatter for c#.
BlazorSnippets - VS Code Snippets for Blazor
format - Home for the dotnet-format command
HtmlCssClassCompletion - A Visual Studio 2022 extension, that improvies the exisiting intellisense of css classes for html-like languages.
GLSL - VSIX Project that provides GLSL language integration.
HTML-CSS-Class-Completion - :chocolate_bar: Visual Studio Code extension that provides CSS class name completion for the HTML class attribute based on the CSS files in your workspace
Unchase.Odata.Connectedservice - :scroll: A Visual Studio extension for connecting to OData services with generating client-side C# proxy-classes
NsDepCop - NsDepCop is a static code analysis tool that helps to enforce namespace dependency rules in C# projects. No more unplanned or unnoticed dependencies in your system.
upgrade-assistant - A tool to assist developers in upgrading .NET Framework applications to .NET 6 and beyond
.NET Compiler Platform ("Roslyn") Analyzers
code-butler - Code Butler is a command line tool and VS code extension for your C# files at your service. This tool is heavily inspired by CodeMaid. As it is available as as a stand-alone version and as a Visual Studio Code extension, this tool will provide similar features.
MyGetDocs - Documentation site for MyGet