Support & Learning
Application Development and Deployment
Data Connectivity and Integration
Web Content Management
Get A Free Trial
close mobile menu
Testing & ALM
Improving OpenAccess ObjectScopeProvider for Runtime Connection Config
Phew! That's a long blog post title, but hopefully it clearly conveys what I'm about to show you. In my last post, I talked about where you should set your OpenAccess database connection strings. I showed you how you can define multiple database connections in your web.config (or app.config), simulating the idea of having a unique connection string for DEV, TEST, and PROD environments. So now that you have your connection strings set in a way that is easy to maintain, you need a way to easily to tell your OpenAccess persistent classes to use a specific connection at runtime. Let's look...
January 09, 2009
Understanding Where to Set Connection Strings in OpenAccess
When you start working with OpenAccess, one of the first tasks you're going to face is the need set a connection string to your database. And odds are, the connection string you're going to start with is not going to be the connection string your going to use on your production server. It might not even be the connection string your going to use in your test environment. Point is, you need to be able to store multiple connection strings and easily "cue" OpenAccess to use the correct connection details at runtime. Fortunately, OpenAccess makes this easy. UNDERSTANDING OPENACCESS CONNECTIONS First things first:...
January 07, 2009
Showing RadToolTip on RadInput input error
December 12, 2008
Easily persist RadTabStrip Selected Tab using client-side API
While working on a recent "real" project for Telerik, I used the RadTabStrip for ASP.NET AJAX to provide users with a list of content they could navigate. It was simple enough. A RadTabStrip with a few tabs, a RadMultiPage holding each tab's content, and content on each pageview that linked to new pages in the website. With very little effort, I had a rich, tabbed interface that worked completely cross browser. But then during beta testing, a tester reported a bug: if they navigated to a new page by clicking on content in the TabStrip, then clicked their browser's back button,...
December 05, 2008
Before we can begin any serious coding of the recently introduced "dotNetRegister" reference app, we need to define some some requirements. As with any good agile development effort, I want to create a backlog of features that need to be implemented and then prioritize development from there. I even intend to work on this application in sprints, though clearly, as a part time project, I don't expect to have a stellar burn-down rate. ASIDE: If any of these agile terms- like backlog, sprint, or burn-down rate- are unfamiliar to you, I highly encourage you to spend a little time becoming more...
August 26, 2008
Testing & ALM
Latest updates in your inbox
Cooking with ASP.NET Core and Angular
July 26, 2017
Security Alert for Telerik UI for ASP.NET AJAX and Progress Sitefinity
June 29, 2017
Testing & ALM
Getting Started with Progress Test Studio for APIs
July 11, 2017