You searched for the word(s): userid:878191

More Search Options

RSS Available

• Re: ASP.NET : Avoid Flickering Of Master Page And Content Page

  Monalisa, what this simply does is use IE page transitions. That causes IE to effectively buffer the response from the new page until it's fully rendered. With no time in the transition what you end up with is simply an almost instantaneous switch from one page to the other.

  Posted to Master Pages, Themes and Navigation Controls (Forum) by Nissan Fan on 7/21/2009

• Re: stored procedure help??

  Stored Procedures are Transact SQL (T-SQL) statements which you can store within a database in SQL Server. They act just like functions: they accept input parameters from a caller and return results in a defined format (single value, list of data, multiple lists of data). Benefits Centralizes data access logic as close to the actual data as possible, which typically means better performance though today the performance gain is nearly undetectable Allows you to restrict calling programs only to using

  Posted to Data Access and ObjectDataSource Control (Forum) by Nissan Fan on 7/14/2009

• Re: Remember Me

  First of all, the Remember Me feature on the standard ASP.NET Login control persists the Forms Authentication ticket in the browser's cookie cache instead of memory. What it does when it's checked on Login is simply say: if this is checked, when then user closes the browser completely ... the next time they open try to use the Forms Authentication ticket (cookie) created at the last login. If it isn't expired then take them to the page they requested. It's not the behaviour most people

  Posted to Web Forms (Forum) by Nissan Fan on 7/9/2009

• Re: MVC + Models + Webservices

  I haven't seen anything in particular, but based on how the MVC is applied best practice in the ASP.NET space the only justified use of Web Services would be WCF services abstracted via a Repository/repositories. This means neither the client (browser) nor the server are concerned about ASMX/WCF inner workings and you have much greater long-term flexibility and testability. How this could be applied: - e.g. Auto-Complete via AJAX/JSON: instead of going straight to a service from the client you

  Posted to ASP.NET MVC (Forum) by Nissan Fan on 7/7/2009

• Re: Combobox Search throughout the string

  No. An alternative is to use the AutoComplete control going against a Web Service. Using that you could control the selection method completely.

  Posted to ASP.NET AJAX Control Toolkit (Forum) by Nissan Fan on 7/7/2009

• Re: Urgent: Form Authentication

  Don't use cookieless sessions is one way. Even without cookieless sessions unless you utilize SSL someone could hi-jack the HTTP headers and get the cookie information used to sync the session on the server with the requestor. Bottom line: don't use cookieless sessions and don't worry about Man in the Middle attacks so much. Another is you could write code in Global.asax.cs under the Session_Start event to store the IP address of the requestor in the Session. If the IP address varies

  Posted to Security (Forum) by Nissan Fan on 7/7/2009

• Re: Oracle to SQL server replication using .NET ?

  http://msdn.microsoft.com/en-us/library/ms152481.aspx As for knowing when CUDs have occurred on the source, the updates would be sent over as they are made or on a schedule (depends on your config). You could monitor them or be alerted of them as follows: http://msdn.microsoft.com/en-us/library/ms151752.aspx

  Posted to SQL Server, SQL Server Express, and SqlDataSource Control (Forum) by Nissan Fan on 7/7/2009

• Re: Event Validation and Disable Controls

  Yes it's easy to call the methods server-side should you want to, but impossible to trigger them from the client-side. That's because they are simply methods.

  Posted to Web Forms (Forum) by Nissan Fan on 7/7/2009

• Re: Authorize Attribute

  I still can't follow your logic about why you shouldn't be able to authorize anonymous users only for an Action. To me, without an Authorize you are giving an implicit allow to everyone and many sites are driven by user roles. An anonymous user should only have access to things like login, register, etc. and allowing authorized users to muck in areas they shouldn't be in represents the same challenge you would have if someone not authorized were to try to use a resource that requires

  Posted to ASP.NET MVC (Forum) by Nissan Fan on 7/6/2009

• Re: Exception Handling & Logging - Suggestions?

  From a pure security standpoint any unhandled exceptions should be displayed to the user as a generic message. Typically something along the lines of "An unexpected error has occurred. If this problem persists please contact your System Adminstrator." General rule is that you allow exceptions to bubble up. You can use the Error facilities of ASP.NET MVC to catch them at the point it would impact the Users. To use these facilities, apply the [HandleError] Action Filter atttribute to an Action

  Posted to ASP.NET MVC (Forum) by Nissan Fan on 7/6/2009