.Net
Having worked so much with BizTalk, haven't had the chance to create a pure .NET 2.0 web service (automaticly generated WSDL). Much to my surprise, the concept of a "Required Field" is not explicitly supported -- i.e. setting minOccurs = 1, etc. For future reference, some mitigating suggestions are provided by Microsoft here: http://msdn2.microsoft.com/... Feels like going back to the stone ages. Apparently this is much better with WCF bindings...
Posted On Friday, November 30, 2007 8:31 AM | Feedback (1)
Installing a BizTalk App can be quite a challenge. You have options of 1) Manual, lots of documentation needed. But then you were going to create docs anyway, right? This is good when you only need to install it once. 2) BizTalk-generated MSI. This is simple and quick to produce. My main issue is that this is not customizable with regard to the application name and product version (think Add/Remove programs) nor can you specific the installation folder. Another huge problem is that *if* the deployment...
Posted On Thursday, November 15, 2007 8:31 AM | Feedback (0)
I was trying to sovle a sticky problem involving someone else's assemblies but not getting very far -- I needed more information such as line numbers. Usually when you invoke a .NET assembly from BizTalk you need to put it in the GAC and this means you are deprived of the symbols (PDB) which would normally sit beside the assembly in the file system. There are some good posts out there but they seem to relate to .Net 1.0 so they didn't quite work. Here's what you do: You can copy the PDB files directly...
Posted On Thursday, November 15, 2007 8:10 AM | Feedback (1)