August 2004 - Posts
Just a few more hours before my vacations starts! This will be the first time since February 2003 I’ll be “out of office”. We’ll be moving to our home next week and probably spend the next few weeks to settle in. So this will keep me from blogging for a while. Hopefully I can free up some time to read more on Software Factories and finish my follow-up post concerning developer creativity in a Modern Software Factory. On top of that I really need to get my hands dirty on XAML.
By the end of my vacation I’ll be prepared to make the second most important decision in my life (thus far). Stay tuned…
There isn’t much for me to add, you know what they say about pictures. Get Xamalon beta 5 to do your XAML on .NET V1.1.
Natty Gur blogged abaut the “Error while trying to run project: Unable to start debugging on the web server.” Error.
Open your Internet Information Services manager and from the [your machine]/Web Sites/ Default Web Site node select the virtual folder which stores your project. Right Click and select Properties to select the ASP.NET tab page. Make sure the correct version ASP.NET Version is selected.
I have VS.NET 2003 and 2005 beta 1 running side-by-side on my box and noticed ASP.NET Version 2.0 is targeted by default, even for VS.NET 2003 projects.
Why do I need this hack to get my RowState the way I like it? Not to mention what got me into this mess in the first place :D
private DataSet WhyDoINeedThisHack(DataSet source)
// create a copy of the schema
DataSet destination = source.Clone();
foreach(DataTable table in source.Tables)
foreach(DataRow row in table.Rows)
// this sets the rowstate to added, unless we AcceptChanges
I'm still in search for the perfect aggregator. Could it be Sauce Reader? See for yourself!
Via Derek Hatchard
The Neo roadmap has been updated with some pretty exciting features. A little while back I submitted a prototype demonstrating support for Enterprise Services in Neo. I blogged some of the details here. While .NET 2.0 supports a superior light weight transaction manager, Enterprise Services are here to stay for a little while longer. I strongly believe this could ease the adaption of Neo in Enterprise Applications. More importantly, to provide an integration layer for legacy components. It is being worked on…
I’ll be using a similar concept to implement ContextLogging. More on that later…
Paul Hammant is working on a model diagram generator which eventually will lead to a better user experience.
Planned features are:
- Single table inheritance
- MultiStore (very interesting for some problem areas)
- Start with objects (declarative mapping, which I dislike)
- Improved qualifiers
- Full sorting support
- Schema generation for ‘legacy’ databases
Another Dutch .NET blogger namely Dennis Mulder has been added to our list.
Get the “Dutch .NET Developers Alliance” opml to be imported in your favorite RSS reader here.
Yesterday I commented about XQuery moving forward in favor of XPath 1.0 and XSLT 1.0. Whether this is a good thing or not, Oleg Tkachenko has written a fine article concerning the XPath and XSLT extension, provided by the EXSLT.NET library.
EXSLT is a community initiative to provide numerous of powerful extensions to XSLT, and currently it defines more then 70 extension functions and elements. Extensions are broken down into a number of modules; Common, Datest and Times, Functions, Math, Random, Regular Expressions, Sets, Strings. An interesting side note is that the project is led by Dare himself.
With EXSLT.NET’s current status marked as stable it suggest you see for yourself what EXSLT.NET has to offer.
The XPathNavigator is recommended for methods that accept XML input or return XML as output. .NET 1.x supports a read-only cursor over XML data sources. Though this is about to change in .NET 2.0 with the XPathEditableNavigator in sight. Dare says XQuery is the future and already incorporates pretty much everything what makes XPath 2.0 such interesting technology.
If today has your focus I suggest you give Praj Joshi’s XPath Visualizer a spin; otherwise invest in XQuery.
Seriously, “On the road to Indigo” doesn’t really reflect the importance of the path towards the set of .NET technologies code-named “Indigo”. Indigo isn’t “Just Another Stack” but the infrastructure for developing connected systems.
You should read the when to use what discussions and store the Four Tenets of Service Orientation somewhere on your “headdisk”.
- Service Boundaries are Explicit
- Services are Autonomous
- Services expose Schema and Contract, not Object and Type
- Services integrate using Policy
Make sure you know how to picture Remoting against ES and have a bird’s eyes view on .NET Framework 2.0’s new Web Service Features.
One interesting facet of Indigo is that it’ll finally get rid of the code generation process we know of ASMX. We don’t do code generation – we let the runtime do stack-to-message translations (Don Box).
More Posts Next page »