.NET VNC Viewer 1.0 Released

[Darius Wey]

<div class='os_post_top_link'><a href='http://dotnetvnc.sourceforge.net/' target='_blank'>http://dotnetvnc.sourceforge.net/</a><br /><br /></div><i>".NET VNC Viewer is a VNC viewer written entirely in C#. It is binary compatible with Pocket PCs (.NET Compact Framework) and Windows desktops (.NET Framework). I write this mainly because other VNC viewers on Pocket PC do not do full screen and rotation."</i><br /><br /><img src="http://www.pocketpcthoughts.com/images/web/2003/wey-20050129-NETVNC.jpg" /><br /><br />This new release has support for both fullscreen and portrait/landscape display modes. The viewer is also able to keep track of session histories. You will need the .NET Compact Framework 1.0 or later (for the Pocket PC) and the .NET Framework 1.1 or later (for the PC) for .NET VNC Viewer to function correctly. More details on the application can be found <a href="http://dotnetvnc.sourceforge.net/">here</a>.

[ctmagnus]

Very nice! This scrolls about as fast as the LogMeIn client on the Pocket PC, but as with all other VNC viewer/server combinations I've tried, there is still some visual lag on this one.

[powder2000]

I like! As long as I can see the lower bar and bottom right control panel on xp, I'm very satisfied.

[alabij]

could someone please point me in the direction of how to use a VNC app both server and client.

Thanks

[Menneisyys]

could someone please point me in the direction of how to use a VNC app both server and client.

Thanks

Installing the VNC server for Windows, http://www.realvnc.com/v4/winvnc.html#1 (I recommend RealVNC for Windows).

Usin the VNC client on your PDA: there're numerous threads on it, use the forum search option.

[Dermot81]

Is this faster than the TS client?

[Vincent M Ferrari]

Judging from the homepage of the program, it isn't bad, but it doesn't appear to support scaling the screen down to full size view on a qvga screen.

Gotomypc does do this which allows you to scale the screen down, see what you want to see at a glance, and then zoom in to what you want.

I think that's a killer feature...

[rudolph]

Judging from the homepage of the program, it isn't bad, but it doesn't appear to support scaling the screen down to full size view on a qvga screen.
...[snip]...

Nope, it doesn't, but it's a planned feature. There's a todo list on the product page, and client/server side scaling is on the list.


Is this faster than the TS client?


I found the TS client is actually faster. I wish MS would improve it though, and add full-screen and 16-bit support to it though.

[Ed Hansberry]

Is this faster than the TS client?
no. if you have access via a TS server/remote desktop, use that. VNC is good for Win2K and XP Home though.

[PDANEWBIE]

Does the VNC client allow you to connect on another port? I can't stand that TS only allows 1 port connection.

[Dave Beauvais]

Does the VNC client allow you to connect on another port? ...
Yes; just put the port number you wish to use after two colons. ( Aside: Why all the VNC viewers violate the established convention of putting a port number after a single colon is beyond me.) If you wanted to use port 63982 instead of the default of 5900, you'd type host.example.com::63982.

[Mr. PPC]

Does the VNC client allow you to connect on another port? I can't stand that TS only allows 1 port connection.

You may not know this, but you can modify the TS port as well.

[Dave Beauvais]

You may not know this, but you can modify the TS port as well.
Yes, but the Pocket PC's Terminal Services Client doesn't allow you to specify the port; it will only connect to the default 3389. On the desktop Remote Desktop or TS Client, you can specify any port using the standard convention of [host]:[port]. If you know of a way to specify the port number on the Pocket PC, I would be grateful if you'd share! :D

[PDANEWBIE]

Yes I would love for there to be a port deisgnation on the Pocket PC side.

[Janak Parekh]

(Aside: Why all the VNC viewers violate the established convention of putting a port number after a single colon is beyond me.)
Because VNC has a "display number" convention, i.e., hostname:2 is the second "exported display" from a server (host). That is used to determine the initial port number, but the third parameter overrides it.

--janak

[jchybinski]

You may not know this, but you can modify the TS port as well.
Yes, but the Pocket PC's Terminal Services Client doesn't allow you to specify the port; it will only connect to the default 3389. On the desktop Remote Desktop or TS Client, you can specify any port using the standard convention of [host]:[port]. If you know of a way to specify the port number on the Pocket PC, I would be grateful if you'd share! :D

You can use the latest version of Tweaks2K.net to change the TS port number on the PPC client - John

[Dave Beauvais]

Because VNC has a "display number" convention ...
Yeah, I know, but why couldn't they use the two colons for their display number? Rhetorical question only. :)

[theipaqlover]

does anyone have a link to a good VNC server implementation for windows XP that works with this .Net Viewer?

Thanks

George.

[ctmagnus]

I've been using it with UltraVNC (http://ultravnc.sf.net) with no issues to speak of. However, there are a few warnings on the .Net viewer's site regarding versions of UltraVNC that have issues with this viewer, so it's probably best to take those into account before you download a particular version of the server.

[ctitanic]

You may not know this, but you can modify the TS port as well.
Yes, but the Pocket PC's Terminal Services Client doesn't allow you to specify the port; it will only connect to the default 3389. On the desktop Remote Desktop or TS Client, you can specify any port using the standard convention of [host]:[port]. If you know of a way to specify the port number on the Pocket PC, I would be grateful if you'd share! :D

You can specify any port for the PPC TS Client, using a registry hack included in Tweaks2k2 ;)

[Dave Beauvais]

You can specify any port for the PPC TS Client, using a registry hack included in Tweaks2k2 ;)
True, but that's a global thing. Most of the TS or Remote Desktop connections I make use the default port 3389, but a couple require a custom port. It would be nice if Microsoft would allow connection-specific port selection as they do for the Remote Desktop clients on desktop PCs. Oh well, a guy can dream. :)

[ctitanic]

You can specify any port for the PPC TS Client, using a registry hack included in Tweaks2k2 ;)
True, but that's a global thing. Most of the TS or Remote Desktop connections I make use the default port 3389, but a couple require a custom port. It would be nice if Microsoft would allow connection-specific port selection as they do for the Remote Desktop clients on desktop PCs. Oh well, a guy can dream. :)

No, that's ok, you can dream :D and now you are going to dream better knowing that it's possible to change the default port :D

[pacemkr]

"written entirely in C#."

Thats the part that caught my eye.
Now don't hold the following statement as a fact, but to me C# equals great programs. With C++, for example, most of my time is spent getting things to work and dealing with the innumerable nuances of the language. With C# its just hassle free, you can focus on making better user interface, optimization, more functionality, in one word better software. C# is just... gooood. :lol:

I dont know if this is off topic, but that was my reaction to the news. :wink:

[gibson042]

"written entirely in C#."

Thats the part that caught my eye.
Now don't hold the following statement as a fact, but to me C# equals great programs. With C++, for example, most of my time is spent getting things to work and dealing with the innumerable nuances of the language. With C# its just hassle free, you can focus on making better user interface, optimization, more functionality, in one word better software. C# is just... gooood. :lol:

I dont know if this is off topic, but that was my reaction to the news. :wink:
I thought that was really cool too. And I am just blown away by "binary compatible with Pocket PCs (.NET Compact Framework) and Windows desktops (.NET Framework)." Now THAT is what .NET is all about.

[pacemkr]

"written entirely in C#."

Thats the part that caught my eye.
Now don't hold the following statement as a fact, but to me C# equals great programs. With C++, for example, most of my time is spent getting things to work and dealing with the innumerable nuances of the language. With C# its just hassle free, you can focus on making better user interface, optimization, more functionality, in one word better software. C# is just... gooood. :lol:

I dont know if this is off topic, but that was my reaction to the news. :wink:
I thought that was really cool too. And I am just blown away by "binary compatible with Pocket PCs (.NET Compact Framework) and Windows desktops (.NET Framework)." Now THAT is what .NET is all about.

Yep, makes programming a lot more efficient.

[Darius Wey]

Just a heads-up that .NET VNC Viewer has been updated to v1.01.10. Updates include:

* Client-side scaling implemented.
* Fixed a problem with Smartphone key input mode which prevents the viewer from going back to mouse mode after exiting extended input mode.
* For Smartphones, the back soft key is now backspace even not in key input mode.
* Improved the code for painting.
* Made adjustments to thread priority to provide a more responsive UI.
* Added "Shift Down" and "Shift Up" to the "Keys" menu.
* For Smartphones, added an option to send the mouse location to the server when the cursor is idle.
* Fixed a bug on Smartphones that would cause the right mouse button to not properly function after exiting full screen mode.

[Kowalski]

programming in c# is realy fun, but there are some drawbacks about programs written in c#. the first shortcomming is performance, but i advise you to install the latest CF service pack.

you will notice the improved performance

[Darius Wey]

Just a heads-up that v1.0.1.16 was released yesterday. New features include:

- Server-side scaling and single window mode implemented.
- On a PPC or a Smartphone, now the viewer calls into the connection manager to initiate a network connection (e.g. GPRS) before connecting to the server. From now on the viewer is not P/Invoke-free anymore.
- Added an icon.
- Added an option for users to choose whether to update the screen ASAP or in a batch.
- Added a sample build script.
- Fixed a bug that would hang the viewer if the connection is terminated unexpectedly.

[kedlm]

I have a CE.NET 5 device (Denso BHT-400) that runs the program, but gets an error
when you try to connect to a machine:
Error
vncviewer.exe
MissingMethodException
NetworkConn:Est+0x12
conn:EstNetworkConn+0x3e
Conn:Run+0x14
App:NewConn+0x21
App:Main+0x3e

This device has a wireless card that is already connected (always is) to a LAN.
Is there an easy fix to this problem?

Thanks,
Mike

[james048a]

Hi everyone,
Im new to this forum, i just picked up the Cingular 8125 last friday, since all the bosses got the Blackberry 8700 units, i had to upgrade mine. I went with the Cingular 8125 for many reasons, one is that it is not as wide as the other pda's, slide out key pad. Another is it came with excel, word, powerpoint, pdf reader, and so on. Plus i want to be able to remote log into our server at work and my workstation to check status of tape back ups and other minor things. I normaly use a laptop, but there are time when i dont have wireless access.

Now on to my question, I have been tring different software on my pda and the only one i got working is Logmein. I'd like to use VNC or z2 remote2pc software. I currently have VNC on most of the computer at our office. But i cant get the VNC to work on the PPC. Im not sure if i set it up right. Our office is behind a symantec firewall/vpn 100. Is there a setting on the firewall that i need to check or change to get my 8125 to vnc in?

Thanks for any info
James