That was until I tried .Net... Oh my god.
I've been using Weblogic Integration lately. It has it's problems, but it's actually quite ok as long as you don't stray to far from the path defined for you.
So I needed to use Visual Studio. F*ck me! One might think that a development tool and a framework "built with support for Web services from the start" would actually have support for web services... And it does, almost. BUT IT DOES NOT HANDLE INCLUDE! Shure, import works, but do you have any idea how annoying it is to refactor 10 xsds from include to import. That changes all the namespaces which in turn changes all the XML beans that BEA generates. Also, quite naturally that ruins all the transformations so one has to do them all over again. Not that it's hard work, but it's annoying.
Oh, and one would think that .Net would handle all the basic datatypes of XML Schema, such as token. Well think again!
The code editing in Visual Studio is... lacking, in each and every way. Better than Workshop but hey, that doesn't really say much does it.
Damn I miss IntelliJ Idea.
Oh. Visual Studio is missing one thing that makes it almost unusable. Proper support for CVS! Don't come writing about third party implementations that wraps CVS in SourceSafe like manner, because that's like wrapping your jewelry in used toiletpapper with barbedwire hooked up to the unforgiving end of electricity transformer station. I'm not going near that, not now, not ever.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment