Wednesday, December 26, 2018

The setup for this installation of Visual Studio is not complete. Please run the Visual Studio Installer again to correct the issue.


                                 Recently I have faced this issue. I tried to install the Visual Studio community edition.  Cannot start Visual Studio Community Edition after installing. Got the error message "The setup for this installation of Visual Studio is not complete. Please run the Visual Studio Installer again to correct the issue." when launching.



Tried to reinstall, repair, cleanup of install, deleting old directories. Nothing works. Here is the workaround which fixed.

Workaround: 
  • Close any active Visual Studio applications
  • Go to the path C:\\Program Files (x86)\\Microsoft Visual Studio\\
  • Delete Installer folder
  • Now start the Visual Studio. It works :)

Friday, August 10, 2018

Format of the initialization string does not conform to specification starting at index 0

                       Recently I have faced this issues, I have got an opportunity to provide some enhancements to existing application. When I start running the application, I got this error. After analyzing further with configuration, I found that the connection string is not well-formed in the web.config.


Solution:

Check your connection string. If you need help with it check Connection Strings, which has a list of commonly used ones.

Commonly used Connection Strings:
SQL Server 2012
Standard Security
Server=myServerAddress;Database=myDataBase;User Id=myUsername;Password=myPassword;
Trusted Connection
Server=myServerAddress;Database=myDataBase;Trusted_Connection=True;
Connection to a SQL Server instance
The server/instance name syntax used in the server option is the same for all SQL Server connection strings.
Server=myServerName\myInstanceName;Database=myDataBase;User Id=myUsername;
Password=myPassword;
SQL Server 2005
Standard Security
Server=myServerAddress;Database=myDataBase;User Id=myUsername;Password=myPassword;
Trusted Connection
Server=myServerAddress;Database=myDataBase;Trusted_Connection=True;
Connection to a SQL Server instance
The server/instance name syntax used in the server option is the same for all SQL Server connection strings.
Server=myServerName\myInstanceName;Database=myDataBase;User Id=myUsername;Password=myPassword;
MySQL
Standard
Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
Specifying TCP port
Server=myServerAddress;Port=1234;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
Oracle
Using TNS
Data Source=TORCL;User Id=myUsername;Password=myPassword;
Using integrated security

Data Source=TORCL;Integrated Security=SSPI;

Friday, July 20, 2018

Exclude ELMAH 404 errors reporting

                 
                                 Recently we have faced a situation that receiving lots of 404 errors for a xx\xx path not found due to vulnerabilities scan software run against our web application. Since these errors raised by vulnerabilities scan software , we no need to concern and not required to log . So we decided to stop ELMAH reporting this error.

 I have done some analysis to find the best way to exclude these types of errors from being reporting. Here is the working solution I made with simple configuration changes in the  <elmah> section of web.config as specified below