Ice 2.1.0 and vb.net question

in Help Center
I've just installed the MSI for Ice 2.1.0 on Visual Studio .NET 2003 and could not find the icecs.dll that is referred to in the demos. I also did not see the slice2vb or slice2cs executables in the c:\Ice-2.1.0\bin directory. Is there another distribution that must be installed to obtain these files?
Also, from a compatibility perspective, will a VB.NET client which was written and compiled with ice 2.0.0 work against a (java) server which is running with ice 2.1.0 assuming the class definitions have not changed?
Thanks,
Mayer
Also, from a compatibility perspective, will a VB.NET client which was written and compiled with ice 2.0.0 work against a (java) server which is running with ice 2.1.0 assuming the class definitions have not changed?
Thanks,
Mayer
0
Comments
There are no problems with running an Ice 2.0 client with an Ice 2.1 server or vice versa, regardless of the language mappings being used for the client or the server. The Ice protocol has not bee changed since version 1.0, with the only exception being the marshaling for objects by value (changed in version 1.1) and facets (changed in version 1.4).
These files belong to the Ice for .NET, C# Development and Visual Basic Development features of the installer. In order to install these features successfully you must run the installer from a user account with Administrator privileges. As well, the Microsoft .NET 1.1 Framework must be installed on the target computer. These are requirements because the installer needs to install the Ice assemblies in the global assembly cache.
Thanks again,
Mayer
I'm not positive but I think that the same requirements existed for the 2.0.0 installer and I suspect that the install would fail if the conditions weren't met. That said, the 2.1.0 installer will not show you an error dialog if the conditions for Ice for .NET are not met. There is a note on the "Setup Type" section of the installer wizard however. A more obvious indication will most likely be added in an future release. I apologize for any confusion.