Web Service code generator from Business.Entities

I have been using Paladin classes in several small prototypes in VS2003

I have also created one web service that extend the posibilities to use the entities classes.

Now I try to migrate one of such prototypes to VS2005/Net 2.0. As the database is the same, I have used the previous Net 1.1 WebService, just including it as datasource for WinForms or ObjectDatasource for WebForms. As far as I have tried it is working right.

I have several databases more, so I pretend to generate the Web Service methods from the metadata of the business.entities assembly. In this way I can obtain the names of the entities from the assembly and build the similar and easy methods I need now, without being force to write them by hand.

I have the next problem in the macro:

Path_Assembly = "C:\0_PALADIN\Northwind\Business.Entities\Implementation\bin\Business.Entities.dll

MyAssembly = System.Reflection.Assembly.LoadFrom(Path_Assembly)

For Each t In CurrentAsm.GetTypes

...Get Types data...

Next

The macro does not obtain the GetTypes and wait infinite no giving any error.

If I tried the same Paladin assembly with IL DASM, I can see all the types.

If I tried another no Paladin assembly in my macro I can also obtain the types.

Any sugestion?

 

 

 

 

Take note that Paladin is not tested on .NET 2.0 and if not mistaken, it will not run properly.

All Entity assemblies references Paladin.Core.dll, so if that's missing, that could be the cause.

You may want to use Reflector to dis-assemble Paladin instead. Looks neater and exposes you to many unmentioned features

I use Paladin only in version Net 1.1. The reason to create the web service, (also in Net 1.1), is to use Paladin through the WS in Net 2.0 as a datasource, and this is working without any problem, giving you databind functionality.

I can write the web service manually, bit I tried to do it automatically, generating the code from one macro. Then is when I found out the problem about the types of Paladin using reflection.

I can not add the Paladin core reference in one macro.

But this is not a Paladin problem, I will try it another way.

Thanks for your attention

Paladin is working fine in .NET 2.0 for me. Remember .NET 2.0 is completely backward compatible (and Microsoft would be shooting themselves in the foot if it wasn't)