Deploying VB.net programs by just copying *.exe

[C]

In what cases can one deploy a VB.net program by just copying the
*.exe file? Since Windows XP and Vista have all the .net framework, it
should not require very much else.

 

[Tom Shelton]

In what cases can one deploy a VB.net program by just copying the
*.exe file? Since Windows XP and Vista have all the .net framework, it
should not require very much else.

You can't assume that an XP box has the framework - most do, but not all. It
was never part of the release. I think (though, I would have to verify) that
it was part of sp3 - and it has been in windows update for a long time, but
only as an optional update. What it boils down to, is that the existence of
the framework on an XP box is not guarenteed.

Vista shipped with the 3.0 framework - so if your using and 3.5 features, then
you will need to make sure they have the 3.5 framework installed.

 

[C]

You can't assume that an XP box has the framework - most do, but not all. It
was never part of the release.  I think (though, I would have to verify) that
it was part of sp3 - and it has been in windows update for a long time, but
only as an optional update.  What it boils down to, is that the existence of
the framework on an XP box is not guarenteed.

Vista shipped with the 3.0 framework - so if your using and 3.5 features,then
you will need to make sure they have the 3.5 framework installed.

As a beginner I intend to use only Visual Basic Express 2008, and
mostly the common and simpler features. Will it then work on Vista
without any packaging? And may be XP also?

 

[Miro]

well since 2008 uses the 3.5 framework I would assume No.
( Since vista originally was 3.0 )

( unless you change the target framework in the project to 2.0 )

Then you might have a "chance" of hitting computers that have the framework
installed.

Perhaps the question is - why do you want to do a "copy of the exe" verses a
clickonce / or install?

Im assuming you want to run some batch file and "PUSH" the new exe to all
the machines in the office?

Miro

You can't assume that an XP box has the framework - most do, but not all.
It
was never part of the release. I think (though, I would have to verify)
that
it was part of sp3 - and it has been in windows update for a long time,
but
only as an optional update. What it boils down to, is that the existence
of
the framework on an XP box is not guarenteed.

Vista shipped with the 3.0 framework - so if your using and 3.5 features,
then
you will need to make sure they have the 3.5 framework installed.

As a beginner I intend to use only Visual Basic Express 2008, and
mostly the common and simpler features. Will it then work on Vista
without any packaging? And may be XP also?

 

[C]

well since 2008 uses the 3.5 framework I would assume No.
( Since vista originally was 3.0 )

( unless you change the target framework in the project to 2.0 )

Then you might have a "chance" of hitting computers that have the framework
installed.

There are much bigger chances perhaps that I may not be using the 3.5
features in my primitive applications.

Perhaps the question is - why do you want to do a "copy of the exe" verses a
clickonce / or install?

I am fanatic about simplicity. I used VB2 for a long time even after
VB.net came into existence..

 

[Miro]

In reply to your "I am fanatic about simplicity. I used VB2 for a long time
even after
VB.net came into existence.."

try clickonce.

Make a dummy form, publish it with clickonce.
Make sure you set the app to "check for updates" automatically upon startup.

Run the app.

Go make a change and re-publish the app.
Re-Run your application.

You can "use code" to check for updates or whatever.

( I am a fan of clickonce for these simple apps ).

What do you do when you want to update all the exe's by your batch file, and
I am using your 'exe' on my drive. Therefore I have it "locked", and you
will get a write violation will you not?

Miro

well since 2008 uses the 3.5 framework I would assume No.
( Since vista originally was 3.0 )

( unless you change the target framework in the project to 2.0 )

Then you might have a "chance" of hitting computers that have the
framework
installed.

There are much bigger chances perhaps that I may not be using the 3.5
features in my primitive applications.

Perhaps the question is - why do you want to do a "copy of the exe" verses
a
clickonce / or install?

I am fanatic about simplicity. I used VB2 for a long time even after
VB.net came into existence..

 

[Family Tree Mike]

There are much bigger chances perhaps that I may not be using the 3.5
features in my primitive applications.


I am fanatic about simplicity. I used VB2 for a long time even after
VB.net came into existence..

It sounds like you need to make sure you set your build to use .Net 2.0.
This is done on the Compile tab for the project properties. Click the
Advanced button and should see a dropdown that says the target
framework. Change it to 2.0. This will ensure your app only needs 2.0
to run, and not the 3.5 version.

 

[Alex Clark]

In what cases can one deploy a VB.net program by just copying the
*.exe file? Since Windows XP and Vista have all the .net framework, it
should not require very much else.

If you aren't using any of the 3.0/3.5 features and you target v2.0 of the
framework, you stand a better chance of your target machine already having
it installed, but on XP nothing is guaranteed (as Tom correctly points out).
You should be able to choose your target framework when you first create a
new project, and you can alter your desired target framework via the project
properties afterwards.

Vista has 3.0 already installed, so xcopy deployment for a simple 2.0/3.0
app should be fine.

 

[C]

It sounds like you need to make sure you set your build to use .Net 2.0.
  This is done on the Compile tab for the project properties.  Click the
Advanced button and should see a dropdown that says the target
framework.  Change it to 2.0.  This will ensure your app only needs 2..0
to run, and not the 3.5 version.

Thanks. This is the kind of answer I was looking for.

 

[C]

If you aren't using any of the 3.0/3.5 features and you target v2.0 of the
framework, you stand a better chance of your target machine already having
it installed, but on XP nothing is guaranteed (as Tom correctly points out).
You should be able to choose your target framework when you first create a
new project, and you can alter your desired target framework via the project
properties afterwards.

Vista has 3.0 already installed, so xcopy deployment for a simple 2.0/3.0
app should be fine.

Thanks.

 

[Gregory A. Beamer]

In what cases can one deploy a VB.net program by just copying the
*.exe file? Since Windows XP and Vista have all the .net framework, it
should not require very much else.

If you know your clients have .NET, you can copy and paste. You will most
likely want at least a batch file to create the shortcut to the program,
but that is not hard.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************

 

[C]

If you aren't using any of the 3.0/3.5 features and you target v2.0 of the
framework, you stand a better chance of your target machine already having
it installed, but on XP nothing is guaranteed (as Tom correctly points out).
You should be able to choose your target framework when you first create a
new project, and you can alter your desired target framework via the project
properties afterwards.

It seems 2.0 is the default in Project Properties -> Compile ->
Advanced Options.

 

[C]

It sounds like you need to make sure you set your build to use .Net 2.0.
  This is done on the Compile tab for the project properties.  Click the
Advanced button and should see a dropdown that says the target
framework.  Change it to 2.0.  This will ensure your app only needs 2..0
to run, and not the 3.5 version.

I did not have to change it. The default seems to be 2.0 on this
Visual Basic Express 2.0.

This thing they call Express should perhaps be called ultasuperslow.
All versions until VB6 were supersonic in comparison.

 

[C]

If you know your clients have .NET, you can copy and paste. You will most
likely want at least a batch file to create the shortcut to the program,
but that is not hard.

Why not copy and paste as shortcut?

 

[Gregory A. Beamer]

Why not copy and paste as shortcut?

Another good way to create a shortcut. ;-)

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************