I routinely share application solutions between Radzen Blazor Studio and Visual Studio 2022 in my development. This is mainly because I develop the pages in Blazor Studio and tune my application in Visual Studio (and sometimes in Jet Brains Rider) for speed, adherence to best practices, and, finally, to commit the code to source control. Generally, I find that there are minimal issues that are easily worked around. However, there have been issues, such as the database interface within the Blazor Studio Editor disappearing and the absence of the ability to add any additional API functionality to any data source. I was curious whether you might have any idea as to why this occurs. It's pretty easily reproduced. Just create a new application, add a database data source (SQL Server in my case), and then create a REST API data source and populate it with at least one API function. Then save all and open the solution in visual studio and again save. Finally, reopen the solution in Blazor studio and attempt to Create or Update a Data Source..
Interestingly Radzen Blazor Studio needs to directly connect to the API before it can show the '+' Icon so that I can add new functionality in the REST Connection. I guess I can live with that, as it's only a little inconvenient. It would be nice to have some stats notification or maybe an informative message to the effect, though. But why does the SQL Server Data Source GO away?
I cannot reproduce such an issue. Added SQL database (Northwind) and the Spotify REST API from our documentation. Opened the application in VS2022 and clicked the "save all" button in the toolbar. Nothing changed - I see the data sources in RBS just fine:
I am also attaching my test application. Net802Wasm.zip (730.0 KB)
The + button is visible right from the start. Here is what I see:
Do you mean that an existing data source disappears from the Data sources dialog? This could happen if the generated code is changed in a way that RBS no longer recognizes it as a data source. The algorithm is as follows:
- Find the "startup" code - usually Program.cs
- Find code invoking the
AddDbContextandUseSqlServermethods. - Find the generated EF DBContext class.
If any of these steps fails the database won't be recognized.
You can send us your app to info@radzen.com and we will investigate further.