How to Create a PDF with proper tags for accessibility
Using Visual Studio 1 solution 3 projects A front end, using react for external users to submit (react) A front end for internal users for approvals (razor) A backend used by both (C#) We are presently creating PDFs. The PDFs are not Accessibility compliant. We need to avoid licensing or service fees. How can we create PDFs (ideally in the c# backed) that allows for tagging to ensure that the PDF's are accessibility standards compliant (e.g. WCAG) Thank you!
Feature messages keep popping up in Visual Studio Community 2026
Good day, I am trying to fix/get rid of these annoying messages that keeps popping up in my IDE. Microsoft.ServiceHub.Framework.ServiceActivationFailedException : Activating the "Microsoft.VisualStudio.LanguageServices.AssetSynchronizationCore64" service failed. ---> StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete. Microsoft.ServiceHub.Framework.ServiceActivationFailedException : Activating the "Microsoft.VisualStudio.LanguageServices.DocumentHighlightsCore64" service failed. ---> StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete. Microsoft.ServiceHub.Framework.ServiceActivationFailedException : Activating the "Microsoft.VisualStudio.LanguageServices.NavigationBarItemCore64" service failed. ---> StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete. Any idea how I can get rid / fix 'em Tried: Repairing VS Clearing MEF & component cache Environment reset Manually Add CET Features via XML Setup: Windows 11 (OS Build 21996.1) on KVM/QEMU Thank you all!VS bugs in 2026 impacting average users
I am one of those people who never sees bugs in long-time major products. My browsers don't crash, OneDrive backups work, my car radio turns on when I push the button. I am just an average developer/user. But I installed Visual Studio 2026 (community) in April. I immediately experienced a catastrophic publishing bug that others had just reported in the previous few days. Now in October, after the recent update, Github Copilot (free) chat doesn't work, and dragging the execution point in the debugger works only if Hot Reload is disabled. These are monumentally annoying bugs that impact huge numbers of users, even infrequent users. They are things that everyone does. It is shameful that the newest version of VS is regularly being updated with bugs that cause such massive impacts.
Blazor App No Longer Compiles
I just updated MS Visual Studio 2022 Community Edition to version 18.11.0. After the update, Blazor apps no longer compile in for the release version, they still work for the debug version of the project. This is true with existing projects and new Blazor App projects created with C#. I get this error message: ===================== 10/16/2026 4:16:12 AM Project: BillByrnes.csproj Recoverable System.AggregateException: One or more errors occurred. ---> (Inner Exception #0) Microsoft.Assumes+InternalErrorException: No pending webSession for web server 1 at Microsoft.Assumes.Fail(String message) at Microsoft.WebTools.ProjectSystem.HotReload.WebHotReloadAgent.StartSession(IWebServer webServer) at Microsoft.WebTools.ProjectSystem.Debugger.BaseDebugTargetsProvider.<OnAfterLaunchAsync>d__84.MoveNext() <--- (Inner Exception #0) =================== Any help would be appreciated. Thanks, Bill Byrnes email address removed for privacy reasons
Simple request for Visual Studio's Find and Replace operation
Doing a Find + Replace operation in VS, I could wish there was an option, when selecting to do so over the whole project or solution, to choose which types of files to include or exclude. For example, in a classic Web Forms project, I'd like to omit the designer pages. I've been caught out by this ore than once ... :( (More fool I...)Mastering Query Fields in Azure AI Document Intelligence with C#
Introduction Azure AI Document Intelligence simplifies document data extraction, with features like query fields enabling targeted data retrieval. However, using these features with the C# SDK can be tricky. This guide highlights a real-world issue, provides a corrected implementation, and shares best practices for efficient usage. Use case scenario During the cause of Azure AI Document Intelligence software engineering code tasks or review, many developers encountered an error while trying to extract fields like "FullName," "CompanyName," and "JobTitle" using `AnalyzeDocumentAsync`: The error might be similar to Inner Error: The parameter urlSource or base64Source is required. This is a challenge referred to as parameter errors and SDK changes. Most problematic code are looks like below in C#: BinaryData data = BinaryData.FromBytes(Content); var queryFields = new List<string> { "FullName", "CompanyName", "JobTitle" }; var operation = await client.AnalyzeDocumentAsync( WaitUntil.Completed, modelId, data, "1-2", queryFields: queryFields, features: new List<DocumentAnalysisFeature> { DocumentAnalysisFeature.QueryFields } ); One of the reasons this failed was that the developer was using `Azure.AI.DocumentIntelligence v1.0.0`, where `base64Source` and `urlSource` must be handled internally. Because the older examples using `AnalyzeDocumentContent` no longer apply and leading to errors. Practical Solution Using AnalyzeDocumentOptions. Alternative Method using manual JSON Payload. Using AnalyzeDocumentOptions The correct method involves using AnalyzeDocumentOptions, which streamlines the request construction using the below steps: Prepare the document content: BinaryData data = BinaryData.FromBytes(Content); Create AnalyzeDocumentOptions: var analyzeOptions = new AnalyzeDocumentOptions(modelId, data) { Pages = "1-2", Features = { DocumentAnalysisFeature.QueryFields }, QueryFields = { "FullName", "CompanyName", "JobTitle" } }; - `modelId`: Your trained model’s ID. - `Pages`: Specify pages to analyze (e.g., "1-2"). - `Features`: Enable `QueryFields`. - `QueryFields`: Define which fields to extract. Run the analysis: Operation<AnalyzeResult> operation = await client.AnalyzeDocumentAsync( WaitUntil.Completed, analyzeOptions ); AnalyzeResult result = operation.Value; The reason this works: The SDK manages `base64Source` automatically. This approach matches the latest SDK standards. It results in cleaner, more maintainable code. Alternative method using manual JSON payload For advanced use cases where more control over the request is needed, you can manually create the JSON payload. For an example: var queriesPayload = new { queryFields = new[] { new { key = "FullName" }, new { key = "CompanyName" }, new { key = "JobTitle" } } }; string jsonPayload = JsonSerializer.Serialize(queriesPayload); BinaryData requestData = BinaryData.FromString(jsonPayload); var operation = await client.AnalyzeDocumentAsync( WaitUntil.Completed, modelId, requestData, "1-2", features: new List<DocumentAnalysisFeature> { DocumentAnalysisFeature.QueryFields } ); When to use the above: Custom request formats Non-standard data source integration Key points to remember Breaking changes exist between preview versions and v1.0.0 by checking the SDK version. Prefer `AnalyzeDocumentOptions` for simpler, error-free integration by using built-In classes. Ensure your content is wrapped in `BinaryData` or use a direct URL for correct document input: Conclusion Using AnalyzeDocumentOptions provides a cleaner and more reliable way to work with query fields in Azure AI Document Intelligence using C#. By aligning with the latest SDK approach, developers can simplify implementation, reduce common errors, and improve code maintainability. Keeping up with SDK enhancements and recommended practices ensures more accurate and efficient document data extraction. As Azure AI capabilities continue to evolve, adopting modern integration patterns will help you build scalable and future-ready document processing solutions with greater confidence. Reference Official AnalyzeDocumentAsync Documentation. Official Azure SDK documentation. Azure Document Intelligence C# SDK support add-on query field.Pair Programming and test-driven development with Visual Studio Live Share and GitHub Copilot
Pair programming and TDD are valuable software development techniques that can enhance the development process, and GitHub Copilot can help teams effectively utilize these practices to produce high-quality code.Enhancing Data Security and Digital Trust in the Cloud using Azure Services.
Enhancing Data Security and Digital Trust in the Cloud by Implementing Client-Side Encryption (CSE) using Azure Apps, Azure Storage and Azure Key Vault. Think of Client-Side Encryption (CSE) as a strategy that has proven to be most effective in augmenting data security and modern precursor to traditional approaches. CSE can provide superior protection for your data, particularly if an authentication and authorization account is compromised.
