VB

  • Thread starter Thread starter pierre.k
  • Start date Start date
P

pierre.k

Hi, first of all, please forgive me if I am posting in a wrong forum.
I'm using Visual Studio .NET 2005 Pro and I am wondering if there
is a way to target win32 platform when compiling a VB project, so that
the application does not need .NET Platform installed on the target
machine (similar to VisualStudio 6). I do not need to use any of the
..NET features. I've been fiddling with the IDE and searching the docs
for a couple of hours to no success.

Thanks in advance
pierre.k
 
Hi,

Not with VB. However, this is NOT different that Visual Studio 6 (and VB),
where you also had to install the VB runtime and other dependencies. C/C++
are a somewhat different story, if you limit yourself to unmanaged code.

--
Richard Grier, MVP
Hard & Software
Author of Visual Basic Programmer's Guide to Serial Communications, Fourth
Edition,
ISBN 1-890422-28-2 (391 pages, includes CD-ROM). July 2004, Revised March
2006.
See www.hardandsoftware.net for details and contact information.
 
If you are writing VB .NET, you'll need the .NET Framework on the target
machines. VS.NET does not compile VB 6.0 code.
 
Thanks for the response, that's what I thought myself :-( Unfortunately
in my case I cannot deploy the .net framework runtime to the target
machines.
The reason I am about VB is the ease with which it can implement a COM
server and sink COM events - something not that easy and
straightforward in C++.
This leads me to another question - can VS2005 and the old VS6 be
installed on a single system without conflicts?
I wonder why MS closed the doors for those writing in VB and not being
able to deploying the .net runtime...
 
pierre.k said:
Unfortunately in my case I cannot deploy the .net framework runtime
to the target machines.

This might be a silly question, perhaps, but - why not?
If it's an installation permissions issue, then you'll have trouble
trying to deploy any COM-based solutions as well.

If your users are running Windows XP, they /probably/ have the 1.1
Framework already!
The reason I am about VB is the ease with which it can implement a COM
server and sink COM events - something not that easy and
straightforward in C++.
Agreed.

This leads me to another question - can VS2005 and the old VS6 be
installed on a single system without conflicts?

Yes. '2005 will probably upgrade your version of MDAC /yet/ again, but
I've not encountered or heard of anything worse (at least not in terms
of "running" them side-by-side.
I wonder why MS closed the doors for those writing in VB and not being
able to deploying the .net runtime...

You never could write VB without installing some sort of Run-Time
library. The Framework is just a much, much bigger one that
additionally supports other languages as well. And, of course, you can
just download the Framework, can't you?

IMHO, until /very/ recently, Our Friends in Redmond seemed to believe
that everybody and their granny had a T3 connection direct to their PC's
so they could download anything and everything they wanted in seconds.
It just never occured to them that people might still use dial-up modems.

HTH,
Phill W.
 
I wonder why MS closed the doors for those writing in VB and not being
Because that is probably a very, very, very small amount of people. As
pointed out, the .NET Framework has been part of the XP SP's and will be
standard on Windows Vista.
 
Hi,
This leads me to another question - can VS2005 and the old VS6 be
installed on a single system without conflicts?
<<

Yes (at least, I've seen no problems).
I wonder why MS closed the doors for those writing in VB and not being
able to deploying the .net runtime...
<<

Take a look here: http://blogs.msdn.com/astebner/articles/574618.aspx

Dick
--
Richard Grier, MVP
Hard & Software
Author of Visual Basic Programmer's Guide to Serial Communications, Fourth
Edition,
ISBN 1-890422-28-2 (391 pages, includes CD-ROM). July 2004, Revised March
2006.
See www.hardandsoftware.net for details and contact information.
 
Back
Top