Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
139266 stories
·
31 followers

Salesforce wants to do for agentic AI what they did for SaaS

1 Share
Christophe Coenraets, SVP of Developer Relations at Salesforce, tells Eira and Ben about building the new Salesforce Developer Edition, which includes access to the company’s agentic AI platform, Agentforce. Christophe explains how they solicited and incorporated feedback from the developer community in building the developer edition, what types of AI agents people are building, and the critical importance of guardrails and prompt engineering.
Read the whole story
alvinashcraft
1 hour ago
reply
Pennsylvania, USA
Share this story
Delete

Announcing Native Azure Functions Support in Azure Container Apps

1 Share

A New Way to Host Functions on ACA

With the new native hosting model, Azure Functions are now fully integrated into ACA. This means you can deploy and run your functions directly on ACA, taking full advantage of the robust app platform. 

Create via Portal: Option to optimize for Azure function

If you are using CLI, you can deploy Azure Functions directly onto Azure Container Apps using the Microsoft.App resource provider by setting “kind=functionapp” property on the Container App resource.

Create via CLI: Set “kind=functionapp” property

Please note, in the new native hosting model,

  • Azure Functions extensions will continue to work as before.
  • Auto-scaling will remain available.
  • Deployments are supported through ARM templates, Bicep, Azure CLI, and the Azure portal.
  • Monitoring using Application Insights is supported in the same way as apps hosted by Azure Functions.
  • Your function app can access the same virtual networking resources provided by the Container App environment.
  • Entire range of event-driven triggers and bindings is available. However, only the following triggers can dynamically scale (from zero instances) when running in ACA environment. This list is consistent with earlier approach of hosting via Microsoft.Web resource provider.
  • All standard function tasks like processing file uploads, running AI tasks, executing scheduled jobs, or reacting to changes in a database and entire list of Azure function scenarios are supported.
  • Serverless GPU and GPU-enabled hosting in the Dedicated plan with workload profiles is supported.

Feature-Rich and Fully Integrated

Native Azure Functions on ACA unlock the complete feature set of Azure Container Apps, including:

In summary, by running Functions in Container Apps, you benefit from automatic scaling, access to native ACA features, official support and a fully managed container environment—all without having to manage the underlying infrastructure yourself.

Transitioning to the new hosting method

Previously, hosting Azure Functions on Azure Container Apps (ACA) was made available using Microsoft.Web resource provider. While this method is effective, it introduced complexity and had limited access to some of ACA’s native features. Additionally, some of you may have deployed plain vanilla function images on the ACA environment, However, this approach does not offer advantages of auto-scaling and is not officially supported.

If you are currently deploying function images on Azure Container Apps, we recommend transitioning to the new native hosting model. Here are the steps to move to this new approach,

  • Simply create a new Function Container App using the native hosting model. You can create via Azure Portal or Azure CLI.
  • During the creation process, provide the function image URL of your existing function image at the appropriate steps. Additionally, remember to manually create the storage account and app insight resources, and set necessary app settings from existing app as Environment Variables and Secrets in the native Functions Container App. This will set your Function Container App with the new “kind=functionapp” property.
  • The new native Function Container App should be tested to ensure it is working correctly. If it is functioning as expected, you can proceed to delete the old deployment.

Get Started Today

Ready to try it out? You can deploy your first function app natively on ACA using the Azure CLI, Bicep, ARM templates, or the Azure Portal.

Explore the documentation below to learn more.

Read the whole story
alvinashcraft
1 hour ago
reply
Pennsylvania, USA
Share this story
Delete

Episode 519: This is a “hit by pitch”

1 Share

This week, we discuss Zenoss finally getting acquired, Databricks buying Neon, and the debut of WizOS. Plus, updates on OpenAI, Google, Apple—and hot takes on Marmite, Vegemite, and Emacs.

Watch the YouTube Live Recording of Episode 519

Runner-up Titles

  • Vegemite is still bad
  • You’re probably eating it
  • It’s a bold statement
  • This episode’s all about us
  • Pendantic is my jam
  • They tell you they’re making “calculated bets”
  • Rupert
  • SlackGPT
  • No one knows anything, do everything

Rundown

Relevant to your Interests

Nonsense

Conferences

SDT News & Community

Recommendations

Photo Credits





Download audio: https://aphid.fireside.fm/d/1437767933/9b74150b-3553-49dc-8332-f89bbbba9f92/d2454583-fcc4-4aa6-a363-429d3fda8c50.mp3
Read the whole story
alvinashcraft
1 hour ago
reply
Pennsylvania, USA
Share this story
Delete

.NET Web App Modernization Made Easy with Tomáš Herceg's New Book and DotVVM

1 Share

DotConnect and Entity Developer

dotConnect and Entity Developer boost .NET development with high-performance ADO .NET providers and visual ORM builder. Try a 30-day free trial now!

Show Notes

"I remember I had the entire life cycle of the web forms printed on a wall. It was like six sheets of paper and it was very complex, and it was very useful to have it on the wall because, like, you could always look at it and say, "okay, this is going on before this one." So you have to like switch the order of things. But that's exactly what I call interesting"— Tomáš Herceg

Welcome friends to The Modern .NET Show; the premier .NET podcast, focusing entirely on the knowledge, tools, and frameworks that all .NET developers should have in their toolbox. We are the go-to podcast for .NET developers worldwide, and I am your host: Jamie "GaProgMan" Taylor.

In this episode, we talk with Tomáš Herceg about strategies for modernizing .NET Framework web applications such that they leverage the very latest in the .NET stack. Tomáš shares his insights from the journey of upgrading his own applications and those of his clients, both of which provided the background for his new book: "Modernizing .NET Web Applications".

"The biggest problem of the YARP migrations: that they will force you to do a lot of infrastructure things at the beginning before you even start migrating some real functionality."— Tomáš Herceg

Along the way, we discuss how using his DotVVM project can help with the migration. Not only is the upgrade path for DotVVM projects a process of swapping a NuGet package, but is also keeps the upgrade as a single in-memory process—something that YARP-based migrations aren't able to do.

Anyway, without further ado, let's sit back, open up a terminal, type in `dotnet new podcast` and we'll dive into the core of Modern .NET.

Supporting the Show

If you find this episode useful in any way, please consider supporting the show by either leaving a review (check our review page for ways to do that), sharing the episode with a friend or colleague, buying the host a coffee, or considering becoming a Patron of the show.

Full Show Notes

The full show notes, including links to some of the things we discussed and a full transcription of this episode, can be found at: https://dotnetcore.show/season-7/dotnet-web-app-modernization-made-easy-with-tomas-hercegs-new-book-and-dotvvm/

Links:

Supporting the show:

Getting in Touch:

Remember to rate and review the show on Apple Podcasts, Podchaser, or wherever you find your podcasts, this will help the show's audience grow. Or you can just share the show with a friend.

And don't forget to reach out via our Contact page. We're very interested in your opinion of the show, so please get in touch.

You can support the show by making a monthly donation on the show's Patreon page at: https://www.patreon.com/TheDotNetCorePodcast.

Music created by Mono Memory Music, licensed to RJJ Software for use in The Modern .NET Show





Download audio: https://traffic.libsyn.com/clean/secure/thedotnetcorepodcast/S07E19-TomasHerceg.mp3?dest-id=767916
Read the whole story
alvinashcraft
1 hour ago
reply
Pennsylvania, USA
Share this story
Delete

Creating an Azure AI Search service

1 Share

Azure AI Search provides a fast, scalable, reliable vector search service that you can extend with RAG and other AI services.

In this article, I will show how to create an Azure AI Search service.

Navigate to the Azure Portal and log in.

Click the [Create a resource] button (Fig. 1) and search for "ai search" or "azure ai search," as shown in Fig. 2.

Create Resource button
Fig. 1

Search For AI Search
Fig. 2

From the list of results, select the [Create] button in the "Azure AI Search" panel (Fig. 3) to expand the menu, and select the [Create] option, as shown in Fig. 4.

Azure AI Search Panel
Fig. 3

Create Button
Fig. 4

The "Create a search service" dialog displays with the "Basics" tab selected, as shown in Fig. 5.

Create AI Search Blade -Basics Tab
Fig. 5

At the "Subscription" dropdown, select the subscription in which you want to create this AI Search service. Many of you will have only one subscription, so you will not need to choose anything here.

At the "Resource group" field, select the resource group in which you want to create the Search service, or click the "Create new" link to create a new resource group in which to add the Search service. A resource group is a logical grouping of Azure resources you want to manage together.

At the "Service name" field, enter a unique name for this Search service.

At the "Location" dropdown, select an Azure region in which to create the Search service. Consider the location of the people and services using this service to minimize latency.

The "Pricing tier" field defaults to "Standard." If you want to change this, click the "Change pricing tier" link and select an appropriate tier from the list of options, as shown in Fig. 6.

SelectPricingTier
Fig. 6

These pricing tiers are listed in ascending order of price and capacity. You should select one that meets your needs, but resist paying for more than you need.

Fig. 7 shows the "Scale" tab. It is unnecessary to change anything on this tab, but it allows you to add more Replicas and partitions. Increasing Replicas increases the availability of the service, while increasing Partitions increases the capacity of the service. You should set the Replicas to at least 3 for production environments to achieve high availability for read and write operations.

Create AI Search Dialog - Scale Tab
Fig. 7

Fig. 8 shows the "Networking" tab. It is unnecessary to change anything on this tab, but it allows you to restrict access to the account to specific networks and configure private endpoints for the account.

Create AI Search Dialog - Networking Tab
Fig. 8

Fig. 9 shows the "Tags" tab. It is not necessary to change anything on this tab, but you can apply name-value pairs to this resource that you may use to filter or sort your reports.

Create AI Search Dialog - Tags Tab
Fig. 9

Fig. 10 shows the "Review + create" tab. If you made any errors, such as leaving a required field empty or selecting an inconsistent combination of options, these errors will be listed here, and you will need to correct them before you can proceed.

Create AI Search Dialog - Review + Create Tab
Fig. 10

After correcting any errors, click the [Create] button (Fig. 11) to start creating the Azure AI Search service.

Create Button
Fig. 11

After a short time, a confirmation message like the one in Fig. 12 will display, indicating that the Search service has been created.

Deployment Complete message
Fig. 12

Click the [Go to resource] button (Fig. 13) to show the "Overview" blade of the newly created Azure AI Search service, as shown in Fig. 14.

Go To Resource Button
Fig. 13

AI Search Overview Blade
Fig. 14

This article showed you how to create an Azure AI Search service.

Read the whole story
alvinashcraft
1 hour ago
reply
Pennsylvania, USA
Share this story
Delete

Semantic Kernel: Package previews, Graduations & Deprecations

1 Share

Semantic Kernel: Package Previews, Graduations & Deprecations

We are excited to share a summary of recent updates and continuous clean-up efforts across the Semantic Kernel .NET codebase. These changes focus on improving maintainability, aligning with the latest APIs, and ensuring a consistent experience for users. Below you’ll find details on package graduations, deprecations, and a few other improvements.

Graduations

  • Plugins.Core Package Graduated to Preview The Microsoft.SemanticKernel.Plugins.Core package has been moved from “alpha” to “preview” status, reflecting its maturity and readiness for broader use. This change does not introduce new features but signals increased stability for those relying and building on these core plugins.
  • PromptTemplates.Liquid Package Graduated The Microsoft.SemanticKernel.Liquid prompt template package has also graduated, with package validation enabled to ensure quality and compatibility.

Spring Cleaning – Deprecations

  • Markdown Package Deprecated The Microsoft.SemanticKernel.Markdown package has been removed due to lack of usage. If you still use this package, please refer to the migration guide.
  • Math and Wait Plugins Removed The Math and Wait plugins, which were part of the project since its early days, have been removed as they are no longer relevant.
  • OpenAI and Handlebars Planners Deprecated The Microsoft.SemanticKernel.Planners.Handlebars and Microsoft.SemanticKernel.Planners.OpenAI planners were deprecated in favor of more reliable mechanisms such as function calling, and the decision was made to discontinue their availability on NuGet packages. For migration details, see the stepwise planner migration guide.

Improvements & Updates

  • Plugins.Core Package API Is No Longer Experimental The experimental attribute has been removed from the Plugins.Core package API, reflecting its stable usage in production environments.
  • Stable OpenAPI API The experimental attribute was also removed from the stable OpenAPI API, and package validation was enabled to ensure ongoing reliability.
  • SessionsPythonPlugin Updates
    • API Migration The plugin was migrated to the latest Azure code interpreter API version (2024-10-02-preview). This required some breaking changes to the plugin public API surface. See the migration guide for details.
    • Structured Results Python code execution results are now represented by a dedicated type, allowing for more structured handling and easier integration with other components.
    • Request Handling The plugin now propagates cancellation tokens through all kernel functions, ensuring that operations can be gracefully terminated in response to user requests or timeouts, thereby improving resource management and application responsiveness.
    • Domain Control Added the ability to control which domains requests can be sent to, increasing security and configurability.
    • HTTP Consistency Refactored to use SendWithSuccessCheckAsync extension methods for HTTP requests, aligning with other Semantic Kernel components.
    • Code Clean-up Common functionality was consolidated to reduce duplication, and minor logging and readability improvements were made.
    • Integration Tests Added integration tests for the plugin to ensure its reliability, and early detection of issues.

These updates are part of our ongoing effort to keep the Semantic Kernel codebase clean, stable, and easy to use. For more information on migrating from deprecated or updated components, please refer to the linked migration guides.

If you have feedback or questions, please join the discussion on our GitHub repository.

The post Semantic Kernel: Package previews, Graduations & Deprecations appeared first on Semantic Kernel.

Read the whole story
alvinashcraft
1 hour ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories