ArcGIS ADF – Biting the Dust

January 30, 2008

Dave Bouwman writes about how ArcGIS 9.2 ADF does not support curves. We've actually bumped into this issue a long time ago, resorting into converting the curves to a series of points (as Dave suggests). This is but another huge issue with the ADF. As I've said before, this is one horrific development platform. I've started to seriously think about coding a replacement that will work against ArcObjects (at least something that will satisfy my team's needs), but it would take a lot of time which we currently do not posses. One day, though, one day.

Easy Configuration Deployment with MSBuild and the XmlMassUpdate Task

January 18, 2008

I've been looking for the easiest possible way to deploy a web.config file to several different environments. My web.config looks something like this in development: <configuration> <appSettings> <add key="LogEveryRequest" value="true" /> <add key="EnableCaching" value="false" /> <add key="DefaultGisServer" value="" /> </appSettings> <connectionStrings> <add connectionString="UserName=scott,Password=tiger" name="DBConnection" /> </connectionStrings> <system.web> <compilation debug="true"> </compilation> </configuration> I need the ability to change specific values in the test and production (release) environments. For instance, the connection string is obviously different, and I would...

Don’t Seal That Door

January 11, 2008

I've been going over this week's updates, and ran across this post in CodeBetter, that talks about why classes should be sealed by default, only to be unsealed by the 'unsealed' keyword. I couldn't disagree more. I think that you need a hell of a good reason to seal a class, so claiming that most classes should be sealed is a bit seems outrageous to me. I believe it's absurd to prevent extensibility for your classes, and if classes are sealed by default, the result will be, obviously, a lot more sealed classes around. After all, unless you plan...
tags: ,