Re: I have seen some fat client Dot Net apps

Brian Moelk wrote:

Mike Swaim wrote:
IIRC, (It's been a couple of years), Borland made some assumptions
about the amount of work needed, based on what they thought MS would
provide. Unfortunately, those assumptions turned out to be
greviously wrong, so development of CF support was cancelled.
The same thing's true for WinForms. Previous versions of Delphi used
the MS designers. With .net 2.0 and later, they're no longer
available.

Ok, so the bottom line here is that Delphi developers suffer.

If I go to the store to purchase something and the shipping company
didn't deliver it. I'm upset at the store, not the shipping company.
They should have found someone else to deliver the goods; just like I
can go to the shop down the street.

But as far as I know, they never promised deploying to CF devices. The
closest they came was an early "it doesn't look too hard" based on
betas of the .net framework. Unfortunately, things changed in either a
late beta or with the final release that changed the rules of the game.

Here's what Danny Thorpe (at Borland at the time) wrote about CF _4_
years ago. (Google is your friend)
"Does the CF runtime redistributable provide the debugging and
development support tools that VS uses for CF development? When we
last asked Microsoft, the answer was no. When we asked for the wire
protocol spec for a desktop-hosted debugger to debug .NET code running
on a CF device, the answer was no. The CF SDK installs into the VS
directory tree. How do you install the CF SDK if you don't have VS?
VS's CF SDK also includes device emulators that run on the desktop to
assist with debugging and visualization in the absence of a real CF
device. Are those included in the CF runtime redistributable? No.
CF does have technical entanglements with VS. The runtime
redistributable is a big step forward (used to be, the only way to
install CF on a device was to write a trivial CF app in VS and install
the app on the device - CF was installed along with the app) but there
are still snags on the development tools side. "

And here's some more;
"Borland does not have license to ship the CF assemblies. That makes
it a legal issue.
The technical difficulty is that you have to link against the CF
assemblies. In the CF betas, you could link an app against the desktop
assemblies and run the app unchanged on the CF platform. In the CF
release, they strongnamed the CF assemblies using a different key from
the desktop assemblies. Apps compiled for the desktop will no longer
load on the CF platform. You have to produce a new exe linked against
the CF assemblies in order to run on the CF platform.

And to link against those CF assemblies, you have to extract them from
Visual Studio's install set."

So, when did Borland promise CF support?

--
Mike Swaim swaim@xxxxxxxxxx at home | Quote: "Boingie"^4 Y,W & D
MD Anderson Division of Quantitative Sciences
mpswaim@xxxxxxxxxxxxxx or mswaim@xxxxxxxxxxxxxxxxxx at work
ICBM: 29.763N 95.363W|Disclaimer: Yeah, like I speak for MD Anderson.
.

Relevant Pages

  • RE: Troubles deploying my application
    ... You say that you supply COM interop wrappers - does your install also install and register the COM components? ... One time I succeeded to run the app by making ... > execution and privileges to the required assemblies. ... > CodeBase: ...
    (microsoft.public.dotnet.general)
  • Re: .NET JITTing - AOT compiling - Choice?
    ... > install or at least have a choice.. ... If you know the app is going to be ... Thorpe the jitter compiles about as fast as D7. ... assemblies make a LOT of inter-module calls - System. ...
    (borland.public.delphi.non-technical)
  • Re: vsto auto update security
    ... Is the update stuff handled by a different assembly than the one you've already granted trust to? ... That would require adding trust for that assembly also, assemblies called by trusted assemblies aren't themselves trusted automatically. ... I publish the app and added the manifest file to ... the install and removed filtered out the default manifest. ...
    (microsoft.public.office.developer.com.add_ins)
  • Re: COM interop, pathing from .NET
    ... DLL that is being accessed by a VB6 app. ... Working with Assemblies and the Global Assembly Cache ... you do not have to install assemblies into the global assembly ...
    (microsoft.public.dotnet.framework.interop)
  • Re: Keeping Office 2003 on XP and also installing Office 2007
    ... and that 2007 shortcuts and default app takes over from 2003 ... Office 2003 on the XP platform. ... What do I need to know to install this 2007 successfully so it doesn't ...
    (microsoft.public.windowsxp.hardware)