Browse by Tags
All Tags »
DotNetX (RSS)
The DbObjMapping feature from DotNetX, is now generating DLINQ "semi"-compatible classes. I say "semi"-compatible, since i still don't like some DLINQ attribute property names, like "AutoGen" and I believe the API is too young, and I’m sure it will
Read More...
Today I came from the ISV Touchdown on Sql Server 2005, and I could' sleep without confirming that the DotNetX DbObjMapping feature (O/R Mapping) was completely compatible with Sql Server 2005. So I started the June CTP installation, and my problems started…
Read More...
This is one of my favourite features of ServiceModel: ServiceBroker! Well, first of all, service broker is the fact of exposing a door in to your services, and redirect (delegate) them to another service. It is not routing, since we're not having any
Read More...
One of the beginning goals of the project where I'm involved now, was the ability to call a service broker exposed in web services, through unmanaged COM code. It looks simple, but services have some policies like a SecurityToken with a KerberosToken
Read More...
Rob Chandler cordially provided a H2Reg distribution license for DotNetX project. With it, the next setup is registering compiled help, and fully integrating DotNetX help files. Txs Rob! Share this post: email it! | bookmark it! | digg it! | reddit! |
Read More...
After working in the dynamic web service proxy generation in the service model, i realized that for windows applications, this is going to be slow. Let's introduce you to the problem: When we configure a soap endpoint in the service model, DotNetX is
Read More...
I'm very excited with this. I finished today the support of SOAP services in ServiceModel. ServiceModel was supporting Remoting, LocalSingleton, LocalSingleCall and LocalWeakSingleton objects until now. The v0.9.7 version is about to introduce two new
Read More...
I'm finishing v0.9.6! This is a big change, since it will modify the base architecture of the framework... I'm doing a presentation in the next days about it, and later publish the bits in the usual place. Stay tuned. Share this post: email it! | bookmark
Read More...
I've been crossing the specified naming convention for the workaround in value type objects used in soap requests, and I must say that this sucks! First, a public field does not comply with fxcop rules, and then, a suffix used for this is just horrible!
Read More...
In the next version (v0.9.6) being currently developed, ServiceModel will also support different service definitions according to the caller. This means that if you wnat to have a specific service implementation to a specific caller, this will be supported.
Read More...
I'm having some doubts about implementing a more complex functionality in the ServiceModel namespace. Its called ServiceContainer. ServiceContainer can be seen as a Service group containers. ServiceLocator class is returning a service based on a contract
Read More...