Blazor as front

[nicolas63]

Give the possibility to choose blazor for the frontend framework with this we can have full stack .NET

The first goal is to have a sample app with login and entities pages

If you are interested : https://github.com/nicolas63/JhipsterBlazor

[nicolas63]

@jdubois, @deepu105 , @pascalgrimaud . I Have work on sample application using Blazor ( an .net framework for create front app with web assembly). I'll soon have the minimum functions for create generator. But what is better, add this options in this blueprint or create an other blueprint juste for the Blazor front ?

[deepu105]

Separate blueprint will be better IMO

[nicolas63]

Yes, but there are certain logics that can be shared such as the C# naming convention, solution management, etc. If I create a new blueprint , maybe this logic can be extracted in another package like jhipster core ?
One of the advantages of using .net on both the client and server side is the ability to share code.
Does it make sense to create another blueprint if I want to share code on the generated application ?

[danielpetisme]

I would propose to generate Blazor front in the current dotnet blueprint. My guess is that only .Net devs will use Blazor. I can't imagine a Java server with a .Net front, it does not feel natural... So stick to the easiest solution, propose Blazor with the current blueprint and later on, if it make sense to split it then we would have facts to justify it. Le dim. 3 mai 2020 à 09:59, nicolas63 <notifications@github.com> a écrit :

…

Yes, but there are certain logics that can be shared such as the C# naming convention, solution management, etc. If I create a new blueprint , maybe this logic can be extracted in another package like jhipster core ? One of the advantages of using .net on both the client and server side is the ability to share code. Does it make sense to create another blueprint if I want to share code on the generated application ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#165 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEQ5HBVQEOFFBERT7UMH33RPUP65ANCNFSM4MQVB55Q> .

[nicolas63]

Okay, I think that's a good solution. Thank you @danielpetisme

[deepu105]

If you do it in this blueprint you need to do dome work around to propose react/angular options without overriding the entire front end prompts

…

On Sun, 3 May 2020, 10:56 am nicolas63, ***@***.***> wrote: Okay, I think that's a good solution. Thank you @danielpetisme <https://github.com/danielpetisme> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#165 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIOKF67N5ABKMMRTBQME23RPUWVPANCNFSM4MQVB55Q> .

[nicolas63]

yes it is possible ?