Ross, No standard VNC Server release has ever used the .NET CLR. Some parts of .NET do use COM, which there may be compatibility issues with with very old VNC Servers (VNC 3.3 series), and any third-party software based on VNC 3.3.
Can you describe the problem you are seeing and what version of VNC you are using? Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Ross MacGillivray > Sent: 17 December 2004 04:42 > To: [EMAIL PROTECTED] > Subject: Conflict Between VNC Server and .NET Framework > Common Language Runtime v1.1 > > I installed VNC server at a business client's site on a > Windows XP machine a > few weeks ago, and it functioned well until recently. > > The business client then installed Quick Books Pro 2005 > client-software on the > same machine with the VNC server. > > The Quick Books Pro 2005 client-server model seems, > apparently, to uses the > .NET Framework Version 1.1 Common Language Runtime (CLR) > > Are there any conflicts between the VNC server, and .NET > Framework CLR v1.1? > > Has anyone test a VNC server on Windows XP with the .NET > Framework v1.1 and an > application that actually uses the .NET > Framework, in this case Quick Books Pro 2005 (multiuser, i.e. > Client-Server) > > /Ross > > [demime 1.01d removed an attachment of type text/x-vcard > which had a name of Ross MacGillivray.vcf] > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
