Visual Studio gives errors when used with the .NET Standard branch
See original GitHub issueWhen I open a project in Visual Studio running with the .NET Standard branch of Rezoom.SQL I get the following error:
The type provider 'Rezoom.SQL.Provider.Provider' reported an error: The type initializer for '<StartupCode$Rezoom-SQL-Compiler>.$Rezoom.SQL.Compiler.Config' threw an exception.
Seems like a VS specific problem: Neither dotnet CLI nor VS Code have a problem with the project.
PS: I’m aware of the fact that this project seems to be a bit abandoned (no offense to you @rkosafo) but I hope a running .NET Standard (#15) version of this library will bring a lot more interest in this project.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:9
Top Results From Across the Web
Visual Studio displaying errors even if projects build
These errors are often namespace issues and missing references, even when the library reference exists. To resolve: Close Visual Studio. Delete ...
Read more >Fix program errors and improve code - Visual Studio ...
This article describes some basic ways Visual Studio can help you find and fix problems in your code, including build errors, code analysis, ......
Read more >Troubleshoot .NET Framework targeting errors
To resolve the error, make sure that your application targets a .NET version that's compatible with the version that's targeted by the projects ......
Read more >Creating and Packaging a .NET Standard library
In this post we will cover how you can create a .NET Standard library and then share that with other developers via NuGet....
Read more >Upgrading your .NET projects with Visual Studio - .NET Blog
The .NET Upgrade Assistant is now available as an experimental extension in Visual Studio to easily enable to update your apps and projects ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It would be great to see this amazing project resurrected
@rspeele What do you think about moving the development to https://github.com/fsprojects? Would you be positive about that? Thanks
@rspeele Thank you for all your work, and it would be great if we can continue it as a community thing
My recommendation would be to move it into fsprojects - neutral incubation spaces attract maintainers and contributions (e.g. paket etc.). We would continue to make your role in originating it evident in the README and docs.
fsprojects has myself and Sergey Tihon doing oversight. So I think between @smoothdeveloper , @bddckr, @toburger and others we would be able to take it forward.
If you decide to do this I think you can just move the repo in directly and then we patch up permissions