vb.net and build platforms

  • Thread starter Thread starter pete
  • Start date Start date
P

pete

Hi,
I have brought VB.Net and I am following the training exercise,"Lucky7".
The problem I have, is that the only build platform available is .Net.
How Do I add other platforms, like xp Pro and XP home, etc....
Thanks :)
 
Hi,

You need the dotnet framework installed on any machine you use vb.net
program on.

Ken
---------------
 
Thanks for the reply Ken.
I am new to VB. I thought that VB.net is the latest version of VB.
Does this mean that this version of VB can not be used to make programs
that can run on normal XP machines?

If so, it looks like I have brought the wrong program!
If this is the case, what program do I need, to be able to make VB
applications to run on any Windows machine?
 
The .NET framework comes as part of VB.NET, you simply need to ensure its
loaded on the target machine. You can do this manually or when you add a
setup project to your solution.

--

OHM ( Terry Burns )
. . . One-Handed-Man . . .

Time flies when you don't know what you're doing
 
Thanks for the reply Ken.
I am new to VB. I thought that VB.net is the latest version of VB.
Does this mean that this version of VB can not be used to make programs
that can run on normal XP machines?

If so, it looks like I have brought the wrong program!
If this is the case, what program do I need, to be able to make VB
applications to run on any Windows machine?

When it comes to any version of VB higher than 3, you will ALWAYS need some
sort of supporting files which are NOT guaranteed to already be present on
EVERY version of Windows. With VB6 and below, you had to distribute the VBx
runtime. With VB.NET (and any .NET language), you have to distribute the
..NET framework.

All the applications you create with VB.NET will be .NET applications. You
cannot create a 100% standalone app with VB.NET.
 
* "pete said:
I am new to VB. I thought that VB.net is the latest version of VB.

Yes, that's true.
Does this mean that this version of VB can not be used to make programs
that can run on normal XP machines?

It can. .NET applications can run on Windows 98 and better. There are
some classes that require a certain Windows version, but in general
applications that are compiled for .NET will run on machines that have
the .NET framework installed.
If so, it looks like I have brought the wrong program!
If this is the case, what program do I need, to be able to make VB
applications to run on any Windows machine?

On /any/ Windows machine? That's currently not possible and I doubt it
will ever be. Windows 95 and earlier are not supported.
 
Thank you for all of the replies :)

I have found the .net framework download, 103Mb Phew!, that's a big file to
re-distribute.
Right, I have installed this file onto another pc, But the file will not run
on the other pc, only on mine.

A error message appears:-
C:\windows\Microsoft.NET\V1.1.4322mscorwks.dll could not be loaded.

any clues?
 
Note this is a XP home machine, I can not find the IIS option in add/remove
windows programs.
 
Hi Pete,

The 103 mb file you donwloaded is the Development FrameWork that should be
installed on your development machine.

In order to run your programs in other machines, you need to redistribute
the dotnextfx, which is about 23 mb. this is the runtime files on the client
machine.

Manny
 
IIS is not included with XP Home. Only Windows 2000 Pro and XP Pro. (and of
course the server versions)
 
Thanks for the link Greg.

So if I understand correctly,

1, IIs can not be installed on a xp home machine .
2, ISS is required to install .net framework.
3, xp home can not run programs, written, in visual basic.net.
 
yet another option:

Visual Web Developer 2005 Express Edition (still in beta)

"Visual Web Developer 2005 Express Edition includes support for creating and
consuming Web services, validating applications across multiple browsers,
and easily running and debugging your code using the built-in test Web
server, without having to have access to IIS."

http://lab.msdn.microsoft.com/express/vwd/default.aspx
 
#1 correct
#2 no, IIS is required to develop ASP.NET programs only (with the cassini
web server being the exception to that rule)
#3 if you install the .net redistributable 1.1 package you can run any
vb.net app (or any other .net app for that matter)
 
Cool, now how do get an "windows" application, made in visual studio.net, to
work on a "windows" XP Home Machine??

No where on the box or in the help files does it mention, (that I can find),
that you will not be able to run VB programs written in visual studio.net,
on a XP home machine.
 
pete,

There are two kinds of VB.NET programs.

1. ASP.NET programs where the code-behind is written in VB. These programs
require some kind of IIS server to run.

2. Windows Forms programs. These are more like your classical Windows
programs and do not require IIS.

If you are programming for Windows Forms, for the most part you can just
take the bin directory from your project, copy it to a target machine where
the .NET framework redistributable is installed (It is a part of the OS on
the Tablet computers and will be a part of the OS on all new Windows
platforms) and it will run. If you add references to other assemblies
(.dlls) such as third party controls, you can put these dlls in the bin
directory also and it will work just fine.

The deployment model for .NET is FANTASTIC.

-Sam Matzen
 
Greg your are a genius!
I can now run the application on XP Home.
Many thanks for your patience.
 
See my reply on other thread.

Also note: if you include any of the ADO.NET "features" in your application
you'll need to redistribute yet another package. :)

At least MDAC 2.7 (latest is 2.8)

http://msdn.microsoft.com/data/Default.aspx


You should know now that the VB.NET Standard Edition (which I assume is what
you have) does not allow you to create "class" libraries. (At least not
without a trivial hack). Since you are just learning, I wouldn't let this
concern you too much. The Professional version is quite a bit more $$$. And
Visual Studio 2005 will be here sooner or later. That's when I would think
about upgrading.

Greg
 
Back
Top