Asp.net has a wonderful system built in for handling user accounts and roles. The administration interface is encapsulated in a separate web site that can be accessed from within Visual Studio but it is difficult to integrate into the site. This often leads to building a new user administratio...
[More]
Ok we all know SQL2K has lost support from Microsoft. We all know it is marked with "compatibility" issues with Win2k8. But will it run? Microsoft dropped the ball on us here. They shipped Win2K8 before SQL2000. leaving those of us with giant budgets in a pick...
[More]
Not long ago I started working on changing the look and feel of the default WebService documentation that is generated by asp.net. While I demonstrated how to replace the default page template with a custom one I "glossed" over the details of what you can do with it. By using...
[More]
Web Services: they are an easy way to make information accessible or use information from some other site. For example, weather.gov's wsdl. The beauty of web services is that not all web services are .net and we don't have to care. Any web service that adheres to the w3's standards...
[More]
pre {overflow:scroll;} Delegates have been a great help to developers everywhere; coupled with Events they form the basis of every asp.net web application. Check out the page event life cycle, events are firing long before the code written by the sites developer. But what happens when...
[More]
It's no secret, I use SourceForge.net to work on an open source project ObjectHelpDesk.net and most of the code, patterns and nick nacks that I write about come from that project. I also use TortoiseSVN coupled with VisualSVN to manage my source code. Recently, as part of the Generics, I...
[More]
Ok so in the Generics, Interfaces, Providers and You series, Part 1, Part 2, Part 3 & Part 4, we made a flexible system of interfaces to make working with a data access provider model easier. In Part 4, I listed some ideas where there was room for improvement in the interfaces/class that w...
[More]
Now that we have our interfaces we need to make some changes to our existing objects. Back in part 1 we defined an object tree for contact information. For this example, a 3rd parting marketing system is loading new contact information into our data store and management does not want any...
[More]
In part 1 We talked about the web.config and the basic classes to get started with a provider model. Part 2 covered the interface for the data object and the Provider. Now in part 3 we will address the IProviderCollection and the IProviderRepository. Back in part one we added a provider...
[More]
In part 1 we covered the web.config changes and the classes needed to use them. We also created a ProvidersRepositoryGeneric class to load and manage providers. But what good is a repository of providers if there is nothing to provide? While the Provider model can be used for other...
[More]