VFPConversion Blog

This blog is dedicate to the adoption of technologies such as Microsoft .NET or SQL Server in addition to Visual FoxPro. Expect posts on this blog to be fairly technical, as this blog is geared towards developers, testers, and technical decision makers.

Content Area Footer

Wednesday, June 20, 2007
VFP Forms and Windows Vista Aero

VFP has some problems with Windows Vista Aero. (Aero is the rendering style in Windows Vista that makes window headers and borders appear semi transparent). VFP forms have trouble with this rendering style, unless the user is logged in as administrator (which one typically isn't in Vista).

As it turns out, the problem is related to the way VFP sets some of the properties on a window, which cause the window to be created and then change the border style afterwards. The solution to this problem is to change the order in which windows are created and configured.

Calvin Hsia explains how this is done in one of his recent blog posts.

Posted @ 9:16 PM by Egger, Markus ( -

Sunday, June 17, 2007
Are .NET Applications harder to deploy than VFP apps? Not!

I recently saw some messages on messageboards and blogs that seem to spread the rumor that .NET applications are harder to deploy than their VFP equivalents.


A lot of arguments go back and forth about whether VFP or .NET is better. People compare individual commands and programming techniques. While I generally think people need to look at the much bigger picture, one can at least see that there is some validity to those discussions. But deployment?!? Pa-leaaase!

.NET applications are about as trivial to deploy as it gets. Copy the files from the dev machine to wherever you want to run the app, and then.... well, there is no "then". You are done. The app runs. It is as easy as that.

You want to create a real setup? No problem. Create a setup project in .NET, point it to your EXE, and voila, there you have your installer. You want your conventionally deployed application to update itself automatically? Well, you can have that too, with the updater application block. Or better yet: Switch to ClickOnce deployment, which automatically performs updates without the need for any special coding on your side. It is easy, and it works extremely well in the real world (check out our Xiine magazine client for an example - - you can read VFPConversion articles with Xiine these days...).

Of course there are other scenario beyond WinForms apps. But it really gets no more complicated than this. Sure, some applications require an actual setup (such as Windows Services... but then you can't even do that in VFP, so it would be hard to compare), but the techniques discussed here really cover all scenarios.

So there is no argument here at all. You may hate or like .NET, but a discussion about deployment is just a no-go...

Posted @ 12:07 PM by Egger, Markus ( -
Comments (1)








Syndication RSS 2.0 RSS 2.0

All My Blogs:
My personal blogs:
Dev and Publishing Dev and Publishing
Travel and Internat. Living Travel and Internat. Living
Other blogs I contribute to:
Milos Blog (US) Milos Blog (US)
VFPConv. Dev Blog (US) VFPConv. Dev Blog (US)
VFPConv. Dev Blog (DE) VFPConv. Dev Blog (DE)


Blog Archives
All Blog Posts

    February (1)
    November (1)
    October (2)
    April (1)
    March (1)
    August (1)
    July (1)
    June (2)
    March (1)
    January (1)
    December (1)
    November (2)
    October (1)
    September (1)
    August (1)
    April (3)
    March (2)
    February (1)
    January (1)
    December (2)
    November (3)
    October (2)
    September (7)
    August (3)
    July (4)
    June (12)




This Blog is powered by MilosTM Collaboration Components.