The latest info on AI Features in Microsoft Foundry and ML.NET
What is a Tablix?
Get link
Facebook
X
Pinterest
Email
Other Apps
-
The term "Tablix" can mean different things to different people. However, in the Microsoft realm it refers to the ability of SQL Server Reporting Services (SSRS) to combine a table and a matrix together.
As discussed in our last meeting, web applications can be built to handle both PC browsers and mobile browsers. To do so, the application needs to detect if the browser is a mobile device and redirect the application to a page designed to display UI adequate for the smaller mobile browser. Detecting the browser is done using the following code sample, and it's typically placed in the Page_Load() of the login.aspx or default.aspx Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load Try If Not IsPostBack Then If Request.Browser.IsMobileDevice = True Then Response.Redirect("mobile/login.aspx") End If End If Catch ex As Exception ProcessEx(ex) End Try End Sub
Deploying a model in Azure AI Foundry can be done in 9 different ways. Depending on the type of deployment chosen, it may impact one of more factors, such as cost, latency, efficiency for processing large datasets, compliance. Listed below is a description of each deployment type, along with advantages and disadvantages. For more details, please visit https://learn.microsoft.com/en-us/azure/ai-foundry/foundry-models/concepts/deployment-types Deployment Type Description Advantage Disadvantage Global Standard Shared global infrastructure for general-purpose model inference. Cost-effective and easy to scale. Performance may vary under high demand. Global Provisioned Dedicated global infrastructure for consistent performance. Reliable throughput and latency. Higher cost due to dedicated resources. Global Batch Asynchronous globa...
What's better for mobile development with .NET Maui, Blazor or XAML? Each has its pros and cons. Listed below is a brief comparison of the 2 options: Maui with Blazor : Web Tech, Shared Logic Best for: Web developers or teams already using Blazor for web apps who want to reuse components and logic. Pros: - Write UI in Razor syntax (HTML + C#) - Share components across web and mobile - Easier onboarding for web devs - Great for internal tools or hybrid apps Cons: - Slight performance overhead compared to native XAML - Limited access to some native features (though improving) - Smaller ecosystem for mobile-specific Blazor components Maui with XAML : Native Feel, Rich Control Best for: Developers with WPF, UWP, or Xamarin.Forms experience, or those wanting full control over native UI. Pros: - Deep integration with MAUI’s native controls - Rich styling and layout capabilities - More mature tooling and community support for mobile-specific features - Better performance for compl...
Comments
Post a Comment