View Complete Post
I tried to use Microsoft's Membership option for signing up new users and authenticating them on subsequent pages, but it has not worked very well. The biggest issue has been with the REMEMBER ME function. With this checked, I am randomly logged out in the middle of some functions and some pages always show me as not authenti
this is my aspx and cs code , let me know whether it is correct or not??
onload and performance on navigation of record show be good.
Plz help me
<CR:CrystalReportViewer ID="CrystalReportViewer1" runat="server" AutoDataBind="True"
DisplayGroupTree="False" ReuseParameterValuesOnRefresh="true" HasToggleGroupTreeButton="False" Height="1039px" ReportSourceID="CrystalReportSource1"
<CR:CrystalReportSource ID="CrystalReportSource1" runat="
Good navigation makes for happy users, and happy users are good for your business. See what makes users happy this month.
Dr. Charles B. Kreitzberg and Ambrose Little
MSDN Magazine March 2009
In my childhood I spent several weeks a year in Holland with my extended family. As a young American boy I was fascinated with the electric Dutch trains, something we didn't see in my hometown of Dallas, Texas.
MSDN Magazine October 2005
Edited by Nancy Michell
MSDN Magazine September 2005
Navigation is central to a well functioning Web application and it can be implemented numerous ways using today's technologies. This article highlights some of the key details of the new navigation controls that are part of the upcoming ASP.NET 2.0, and talks about how to design and implement one of these navigation controls today. This article contains a simple Web site that demonstrates the use of these navigation controls, pointing out some of the key items such as a breadcrumb control and things to watch for along the way. The article then describes how to implement a breadcrumb control today.
Dave Donaldson and Steven DeWalt
MSDN Magazine June 2004
As systems grow and become more heterogeneous, so their complexity increases. The more code you write, the more that can go wrong. The more that can go wrong, the more you need a good instrumentation policy. In this article, the author looks at the various technologies available in the .NET Framework, such as tracing, logging, WMI, EIF, which are designed to help you. He will also look at the pitfalls you should avoid and provide you with the fundamentals from both a technical and managerial perspective so that you can instrument your code effectively.
MSDN Magazine April 2004
ASP.NET provides many different ways to persist data between user requests. You can use the Application object, cookies, hidden fields, the Session or Cache objects, and lots of other methods. Deciding when to use each of these can sometimes be difficult. This article will introduce the aforementioned techniques and present some guidelines on when to use them. Although many of these techniques existed in classic ASP, best practices for when to use them have changed with the introduction of the .NET Framework. To persist data in ASP.NET, you'll have to adjust what you learned previously about handling state in ASP.
MSDN Magazine April 2003
Development can have its frustrating moments. How many times have you been in the middle of a project and encountered a problem you just couldn't solve alone? In order to help you through this, Microsoft provides quite a wide variety of support options from Web-based chats and newsgroups to paid premier customer support.
MSDN Magazine February 2003
MSDN Magazine October 2002
MSDN Magazine January 2002
MSDN Magazine September 2001
This article, the second of two parts, continues coverage of Web security for Windows. It introduces the Web Application Manager in IIS that allows Web processes to be isolated, decreasing the security risk associated with running in a logon session. The article then picks up where Part One left off-it discusses authentication methods such as basic authentication, digest authentication, integrated Windows authentication, and anonymous logons, and the benefits and drawbacks of each.
MSDN Magazine July 2000
I always have used Enterprise
Library DAAB with stored procedures for data access with 4 seprate layers
(presentation layer, custom types layer, business logic layer and data access
My feeling is that this development approach wasts much time.
I have not worked with other ways of accessing data but sure there are many
ways that save development time. While searching I read about these:
So much options and my little knowledge, I am confused in making decision
what development patern I should adopt considering that my development may be
fast, extendable, re-usable and up to the standard. Also I want to go for a way
in which my code libraries can be used with other technolgies like silverlight,
mvc framework, services if I ever need to use.
Kindly guide me and help.
This is the twenty-seventh in a series of blog posts I'm doing on the VS 2010 and .NET 4 release.
Today's blog post continues on from the Debugging Tips post I did last week, and covers some useful searching and navigation tips/tricks you can take advantage of within Visual Studio. These tips were ones that my friend Scott Cate (who has blogged dozens of great VS tips and tricks here) recently recommended to me as good tips that most developers using Visual Studio don't seem to know about (even though most have been in the product for awhile).
Hopefully this post will help you discover them if you aren't already taking advantage of them. They are all easy to learn, and can help save you a bunch of time.
Most developers using Visual Studio are familiar with the "Find dialog" that you can launch by pressing the "Ctrl + F" key within the IDE. A surprisingly large number of developers, though, aren't familiar with the "Incremental Search"
1) Exception Information
Exception Type: System.Web.HttpException
Message: Path 'OPTIONS' is forbidden.
TargetSite: Void ProcessRequest(System.Web.HttpContext)
at System.Web.HttpMethodNotAllowedHandler.ProcessRequest(HttpContext context)