Open Windows Explorer, right-click on the CHM file, and select Properties from the popup menu. Click on the Unblock button immediately below the Advanced button on the General page. Click Apply to show the content.
Hope this helps.
This blog is about developers who are working on MS Technologies and mobile development. You can find very interesting stuff related to MS Technologies like ASP.NET, C#, VB.NET, SharePoint 2003, SharePoint 2007, MS SQL SERVER 2000 , MS SQL SERVER 2005, MS SQL SERVER 2008 and about latest technologies. Also people can also post stuffs related MS Dynamics CRM 3.0, MS Dynamics CRM 4.0 , MS Dynamics GP, Ms Dynamics Soloman.
Tuesday, June 30, 2009
Login failed for user [user name]. Reason: Server is in single user mode. Only one administrator can connect at this time
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user [user name]. Reason: Server is in single user mode. Only one administrator can connect at this time.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Solution : visit http://www.interviewsworld.com
Exception Details: System.Data.SqlClient.SqlException: Login failed for user [user name]. Reason: Server is in single user mode. Only one administrator can connect at this time.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Solution : visit http://www.interviewsworld.com
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Solution: viewview Solution
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Solution: viewview Solution
Labels:
.net,
.Net framework,
asp.net 3.5,
C#,
visual studio 2008
Cannot create/shadow copy [Project File Name] when that file already exists.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileLoadException: Cannot create/shadow copy 'Test.UI' when that file already exists.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Test.UI' could not be loaded.
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Solution : visit View Solution
Exception Details: System.IO.FileLoadException: Cannot create/shadow copy 'Test.UI' when that file already exists.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Test.UI' could not be loaded.
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Solution : visit View Solution
Labels:
.net,
asp.net,
C#,
visual studio 2008
Monday, June 15, 2009
Changing the default browser used in VS 2008 and Visual Web Developer
I have seen a few people ask if it is possible to change what browser is launched and used when running web applications in VS 2008 and Visual Web Developer (for example:Chrome, Firefox instead of IE). It is an easy way to configure this.
Below is steps:
1) Right click on a .aspx page in your solution explorer
2) Select the "browse with" context menu option
3) In the dialog you can select or add a browser. If you want Firefox in the list, click "add" and point to the firefox.exe filename
4) Click the "Set as Default" button to make this the default browser when you run any page on the site.
Note that there is also an optional drop-down at the bottom of the dialog that lets you select the default browser window size when loading. You can choose 800x600 or 1024x768 if you want to visualize what the site will look like for people using those screen resolutions. This works for both IE and FireFox (and probably other browsers too -- those just happened to be the two I checked).
Hope this helps,
www.interviewsworld.com
Below is steps:
1) Right click on a .aspx page in your solution explorer
2) Select the "browse with" context menu option
3) In the dialog you can select or add a browser. If you want Firefox in the list, click "add" and point to the firefox.exe filename
4) Click the "Set as Default" button to make this the default browser when you run any page on the site.
Note that there is also an optional drop-down at the bottom of the dialog that lets you select the default browser window size when loading. You can choose 800x600 or 1024x768 if you want to visualize what the site will look like for people using those screen resolutions. This works for both IE and FireFox (and probably other browsers too -- those just happened to be the two I checked).
Hope this helps,
www.interviewsworld.com
Labels:
.net 3.5,
visual studio 2008
Subscribe to:
Posts (Atom)