Re: VB.Net vs. VB 6 - Standalone Apps -- PCTECH

Thanks Craig...I do have VPC running on my new Windows 7 PC, and I
have MSDN, so I have all the OSes. That's a great idea. I currently
have XP running as an environment so I can run VS 6.0 so I can develop
in VB 6.0.

I think I'll start creating virtual environments in the morning.
Sounds like a good thing to do on the last day before a long weekend.
That and developing an evaluation matrix. Virtual environments sound
more fun. :)

On Wed, Dec 29, 2010 at 3:40 PM, Craig Pelkie <craig@xxxxxxxxxx> wrote:

Each client PC that you will run your application on will need the .NET
Framework version that you are targeting loaded onto it.

See this article about "Click Once" deployment, especially the section about
"Application Deployment Prerequisites". In VS2010, you right-click on your
project and select the Publish option to launch the Click Once feature, that
packages up your app for deployment.

http://msdn.microsoft.com/en-us/library/wh45kb66(v=VS.90).aspx

Based on the article, Click Once will check the client PC for prereqs (such
as version of the Framework you're using). I don't know if you can package
the Framework redistributables with the Click Once app. If not, just do a
one-time stand-alone install of the Framework redistributable (similar to
installing a JRE on a PC).

If possible, you might want to see about running Virtual PC (Windows 7) or
Virtual PC 2007 (Vista, XP) to create test environments on your PC of your
client's operating systems. That is, create a VPC for XP, W7, NT, etc. It is
much more pleasant to be able to work with the VPC environment rather than
working directly on a PC for this type of testing.

Craig Pelkie

-----Original Message-----
From: pctech-bounces@xxxxxxxxxxxx [mailto:pctech-bounces@xxxxxxxxxxxx] On
Behalf Of Michael Ryan
Sent: Wednesday, December 29, 2010 12:18 PM
To: PC Technical Discussion for iSeries Users
Subject: Re: [PCTECH] VB.Net vs. VB 6 - Standalone Apps

Thanks for the info Craig...and LTNT. I would need to load the framework on
to each machine though, right?

On Wed, Dec 29, 2010 at 3:02 PM, Craig Pelkie <craig@xxxxxxxxxx> wrote:

This link shows supported Windows operating systems and .NET Framework
versions (4.0, 3.5 (3.0), 2.0) - scroll down to the "Supported Client
Operating Systems" section:

http://msdn.microsoft.com/en-us/library/8z6watww(v=VS.100).aspx

This link shows supported Windows operating systems for .NET Framework
1.1, this will work with the Windows NT 4.0 workstation or Windows NT
4.0 Server operating systems:

http://msdn.microsoft.com/en-us/library/8z6watww(v=VS.71).aspx

This link gets you to the MSFT site for .NET Framework V2.0
redistributable (with links to other versions). You can install these
redistributables on client PCs that require the Framework that you are
targeting. This installs just the run-time support, not development
support (similar to installing JRE instead of JDK/JRE):

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0856eacb-4
362-4b
0d-8edd-aab15c5e04f5&displaylang=en

In VS2010 you can select which version of the Framework you want your
app to target, back to 2.0. There is an option to "install other
frameworks", I don't know if it is possible to target the 1.1
Framework in VS2010. It might be convenient to use VS2008 to target
the 1.1 Framework. You can install
VS2008 side-by-side with VS2010.

It appears that you are developing/deploying a Windows Form app, if
you target Framework 2.0, you'll have good support for all of the
Windows Form features that were available in VB6 (for that matter,
Framework 1.1 also has good support). So it might be worthwhile going
ahead with the .NET version instead of VB6.

In IBM i terms, what you're trying to do is similar to developing an
ILE RPG app at V7.1, then attempting to port it back to a V4Rx
environment. Going backwards, you drop features, in both the language
and the runtime environment. So rather than target Framework 4.0, if
you know you need backwards compatibility, start with a version (2.0)
that is supported on the older operating systems.

Craig Pelkie

-----Original Message-----
From: pctech-bounces@xxxxxxxxxxxx [mailto:pctech-bounces@xxxxxxxxxxxx]
On Behalf Of Michael Ryan
Sent: Wednesday, December 29, 2010 11:09 AM
To: PC Technical Discussion for iSeries Users
Subject: Re: [PCTECH] VB.Net vs. VB 6 - Standalone Apps

Ha! Then just take my original post and substitute JVM for .Net
Framework...search and replace. :)

On Wed, Dec 29, 2010 at 1:35 PM, Joe Pluta
<joepluta@xxxxxxxxxxxxxxxxx>
wrote:

How about... Java?

<grinning, ducking and running>

So I support an environment with multiple versions of client
machines, both hardware and software. All the clients run Windows,
but could be Embedded NT, Embedded XP, XP, and Windows 7. I want to
have a small app that gets some system information. I developed this
in VB.Net with VS 2010. I can't deploy it on the older machines
because the app was developed with .Net 4.0. I know I could develop
with an earlier version of the framework, but that's not going to
help me with the older machines, right? Would I be better off
writing the app in VB 6 to have compatibility? I want to move
forward with the client development, but the multiple Windows
versions and the framework (or lack of) is a stumbling block.

Opinions welcomed. Thanks...

--
This is the PC Technical Discussion for iSeries Users (PcTech)
mailing list To post a message email: PcTech@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/pctech
or email: PcTech-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/pctech.

--
This is the PC Technical Discussion for iSeries Users (PcTech) mailing
list To post a message email: PcTech@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/pctech
or email: PcTech-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/pctech.

--
This is the PC Technical Discussion for iSeries Users (PcTech) mailing
list To post a message email: PcTech@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/pctech
or email: PcTech-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/pctech.

--
This is the PC Technical Discussion for iSeries Users (PcTech) mailing list
To post a message email: PcTech@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/pctech
or email: PcTech-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/pctech.

--
This is the PC Technical Discussion for iSeries Users (PcTech) mailing list
To post a message email: PcTech@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/pctech
or email: PcTech-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/pctech.