N. Taylor Mullen 1e9c0f01af Add Blazor partial class support in Visual Studio. (dotnet/aspnetcore-tooling#1182) ... - No longer mark declaration files as single file generators. Prior to this we relied on SingleFileGenerators to dynamically update the declaration files when .razor files changed. However, to make partial classes work we can no longer depend on declaration files being available because their existence causes us to have to mangle class names for opened documents; otherwise you get two files with same name and result in ambiguous definition errors. - Stopped including declaration files as part of the users compilation. This was intended to make the design time experience operate more similar to how Blazor apps function at runtime (directly access each component instead of their declarations). We now rely on the background code generation effort built from the find all references work to supply users with strongly typed component names. - Stop mangling class names for Visual Studio. Razor.VSCode has its own set of configurations which i'm not addressing as part of this changeset. - Start generating components with the partial modifier to their class name to enable partial class support. - Updated existing tests to expect partial modifier. aspnet/AspNetCoredotnet/aspnetcore-tooling#5487\n\nCommit migrated from 73858cdd37		2019-10-01 13:59:33 -07:00
src	Add Blazor partial class support in Visual Studio. (dotnet/aspnetcore-tooling#1182)	2019-10-01 13:59:33 -07:00