I was writing my own custom configuration class to reduce the amount of <appSettings> in my code, but also to make sure the values were type safe. I wrote a simple test application to try this out. 1: class MyConfigurationTestConfiguration : System.Configuration.ConfigurationSection 2: { 3: private static MyConfigurationTestConfiguration settings = ConfigurationManager.GetSection("MyConfigurationSettingsConfiguration") as MyConfigurationTestConfiguration; 4:  5: public static MyConfigurationTestConfigurat... [More]

Nothing to complex this time, just for reference really. Sometimes you want a simple button to just go back to the previous page. All you need is: <asp:Button runat="server" Text="<%$Resources:MyResources,Back%>" OnClientClick="javascript:history.back(); return false;"/> The reason I'm using an ASP.NET Button is purely for the Localization functionality, so you can use with with HTML controls as well

We tend to use a virtual machine per external client so that we can keep things nicely separated. We can then easily add people to a project by giving them a copy of the virtual hard disk and they can be up and running in minutes (once they’ve renamed the guest machine name to avoid IP conflicts!) That worked fine until we started using TFS, where it would moan that the workspace doesn’t exist because its now a different user accessing TFS. After some digging i found the answer was to edit the following file: C:\Documents and Settings\[USER NAME]\Local Settings\Application Data\M... [More]

When trying to connect to TFS 2008 on VS 2008, I had this error: The path xxx is already mapped in workspace xxx It turns out that when using my VPC, it was cloned incorrectly. Someone else had created a workspace using their credentials, cloned the VPC for my use and then when I logged on using the same account name, I got this error message. The way to allow you to continue is to close VS 2008 and then rename the settings file with a .bak extension located at: C:\Documents And Settings\<current user>\Local Settings\Application Data\Microsoft\Team Foundation\2.0\Cache\VersionControl.... [More]

Recently, I’ve had to interpret some user input and then place this input into an XML file for processing by BizTalk Server 2006. Unfortunately, BizTalk Server 2006 likes you to encode characters using their XML equivalents. Let me explain.. Background This can seem quite easy using the System.Xml.XmlSerializer, with its ability to automatically generate XML and escape invalid characters for us. There are problems though. Here is a template class: public class TestClass {     public string Element1 { get; set; }     public string Element2 { get; set; }     public string Element3 { get;... [More]