VS2022 can build BUT getting errors in many places

[GeorgeS2019]

[GeorgeS2019]

Error CS0117

[sps014]

Yeah These are source generator errors and I was experimenting one idea to automatically generate binding code from struct, class or record definition . New proposed experiment (works on wasm): https://github.com/sps014/BlazorBindGen/blob/main/SampleApp/JSBinding/ML5Binding.cs Old Code https://github.com/sps014/BlazorBindGen/blob/c881152369ee24b9b5c827473bdaf265769c269a/SampleApp/Pages/ML5Page.razor

[GeorgeS2019]

I am using the proposed experiment which works on WASM. Question Any suggestions on how to switch off these errors which do not prevent one from compiling successfully?

[sps014]

Can you post error Message ?

[GeorgeS2019]

[sps014]

These errors can be caused by poor tooling of Source Generator at this moment, also at this point new API is in development I need to do lot of code refactoring next month.

[GeorgeS2019]

[GeorgeS2019]

These errors can be caused by poor tooling of Source Generator at this moment, also at this point new API is in development I need to do lot of code refactoring next month.

For users, it is unclear how stable is the new API. Would you consider separating the new API as a SEPARATE BRANCH which you could merge to master ONCE the code refactoring is done?

[sps014]

For users, it is unclear how stable is the new API. Would you consider separating the new API as a SEPARATE BRANCH which you could merge to master ONCE the code refactoring is done?

Yeah that would be better, will create a separate branch.

Also there is workaround for Visual Studio errors(not testesd) https://github.com/dotnet/roslyn/issues/44093

[GeorgeS2019]

Yeah that would be better, will create a separate branch.

What you experiment has a consequence on your user. With more capabilities come more responsibility. :-)

[sps014]

Closing this as these bugs will be fixed by Visual Studio team in upcoming versions.