Otis and/or Answer and/or AnyoneWhoKnows--
I am testing out the LLBLGen Templates With Web Service Support (LTWWSS).
Preliminary testing indicates that they do work fine.
I have one question...
In the readme.doc, it shows this edit for the machine.config...
<system.xml.serialization>
<schemaImporterExtensions>
<add name="SchemaImporter" type="yournamespace.SchemaImporter, assemblyname, Version=1.0.0.0, Culture=neutral, PublicKeyToken=44a0feb02394e70a" />
</schemaImporterExtensions>
</system.xml.serialization>
...and my question is...
Note that we one does change the "yournamespace" part and the "assemblyname" part in the same. However, since the <add> node has name="SchemaImporter" and one does not change this, then what happens when the same machine wants to use >1 set of LLBLGen-generated objects using the LTWWSS? Won't there be a collision given >1 <add> node in the machine.config will have the same name="SchemaImporter" attribute setting?
You see, I am assuming that WSDL and other the other great things that VS.NET 2005 runs to create the proxy class does a lookup into machine.config at run-time when the proxy is gettting generate and looks for that "name" attribute and uses it. But, I am thinking, if there is >1 set of LLBLGen-generated objects, then there will >1 <add> node with the same name and I am wondering how WSDL will find the right one to match with the right output.
And so on.
What do you think?
Please advise.
Thank you.
(Post Script -- Yes, I plan to actually try this; but, I thought I should ask regardless because at this end there is A LOT of room for operator error and I will not know if it is LTWWSS or me, and so on.)
--Mark Kamoski
