Not sending the Application DLL in Blazor WASM

neozhu / RazorPageCleanArchitecture

This is a solution for creating the Razor Pages Application with ASP.NET Core(.net 7.0) following the principles of Clean Architecture

https://commercial.blazorserver.com/

MIT License

401 stars 94 forks source link

Not sending the Application DLL in Blazor WASM #2

Closed garkpit closed 3 years ago

garkpit commented 3 years ago

When using Blazor in WASM - I want to not send any of my business logic (Application) to the client. (I don't want them to reverse engineer it). I want to send only the things it actually needs = the DTOs.

Please can you split out the DTOs to a separate Project - e.g. Application.Dto - and make sure only that goes down the wire to the client?

Open to other ideas!

Thanks!

neozhu commented 3 years ago

That makes a lot of sense split application project. Lightweight simplicity is the original intention, Work with code generation tools, and keep your business code in a single project.

neozhu commented 3 years ago

Blazor WASM is client mode. EF core(dbcontext) not support WASM