ReferenceAssemblyAnnotator
IL weaver to add nullability annotations to .NET reference assemblies (by tunnelvisionlabs)
CsprojToVs2017
Tooling for converting pre 2017 project to the new Visual Studio 2017 format. (by hvanbakel)
ReferenceAssemblyAnnotator | CsprojToVs2017 | |
---|---|---|
6 | 10 | |
70 | 1,069 | |
- | - | |
0.0 | 4.5 | |
over 2 years ago | 4 months ago | |
C# | C# | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
ReferenceAssemblyAnnotator
Posts with mentions or reviews of ReferenceAssemblyAnnotator.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-08.
-
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
CsprojToVs2017
Posts with mentions or reviews of CsprojToVs2017.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-02.
-
WinForms application missing resx
Yes, probably. Try the guide at https://learn.microsoft.com/en-us/dotnet/desktop/winforms/migration/?view=netdesktop-7.0. I personally prefer the tool https://github.com/hvanbakel/CsprojToVs2017/, but it's a bit more manual.
- NuGet Packages Step Into?
-
.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
- .NET 7 is out now! 🎉
-
Is there a way to change my C# language version without editing the project file?
https://github.com/hvanbakel/CsprojToVs2017 to convert projects to the new format. This is much nicer in multiple ways: VS doesn’t need to reload the project when it changes, version control changes are much less noisy, you get a Dependencies node in Solution Explorer instead of the old References one, etc.
-
Migrating to Latest .NET Using Upgrade Assistant
There is a much better tool for that: https://github.com/hvanbakel/CsprojToVs2017
-
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.
-
Date, Time, and Time Zone Enhancements in .NET 6
there's https://github.com/dotnet/try-convert. Haven't tried it; I instead use https://github.com/hvanbakel/CsprojToVs2017, but I assume the former might be a better choice by now.
- Help me with fixing : The project does not support adding package references through the add package command
-
.NET Upgrade Assistant Preview (to help upgrade .NET Framework-based applications to .NET 5)
I personally used https://github.com/hvanbakel/CsprojToVs2017 to port an existing 450+ projects solution using the old .csproj format to the new one. I had to manually fixup some projects afterwards but overall a good experience.
What are some alternatives?
When comparing ReferenceAssemblyAnnotator and CsprojToVs2017 you can also consider the following projects:
MSBuild.SDK.SystemWeb - This MSBuild SDK is designed to allow for the easy creation and use of SDK (shortform) projects targeting ASP.NET 4.x using System.Web.
project-system - The .NET Project System for Visual Studio