.NET news » Search results

Search results for query "cur" (69):

Thread Performance: Resource Contention Concurrency Profiling in Visual Studio 2010

Visual Studio 2010 includes new resource contention profiling features that help detect concurrency contention among threads. We walk through a profiling investigation to demonstrate how you can pinpoint and fix resource contention problems in your code.

Inside Recursive CTE's

The Common Table Expression that was introduced in SQL Server 2005 has long been something of an issue for me. I could reproduce the syntax to get what I wanted, but I couldn't honostly say I understood what was going on there. I always need a mental picture to understand something, and that was just missing.

Recently I think I figured out model that helps me work with them and explain how, although different, they're actually analogous to recursion in normal programming.

2010-05-25 10:42:00   Source: Inside Recursive CTE's   Tags: Database

Silverlight Security: Securing Your Silverlight Applications

Josh Twist explains the unique challenges developers face in securing Silverlight applications. He shows where to focus your efforts, concentrating on the key aspects of authentication and authorization.

Parallel and Concurrency Futures for Microsoft Developers

Parallel computing and concurrent programming are rapidly becoming mainstream topics for discussion in the corporate world. These are not new ideas; in fact they've been around for more than 30 years. However, like many long-running computer science concepts, they're only now becoming relevant to mainstream business developers due to changes in both hardware and in the overall computing environment.

Database Concurrency Patterns - SIP and SUP

Take a look at two new patterns to help with database concurrency: SIP and SUP.
2008-07-29 05:02:00   Source: Database Concurrency Patterns - SIP and SUP   Tags: Database

Accessing and Updating Data in ASP.NET 2.0: Using Optimistic Concurrency

Because multiple users can visit the same web page concurrently, it is possible for a user visiting a data modification page to inadvertently overwrite the modifications made by another user. Consider a page with an editable GridView. If two users visit this page simultaneously from different computers and both edit the same row, whomever saves the first will have her changes overwritten by whomever saves the row last. This type of behavior is known as "last write wins" and is the default behavior for web applications..

2008-05-20 19:00:00   Source: Accessing and Updating Data in ASP.NET 2.0: Using...   Tags: ASP.NET

.NET Role-Based Security in a Production Environment

Edit web.config to Update the Data Provider for Shared Hosting with Role-Based Security: SQL Server, ODBC, Active Directory, ADAM, SQLite, MySQL, Access, XML
2008-05-19 05:04:00   Source: .NET Role-Based Security in a Production Environment   Tags: ASP.NET Security

TLS: An exercise in concurrent programming

This article has two aims. Firstly, there are a series of five exercises that detail the process of successfully multi-threading a sequential algorithm with timely progress display in the UI. It also provides an implementation of a thread local storage class which can help realise the performance promise of many-core machines.
2008-05-11 11:54:00   Source: TLS: An exercise in concurrent programming   Tags: Examples Performance

Never Write an Insecure ASP.NET Application Ever Again

Learn to take advantage of the inner workings of ASP.NET's security model to help eliminate security vulnerabilities from your web applications.

Never Write an Insecure ASP.NET Application Ever Again

One of the most important security principles for software development is least privilege. Simply put, least privilege means that an application, process, or user should have the least access to resources required to accomplish a task and no more. By following this principle, even if your application is attacked or a user goes on the payroll of your nastiest competitor, you'll have limited the potential damage. Bottom line: implementing partial trust in ASP.NET is the single biggest thing you can do to make your applications secure.
« Previous1234567Next »