I spent ages trying to find a solution to this issue after upgrading to VS2012.
This link solved the problem and stopped me returning to VS2005.
Why Microsoft, why?
Thank you malamsson.
Visual Studio 2010 versus COM-Object fails
Recent Categories
- AJAX (1)
- APIM (4)
- Application Insights (3)
- ARM (2)
- asp.net (12)
- Azure (17)
- Azure Function (6)
- Bash (1)
- bicep (2)
- BizTalk (3)
- blob storage (1)
- Business (1)
- button (2)
- c# (7)
- CI/CD (4)
- code coverage (1)
- connection (2)
- cross browser (1)
- css (2)
- D365 (1)
- database (2)
- debug (4)
- deployment (4)
- deployment slot (1)
- devops (4)
- durable (1)
- firefox (3)
- General (23)
- html (2)
- ie (4)
- Integration Monitoring (2)
- javascript (5)
- Key Vault (2)
- Logic App (4)
- Logic App (Std) (5)
- Monitoring (2)
- Nodinite (2)
- Office (1)
- ordered lists (1)
- postback (1)
- Postman (1)
- regular expressions (4)
- Service Bus (3)
- sftp (1)
- sql (3)
- terraform (1)
- Uncategorized (2)
- unordered lists (1)
- visual studio (6)
- VS Code (1)
- winforms (2)
- xml (2)
- xslt (2)
- yaml (2)
- yui (1)
- zero downtime (1)
Recent Posts
- Nodinite e-Learning
- Using Bash to Deploy a Logic App using an Office365 API Connection
- Becareful When Enabling SSH File Transfer Protocol (SFTP) support for Azure Blob Storage
- Using Powershell to Deploy a Logic App using an Office365 API Connection
- What is Consuming my Azure Service Bus Subscription?
Post Archive
- June 2024
- May 2024
- April 2024
- December 2023
- September 2023
- April 2023
- February 2023
- January 2023
- December 2022
- November 2022
- September 2022
- August 2022
- April 2022
- February 2022
- January 2022
- December 2021
- March 2018
- February 2017
- October 2013
- September 2013
- October 2008
- May 2008
- April 2008
- March 2008
- February 2008