@typeparam no longer allows trailing semi-colons

[majorimi]

I have a open sourced Blazor component library. And recently I'm getting this error below when I try to run with dotnet watch run my demo app to develop the components.

C:\Program Files\dotnet\sdk\6.0.100-preview.4.21255.9\Microsoft.Common.CurrentVersion.targets(4964,5): 
error MSB3030: Could not copy the file "D:\Projects\GitHub\blazor-components\src\Majorsoft.Blazor.Components.CssEvents\obj\Debug\net5.0\staticwebassets\Majorsoft.Blazor.Components.CssEvents.StaticWebAssets.xml" 
because it was not found. [D:\Projects\GitHub\blazor-components\src\Majorsoft.Blazor.Components.Modal\Majorsoft.Blazor.Components.Modal.csproj]

To give more details. I'm using Visual Studio 2019 (stable for development) but also have VS 2019 Preview installed. My projects using .NET 5.0.3 and dotnet watch run was working perfectly before .NET 6 preview got installed. But now dotnet commands using preview version: dotnet\sdk\6.0.100-preview.4.21255.9 even if the project is just .NET 5.

As I can see the problem is obj\Debug\net5.0\staticwebassets\<PROJECT_NAME>.StaticWebAssets.xml is generated on every VS build. But when watch tool is detecting changes and does a "build" these files are deleted from obj folder. So instead of file copy the watch tool might move/delete these files. I have multiple project in my solution this is true for all. And getting this error for lot of them...

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[majorimi]

@mkArtakMSFT Now .NET 6 Preview 5 is out and tested dotnet watch run with Preview 5 and still has the error... This time with different projects. It seems issue happens randomly with a few projects in the solution.

C:\Program Files\dotnet\sdk\6.0.100-preview.5.21302.13\Microsoft.Common.CurrentVersion.targets(4964,5): error MSB3030: 
Could not copy the file "D:\Projects\GitHub\blazor-components\src\Majorsoft.Blazor.Components.Timer\obj\Debug\net5.0\staticwebassets\Majorsoft.Blazor.Components.Timer.StaticWebAssets.xml" 
because it was not found. [D:\Projects\GitHub\blazor-components\src\Majorsoft.Blazor.Components.Debounce\Majorsoft.Blazor.Components.Debounce.csproj]

Also now Preview 5 has more issues with Templated components and Typeparams. I'm getting "build" errors with watch command. Meanwhile Visual Studio does not have build errors since it is compiling the project with .NET 5. But watch run uses .NET 6 Preview 5. See new errors below:

D:\Projects\GitHub\blazor-components\src\Majorsoft.Blazor.Components.Typeahead\TypeaheadInput.razor(1,17): 
error RZ1011: The 'typeparam' directives value(s) must be separated by whitespace. [D:\Projects\GitHub\blazor-components\src\Majorsoft.Blazor.Components.Typeahead\Majorsoft.Blazor.Components.Typeahead.csproj]

D:\Projects\GitHub\blazor-components\src\Majorsoft.Blazor.Components.Typeahead\TypeaheadInputText.razor(1,17): 
error RZ1011: The 'typeparam' directives value(s) must be separated by whitespace. [D:\Projects\GitHub\blazor-components\src\Majorsoft.Blazor.Components.Typeahead\Majorsoft.Blazor.Components.Typeahead.csproj]

Is this new issue should be posted separately? Also any quick solution to this?
Thanks.

[majorimi]

@mkArtakMSFT For unblocking my community work for now created a global.json file in the demo app root folder. Where set "allowPrerelease": false so now dotnet watch run uses .NET 5.

But for sure in .NET 6 there are some issues with dotnet watch run. Also it seems that there will be breaking changes. Or error RZ1011: The 'typeparam' directives value(s) must be separated by whitespace. is also a bug in .NET 6?

[pranavkm]

@majorimi the SDK will roll-forward to using the latest version installed, it's not influenced by the version of the app. However, they're designed to be back-compatible. I tried running demo\Majorsoft.Blazor.Components.DemoApp using the latest nightly of the .NET 6.0 preview SDK (https://github.com/dotnet/installer#installers-and-binaries) and VS 16.11.0 Preview 2.0 I'm not seeing the warning / errors you listed.

Could you share detailed steps to reproduce the issue?

[majorimi]

Hi @pranavkm,

Thanks for your reply. Yes the Demo project will work since it does not have direct dependencies to any "Razor Class Library" projects in this solution. demo\Majorsoft.Blazor.Components.DemoApp uses already published Nuget packages from Nuget.org. Demo project works for me as well. Please check TestApps solution folder. You can find 3 projects there. Please try to run Majorsoft.Blazor.Components.TestApp you can even find run.bat inside the project folder.

For more details please check the project structure:

• demo\Majorsoft.Blazor.Components.DemoApp: Published WASM application for demo purposes and uses already published Nuget packages as it would be used by a "package consumer" projects. This project is making sure all published Nuget packages are working as expected. No direct references to any other projects in this SLN and It works!
• src\Majorsoft.Blazor.Components.TestApps.Common: this project has references for all Component and Extension in the solution and provides usage examples and other components with \page directive for navigation. This is shared between WASM and Server hosted Blazor app. With this project sample code is not duplicated.
• src\Majorsoft.Blazor.Components.TestApp: Blazor WASM app using the Common project. So this has direct references (via common project) to all components and during component development I can make sure all components works with Blazor WASM. This does not work!! Please try dotnet watch with this project.
• src\Majorsoft.Blazor.Components.TestServerApp: Blazor Server Hosted application using the Common project and during component development I can make sure all components works with Server side Blazor.