Thank you.

>I can show you my project using teamviewer or teams. I figured out a few things that really helped me as a VFP developer. If you like pm me and we could set up a good time.
>
>Regarding your question about C#: that greatly depends on a few key factors. Proficient is a big word, but the important thing is to be productive and not to scratch your head for each little thing you need to do. But of course there will be blockers, but you will find answers relatively quickly.
>According to my experience, the main factors are:
>- Are you working already as much as possible OOP or still mostly procedural? that will be the first big learning curve if you are far away from OOP.
>- Do you have experience with Visual Studio? It takes one or two weeks to get used to this environment and to find the right places.
>- How much time can you spend? Obviously putting in 50 hours in two weeks is more efficient than 5 hours weekly during 10 weeks.
>- Do you have a real project you can start working on? It's a different thing to just play around, or to create a real project for a client, which gives you more focus and pushes you further.
>
>Apart from those issues, I found C# extremely easy and comfortable to work with. The learning curve is less than FoxPro, not alone because there are lots of libraries and resources that are really great. Of course there are also some more advanced themes, like async tasks, event handling etc, so not everything is sugar coated.
>
>Regarding the Blazor part: that is going to be really easy once you know sufficient C#. There are great tutorials with which you can create solutions in a few hours and understand the concepts step by step. As I mentioned before: You are working with the same technology on the web client as with the server. In fact there is a "Shared" project which has classes used by both.
>
>Here some resources:
>This one really helped me speed up development with Entity Framework and Blazor:
>https://codewithmukesh.com/blog/blazor-crud-with-entity-framework-core/
>
>A lot of sample projects and documents:
>https://github.com/AdrienTorris/awesome-blazor
>
>Also some courses from Tim Corey if you are patient enough:
>https://www.iamtimcorey.com/p/exploring-c-blazor-webassembly
>(He also has free tutorials on Youtube.)
>
>>Thank you for the feedback Christian.
>>
>>Whatever you have to show me... bring it on ;-D
>>
>>How long would you say it should take a VFP developer to be proficient in C# and Blazor?
>>
>>Regards
>>
>>
>>
>>>Just to throw in my 2 cents:
>>>
>>>I decided for Blazor specifically because it uses mainly one language for coding, backend and frontend alike. That is the one thing I liked of VFP, to have one basic language with only some exceptions to be done differently.
>>>
>>>Using Blazor I have to do minimal work in CSS if at all, very little JavaScript, but more than 90% C# backend and frontend alike. You do need some javascript/CSS framework though, there are some free ones and some more professional ones. For my simple project I used Blazorise (https://blazorise.com/)
>>>
>>>If you are interested I could show you my project so you can make yourself a picture of it.
>>>
>>>>Hello Michael,
>>>>
>>>>If you don't mind me asking,.
>>>>
>>>>Why did you decide to use Blazor?
>>>>
>>>>Recommandation?
>>>>
>>>>Just because the big Microsoft is behind it?
>>>>
>>>>Because of the programming language?
>>>>
>>>>When did you start using it? Is it evolving fast?
>>>>
>>>>I appreaciate all the comments.
>>>>
>>>>Regards
>>>>
>>>>>>And now here comes Blazor. I never really heard about it in the last weeks. But recently that changed.
>>>>>>Comments?
>>>>>
>>>>>No experience with it yet.
>>>>>I really really really want it to work.
>>>>>Jumping between C# and JavaScript is a pain.
>>>>>
>>>>>We are using DevExpress components and their Blazor grid is in "preview" and not feature complete, so we are waiting.