Any interest re Microsoft web Service Software Fac

[Kevin G. Watson]

Any one tried to make a meaningful EA model of the microsoft Patterns and Practises, reference implementation source drop. So far I've only managed to get an error message and whole load of build errors and warnings.

There's also an Reference Framewor, and probably some DSL tooling to configure the data layer and Service layers. like workflow and deployments

Regards, and Stay tough
Kevin.
Happy Bank holiday yeah.

[Jeff Odell]

Not exactly sure what you are asking, but I have been able to reverse engineer the Enterprise Library code - both the .Net 1.1 and .Net 2.0 versions.  I can't remember now if I used the Source Code Reverse Engineering or just pointed it at the assemblies, but I think it was the assemblies.  Also, I only imported the public and protected methods and properties as I am treating it as an external library and wanted the library user's perspective.

[Kevin G. Watson]

Hard init!

You answered, we can RE framework - I think I've been eating too many choccie Eggs.

I was thinking how to make it easy to navigate, is there standard.

Kevin

[«Midnight»]

Kevin and Jeff,

I too have done the RE thing with .Net (in my case only 1.1 to date). With the Java libraries things get easier if you partition them into packages, perhaps even in different projects. Then you can import only those you need.

Have you guys (or anyone else, chime in here) managed to resolve the apparent redundancy that the various MS assemblies (i.e System.x.y) show? What I'm talking about is the package structure inside many of the assemblies, that mirrors part of the System pacakge (for example) itself. My thinking is that this is the result of EA attempting to reflect external inheritance and dependancies.

In any case, have anyone found an easy way to produce a 'clean' picture of .Net?

David

PS: I was unable to open the EAP file after importing all but one of the System assemblies (see PPS below). Access 2000 was able to correct the problem, but with considerable trouble. Anyone else have this problem?

PPS: I had a database error (duplicate primary key) when attempting to import the System.DirectoryServices.dll assembly from .Net 1.1.4322). Anyone else seen this? I'll be providing Sparx with whatever (detailed) information I can assemble in case it is an EA issue.

[Eve]

The 'clean' view would be by importing all the libraries into the one root package.  This will prevent the duplicated package structure.

I haven't seen either of the issues you reported either, and I just imported System.DirectoryServices.dll successfully using both import methods.

[«Midnight»]

Hi Simon,

I have repeated the import, and get the problem when EA uses reflection. I've sent detailed results to Aaron.

David

PS: I'm still trying to arrange this on another installation, but have not  yet arranged this with my associates (who have EA).