All Things Microsoft AI

I recently had a .NET solution where I wanted to use the same App.config in 2 different projects.  I wanted to always ensure that changes made in the App.config of the original project would be reflected in other project(s) automatically.  Listed below are the steps I used to facilitate that process. 1.      Right-click your project in Solution Explorer 2.      Select "Add" -> "Existing Item..." 3.      Navigate to the file that you want to add to the solution 4.      [Important]  Instead of hitting Enter or clicking the Add button, you want to click the down-arrow icon at the right edge of the Add button, and select "Add As Link".    

Q: Can we upload documents like pdf as input and configure the agents to retrieve the required content that is expected   A: The short answer is yes, but with some configuration.  Working in the Agent Playground, you have the option to “Add” Knowledge.  This knowledge can be from a variety of different data sources as seen below. As stated below “Currently only a single instance per each type of data source is supported.”  In my scenario, I had a single text file setup when I configured my agent, before being published.   Another option would be to utilize the Azure AI Search to index multiple documents from a data store, where documents can be uploaded after the agent is published.  As of today, there are 6 other options available for accessing documents    

AI agents and agentic AI are related but not the same. AI agents are task oriented systems built around LLMs, while agentic AI refers to a broader paradigm where AI systems exhibit autonomy, goal directed behavior, and self improving capabilities.   AI Agents vs. Agentic AI AI Agents: perform tasks but do not necessarily set their own goals. •             Modular systems built around LLMs or LIMs. •             Designed for narrow, task specific automation. •             Operate through tool integration, prompt engineering, and workflow orchestration.   Examples: ·                   A customer service chatbot ·              ...

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...

User Groups Nov 4: Capital Area .NET Users Group Nov 12: Azure Cleveland Nov 13: Akron AITP Nov 19: Cleveland C# User Group Nov 20: GLUG.NET   Conferences Nov 11-13: .NET Conf 2025  

The SQL Server equivalent of Oracle.ManagedDataAccess.Client is either System.Data.SqlClient or Microsoft.Data.SqlClient System.Data.SqlClient is the older built-in provider. Microsoft.Data.SqlClient is the newer, actively maintained version with better support for .NET Core and .NET 5+.   Feature Oracle.ManagedDataAccess.Client System.Data.SqlClient / Microsoft.Data.SqlClient Database Oracle SQL Server Namespace Oracle.ManagedDataAccess.Client System.Data.SqlClient  or Microsoft.Data.SqlClient Connection class OracleConnection SqlConnection Command class OracleCommand SqlCommand Data reader class OracleDataReader SqlDataReader NuGet package Oracle.ManagedDataAccess System.Data.SqlClient  (legacy) or Microsoft.Data.SqlClient  (modern)   ...

To remove Git from a solution in Visual Studio 2022, effectively unbinding it from source control, follow these steps: Ensure the solution is NOT open in the Visual Studio IDE. Navigate to the root directory of your solution using File Explorer. If you cannot see the .git folder, you need to enable the display of hidden files and folders in File Explorer. In Windows, open File Explorer, go to the "View" tab, and check "Hidden items." Delete the .git folder within your solution's root directory. This folder contains all the Git repository information, including history, branches, and tags for the solution and all projects within it. Visual Studio should now recognize that the Git repository is no longer present and will no longer manage it with Git source control.