Skip to main content

Taste of Vista

I had a taste of Vista this weekend on my friend's laptop. I think Microsoft shot itself in the foot with their over protective security features. I'm pretty sure users will get exhausted with "Are you sure you.....? after some time. I dont understand why I have to confirm every time I open an application. Didn't M$ft think about how it will ruin the end user experience?
My friend created a website in .Net and wanted to host it in IIS. To successfully host the website in IIS we had to go through a multi layered defense system. We overcame the first line of defense by turning on the IIS feature, which I think is good. Then came the second line of defense which is "No permissions to....." to which we did not have a straight answer. After spending some time on Google with no luck, we stumbled on the answer by chance. (We had to give IUSR account permissions on the physical directory that contains the website). I thought well this is the answer and tried to launch the website from IE, and Vista threw a third line of defense which is IIS do not have permission to run ASP.Net. With the help of Google we passed the third of line of defense to successfully run our website in IIS.

Comments

Post a Comment

Popular posts from this blog

Clear Validation Errors and Validation Summary messages

ASP.net built in validation does not provide us a straight forward to clear all the validation errors. This would be really helpful while resetting a form. The reset html button would simply reset the form values but will not clear the validation errors. The following javascript code snippet can be used to clear the validation error messages. Have a reset button on your form and call the following js function onclick. <input type="reset" onclick="HideValidationErrors();" /> function HideValidationErrors() { //Hide all validation errors if (window.Page_Validators) for (var vI = 0; vI < Page_Validators.length; vI++) { var vValidator = Page_Validators[vI]; vValidator.isvalid = true; ValidatorUpdateDisplay(vValidator); } //Hide all validaiton summaries if (typeof (Page_ValidationSummaries) != "undefined") { //hide the validation summaries ...
2 comments
Read more

Find the cause of poor performance in Sql Server

I found the following two part article by Gail Shaw on Simple-Talk really helpful in trouble shooting poorly performing queries in Sql Server. The articles talks about spotting poorly performing queries with the help of the Profiler, understand Sql Server Query plans and fine tune the peformance using proper indexes. Part 1: http://tinyurl.com/ccl6gj Part 2: http://tinyurl.com/okcuqg
18 comments
Read more

SharePoint: Comparing dates in XSLT

In one of my sharePoint projects, I had to compare a date with the current date in XSLT. As it turned out, there is no support for date comparision in XSLT. This is how I went about doing it. The trick involves converting the date string into a number Say the date is in ISO format YYYY-MM-DDTHH:MM:SSZ (for example, 2001-01-21T22:54:47Z). Say we have a variable DueDate <xsl:variable name="DueDate" select="'2001-01-21T22:54:47Z'"> Replace the dashes in the string with empty string Take the first 10 character in the date sring convert the string to number number(translate(substring(@DueDate,1,10),'-','')) On doing the above we get: 20010121 We can do the same thing with the date to compare. We can compare the duedate with the current date in SharePoint as follows number(translate(substring(@DueDate,1,10),'-','')) & lt; number(translate(substring(ddwrt:TodayIso(),1,10),'-','')) You can apply the same log...
2 comments
Read more