Posts

Showing posts from October, 2025

Deployment Types in AI Foundry

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

Nov '25 Regional Tech Events

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  

Converting .NET Application from Oracle to SQL Server

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

How can I remove GitHub bindings from a Visual Studio 2022 Solution

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.