How to add DrawingView or Signaturepad in Maui using CommunityToolkit.maui.core, or how can I implement Signaturepad in maui project.
Both aren't supported for .NET MAUI right now.
For the Release Candidate of the Community Toolkit we plan to have DrawingView, the PR is mostly ready. However, for Windows it will be unsupported, simply because WinUI hasn't implemented the necessary bits yet.
Related
I tried to follow Microsoft guidelines for Windows Applications. I will write apps using .NET MAUI.
Straight off the bat I noticed this .xaml file in the Quick Start MAUI project I created in VS2022. Personally I hadn't encountered these before, so I went to read about them.
At the Learn.Microsoft website it states this:
XAML allows developers to define user interfaces in .NET Multi-platform App UI
(.NET MAUI) apps using markup rather than code. XAML is not required in
a .NET MAUI app, but it is the recommended approach to developing your UI because
it's often more succinct, more visually coherent, and has tooling support
What does it mean "and has tooling support" in the context of using XAML, as opposed to just purely C#?
Just as Steve suggested, with the assistance of XAML Hot Reload, it can enable you to view the result of XAML changes in your running app, without having to rebuild your project. Without XAML Hot Reload, you have to build and deploy your app every time you want to view the result of a XAML change or in C# code(purely C#).
Also, XAML has several advantages over C# code(purely C#):
XAML is often more succinct and readable than equivalent code.
The parent-child hierarchy inherent in XML allows XAML to mimic with
greater visual clarity the parent-child hierarchy of user-interface
objects.
There isn't a control for datagrid that views data in rows and columns that I could find from Microsoft instead of from third party. When is Microsoft going to release it?
Right now there is no such control that I am aware of. Not within .NET MAUI itself nor in the .NET MAUI community toolkit nor in a third-party free control.
I know that nothing is on the roadmap right now for .NET MAUI and the .NET MAUI Community Toolkit. Of course I don't know what is being developed by the community.
As you already pointed out, there are paid vendors that do have controls like these, think of Telerik, Syncfusion and Devexpress. I think Syncfusion has a community license that you can use for free as long as you adhere to certain criteria.
SiteMapPath .Net component works fine on .Net environment. But it seems not on .Net Core.
For e.g., if the https://www.c-sharpcorner.com/UploadFile/2f59d0/implementing-sitemap-in-Asp-Net/ is developed choosing .Net Core, the breadcrumps as expected do not show up.
But I couldn't find any official doc from Microsoft on that. Does any one know.
Thank you.
I am creating a .net library in Visual Studio 2015 with the following aims:-
Support for .net 2, 3.5, 4 and 4.5+
PCL Support (.net 4.5+)
No extra dependencies apart from Json.net
Ideally the .net 4.5+ version of the library would make use of async, and include methods that return Task etc
Now there seems to be many different ways of supporting what I want to do, especially with the Visual Studio 2015/project.json release but what is a good approach starting from scratch today?
My library is relatively simple, so as much as I want to re-use code I don't want to compromise the .net 4.5 version.
What would be a sensible project structure, that would mean I could take advantage of the latest .net framework, but still build in support for older frameworks.
With Beta8 of the WebDev tooling you are able to also target net2, net35, net40, net45, ...
Your library differences you might use #ifdef flags in your code to hide certain methods in certain builds.
In beta builds of Autofac 2.1 there was support for automatic resolution of Lazy<T> as described in Nicholas Blumhardt's Lazing Around with Autofac blog post.
The code still seems to be in the source on Google Code, but I can't find LazyDependencyModule in any of the .NET 4.0 binaries I've looked at. Has it moved somewhere else?
How do I use Autofac's automatic Lazy<T> resolution with the latest Autofac builds?
You don't need to register LazyDependencyModule yourself in the production Autofac 2 builds. It is a part of the default container, so just register T and Lazy<T> will be provided.
Make sure you're not accidentally using a .NET 3.5 binary, too :)
Nick