S
Steve Podradchik
Hi,
In porting a desktop app to the CompactFramework, we're doing OK on
compatibility but we do wonder if folks have solutions for some of the
missing things we need:
1. We need to post data to a Web site in a URLEncoded fashion.
web.HTTPUtility seems missing. How do we do a URLEncode? This must be here
somewhere?
2. We need to upload files to a Web server. On the desktop version, we
used a modified version of some sample code in Help. The sample code uses
the WebClient class which is missing in CF. Ideas?
3. System.Environment.GetFolderPath is used on the desktop app to know
where to put user files
(GetFolderPath(Environment.SpecialFolder.LocalApplicationData)) for example.
Any idea what we should use instead?
4. What's the easiest way to port an entire Access (.mdb) database to a
SQLCe file? I read the previous notes about InTheHand but our database will
be very, very large so I'd rather use SQLCe. Also, does anyone have
thoughts on relative file size and performance?
Thanks, Steve
In porting a desktop app to the CompactFramework, we're doing OK on
compatibility but we do wonder if folks have solutions for some of the
missing things we need:
1. We need to post data to a Web site in a URLEncoded fashion.
web.HTTPUtility seems missing. How do we do a URLEncode? This must be here
somewhere?
2. We need to upload files to a Web server. On the desktop version, we
used a modified version of some sample code in Help. The sample code uses
the WebClient class which is missing in CF. Ideas?
3. System.Environment.GetFolderPath is used on the desktop app to know
where to put user files
(GetFolderPath(Environment.SpecialFolder.LocalApplicationData)) for example.
Any idea what we should use instead?
4. What's the easiest way to port an entire Access (.mdb) database to a
SQLCe file? I read the previous notes about InTheHand but our database will
be very, very large so I'd rather use SQLCe. Also, does anyone have
thoughts on relative file size and performance?
Thanks, Steve