Posts
1145
Comments
890
Trackbacks
1
January 2006 Blog Posts
Fix for Visual Studio 2005 Step Into Bug

If you lost the ability to step into code when debugging because the menu items disappear, this will fix things up:

From: http://aspadvice.com/blogs/plitwin/archive/2005/11/12/13767.aspx

1)       Click the Tools->Import and Export Settings menu item

2)       Choose Reset all Settings

3)       Don’t save your settings

4)       Pick a new profile

posted @ Saturday, January 28, 2006 1:14 PM | Feedback (0)
T-SQL: Other datetime functions

http://weblogs.asp.net/guerchele/archive/2004/05/04/125899.aspx

posted @ Thursday, January 26, 2006 2:19 PM | Feedback (0)
T-SQL: Date only, time only

SELECT dateonly = CONVERT(CHAR(8),column,112) FROM table
SELECT timeonly = CONVERT(CHAR(8),column,8) FROM table 

posted @ Wednesday, January 18, 2006 11:35 AM | Feedback (1)
Managing a Doomed Software Project

If you've ever been on or seen one of these, this is a good read for what to do when they come around:

http://www.informit.com/articles/article.asp?p=437096

posted @ Sunday, January 15, 2006 6:12 PM | Feedback (0)
Create machineKeys for ASP.NET applications
http://support.microsoft.com/default.aspx?scid=kb;EN-US;312906
posted @ Saturday, January 14, 2006 2:00 PM | Feedback (0)
Windows Update Failure on Windows Server 2003

Thanks to this post:

http://mindsharpblogs.com/matthew/archive/2005/07/25/634.aspx

I was finally able to solve this issue. 

posted @ Saturday, January 14, 2006 1:06 PM | Feedback (3)
Setup Web Admin Tool for Production Servers

From khaivq at http://forums.asp.net/1155428/ShowPost.aspx:

“I have been able installed WebAdminTool for Production Servers using the following steps:

Create a virtual directory ASP.NETWebAdminFiles in IIS that point to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ASP.NETWebAdminFiles

Open properties windows of the new virtual directory, make sure that it is configured to run with ASP.NET 2.0, and in Security tab, uncheck Anonymous Access, check Integrated Windows Authentication.

After that, you will be able to connect to WebAdminTools using the following syntax
http://localhost/ASP.NETWebAdminFiles/default.aspx?applicationPhysicalPath=XXX&applicationUrl=/YYY
in my case, it is:
http://localhost/ASP.NETWebAdminFiles/default.aspx?applicationPhysicalPath=D:\Tasks\Libranyon\Photonyon\&applicationUrl=/Photonyon

Although I don't recommend to do it, if you want to access WebAdminTool from other computer, open WebAdminPage.cs from (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ASP.NETWebAdminFiles\App_Code) and comment the following code block
            if (!application.Context.Request.IsLocal) {
                SecurityException securityException = new SecurityException((string)HttpContext.GetGlobalResourceObject("GlobalResources", "WebAdmin_ConfigurationIsLocalOnly"));
                WebAdminPage.SetCurrentException(application.Context, securityException);
                application.Server.Transfer("~/error.aspx");
            }
WebAdminTool still be protected by Intergrated Windows Authentication, so you still some have some defense here.“

posted @ Sunday, January 08, 2006 4:31 PM | Feedback (0)