提高大麻的重建速度
在更改我的Blazor Server项目时，现在相当大的重建大约需要30秒。在某些情况下，这是生产力的障碍。据我所知，在我的情况下，热重新加载几乎完全没有用。
如果我将这个项目分解为较小的项目，那么假设我只会更改一个子项目之一，这会减少重建时间吗？
如果建议这样做，我该如何与共享服务等单个功能性的外界项目一起协调这些子项目？
When making changes to my Blazor server project, which is quite massive now, the rebuild takes approximately 30 seconds. In some cases, this is serving as an impediment to productivity. Hot reload is, so far as I can tell, almost completely useless in my case.
If I break this project into smaller ones, would this then reduce the rebuild times, assuming I only change one of the sub projects?
If this is advisable, how would I go about coordinating those sub-projects into a single functioning Blazor project, with shared services and so on?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
顺便说一下，答案非常简单。您可以构建剃须刀级图书馆项目。
我当前的过程是在主要项目中构建和编辑新组件，然后在我不想暂时不工作时将它们移至库。
The answer to this, by the way, is quite simple. You can build a Razor class library project.
My current process is to build and edit new components in the main project, then move them to the library when I won't want to work on them for a while.