|
 |
Viernes, 11 de Octubre de 2002 |
As part of my demo in the Web Services DevCon, I wanted to use Apache Axis to show how you can use the stuff we generate from another platform. As I had 20 minutes for the demo I did not want to create manually the stubs, etc, so I built an Eclipse plugin that calls the Apache Axis WSDL2Java Emitter, so I have VS.NET's 'Add Web Reference' functionality in Eclipse.
Some people asked if I planned to post the addin somewhere. I will do it sometime next week, after I polish some rough edges ;).
8:56:54 PM 
|
|
Brian Jepson blogged most of the presentations, but not mine ;), which is understandable because mine was the only 'commercial' presentation. So, I'll give you my unbiased opinion about it ;)
The presentation went quite well. People seemed to like the product, and Chris Sells helped by interrupting me a couple of times asking the audience 'Am I the only guy who think this is really cool?'. His welcomed interruptions were when I showed the database refactoring stuff and just at the end of the presentation, after showing a Java app using the DeKlarit-generated web services layer.
After the presentation, I had an interesting conversation with Sam Gentile about VSIP and related stuff.
8:53:56 PM
|
|
Another good day in the DevCon.
I really enjoyed Clemens Vasters presentation. Most of the presentations explained that the 'right' way to do webservices was to write the XML Schema for your types and the WSDL files for your portTypes, arguing that web services is really about XML and not 'objects' that get magically serialized over the wire.
He was the only one who said that if that's the way most people is supposed to build web services, then there won't be a widespread adoption of webservices. It's just too hard. I completely agree with him.
He wanted to solve that problem, so he built a complete set of SoapExtensions to add most of the stuff that ASP.NET does not provide and it should, like security, session management, logging, etc. He also showed undocumented ways of changing the way ASP.NET generates the WSDL files. Cool.
8:36:00 PM
|
|
We've been writing a lot of Visual Studio .NET add-ins using managed code (in addition to the VSIP stuff, that's written in VC++).
The add-ins are built as assemblies that are loaded by VS.NET using COM-interop. The issue is that when you want to load a new assembly from the add-in, the devenv.exe process (which loads the add-in) looks for the assembly in:
- the GAC
- the \Program Files\Microsoft Visual Studio .NET\Common7\IDE folder
- the \Program Files\Microsoft Visual Studio .NET\Common7\IDE\PrivateAssemblies folder
- the \Program Files\Microsoft Visual Studio .NET\Common7\IDE\PublicAssemblies folder
- the path specified by the DEVPATH variable.
So, it looks for the assembly in every place but in the directory where the original assembly was loaded, which is the way the CLR usually loads assemblies. This means that if you need an additional assembly, you have to install it in one of those places. It's really awkward and annoying.
12:59:50 AM
|
|
© Copyright 2003 Andres Aguiar.
|
|
|
