MSBuild.SDK.SystemWeb
ReferenceAssemblyAnnotator
MSBuild.SDK.SystemWeb | ReferenceAssemblyAnnotator | |
---|---|---|
6 | 6 | |
142 | 70 | |
- | - | |
2.9 | 0.0 | |
9 months ago | over 2 years ago | |
Visual Basic .NET | 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.
MSBuild.SDK.SystemWeb
-
Why would you use Windows containers ?
I have some projects stuck on that, but not a lot. For web stuff, https://github.com/CZEMacLeod/MSBuild.SDK.SystemWeb does most of the heavy lifting, although things like publishing are broken.
-
Who is working on converting old projects into new ones?
I’ve had great luck with this on older ASP.NET projects https://github.com/CZEMacLeod/MSBuild.SDK.SystemWeb
- Is there a way to change my C# language version without editing the project file?
-
What's the future of asp.net 4
You can use this unofficial project to modernize your .NET Framework project and take advantage of things like PackageReferences.
-
Do you apply new C# features to existing code after upgrading .NET version?
Sdk at least works with .net standard so shared projects can be converted to that, we also had some success using the MSBuild.SDK.SystemWeb sdk nuget package for our MVC5 projects which I found from the github issue discussions on adding official support for it on older projects.
-
Upgrading .net framework 4.8 to .net core
I've been a bit luckier in that regard, but I'm not sure if your path wouldn't have taken less effort. I use https://github.com/hvanbakel/CsprojToVs2017 (dotnet migrate-2019 wizard) to modernize the projects, then further tweak them by hand. For ASP.NET projects, it's indeed a very difficult road. WebForms outright doesn't exist, and Core is very different from MVC in some areas. https://github.com/CZEMacLeod/MSBuild.SDK.SystemWeb helps somewhat.
ReferenceAssemblyAnnotator
-
Why would you use Windows containers ?
https://github.com/manuelroemer/Nullable (backport nullable attributes so you can use things like [NotNullWhen]). Alternatively, https://github.com/tunnelvisionlabs/ReferenceAssemblyAnnotator/ is even niftier, as it gives you .NET 5's annotations as well. So the compiler tells you whether a Dictionary.TryGetValue result is nullable or not based on annotations that didn't exist in .NET Standard 2.0.
-
Introducing: EasyCsv Dotnet
If you need the attributes, reference https://github.com/manuelroemer/Nullable or https://github.com/tunnelvisionlabs/ReferenceAssemblyAnnotator. The latter is bigger, but retroactively adds nullability annotations to runtime references (such as Dictionary.TryGetValue).
-
How to use C# 11 features in .NET 6 or older versions (even .NET Framework 2.0)
EDIT: A reader reached me about this cool package that partially solves this problem by injecting nullable reference type annotations in CLR's methods of some assemblies (check the docs for more details): ReferenceAssemblyAnnotator.
This helps: https://github.com/tunnelvisionlabs/ReferenceAssemblyAnnotator
-
The MVVM Pattern revisited with the MVVM Community Toolkit 8.0
Can't use 6.0 on that solution because https://github.com/tunnelvisionlabs/ReferenceAssemblyAnnotator/issues/89. But I did try 6.0 on a smaller project, where indeed, the warning seems to only appear if I downgrade to the 5.0.400 SDK. With 6.0.400, I get… a build error instead. With that workaround, it works.
-
Is there a way to change my C# language version without editing the project file?
https://github.com/tunnelvisionlabs/ReferenceAssemblyAnnotator to get Nullable Reference Type annotations from .NET 5 backported to Fx
What are some alternatives?
project-system - The .NET Project System for Visual Studio
visualstudio-docs - This repo is the home of the official documentation for Visual Studio.
IsExternalInit - A source code only package which allows you to use C# 9's init and record features in older target frameworks like .NET Standard 2.0 or the "old" .NET Framework by providing a polyfill for the IsExternalInit class.
CsprojToVs2017 - Tooling for converting pre 2017 project to the new Visual Studio 2017 format.
MSBuildSdkExtras - Extra properties for MSBuild SDK projects
Nullable - A source code only package which allows you to use .NET's nullable attributes in older target frameworks like .NET Standard 2.0 or the "old" .NET Framework.
Xamarin.Legacy.Sdk - Starting from a .NET 6 project, adds the ability to target legacy Xamarin target frameworks such as monoandroid11.0 or xamarin.ios10. *Not fully supported*
PolySharp - PolySharp provides generated, source-only polyfills for C# language features, to easily use all runtime-agnostic features downlevel. Add a reference, set your C# version to latest and have fun! 🚀