how to not use VB.net

  • Thread starter Thread starter Alain Roger
  • Start date Start date
A

Alain Roger

Hi,

I have visual studio 2005 and i need to create a VB application.
However, i do not want to use dotnet features because it will force me
to delivery also the dotnet framework to each application user.

how can i be sure that components i used in my application are not from
dotnet package ?

thanks a lot,

Alain
 
I have visual studio 2005 and i need to create a VB application.

.... don't write it in VB.NET.
Write it in VB6 instead.

They aren't "features"... they're a necessity in VB.NET applications.
Any .NET app needs the CLR to run, which is part of the .NET Framework,
which as you know, needs to be installed on the target machine.

If you want to write an app that doesn't need the .NET framework, then
learn VB6 or C++ or Cobol or Pascal or Fortran or PHP or C or .....
etc.

Of course there will be people who contribute to the thread saying that
its possible to pack the framework with your application (which it is),
its not very viable for most developers. There is software around that
can do it for you. But I think it costs over $10,000 from memory...
 
Steven,

Right text but maybe next time to Add.
If you want to write an app that doesn't need the .NET framework, then
learn VB6 or C++ or Cobol or Pascal or Fortran or PHP or C or .....
etc.
Click to expand...
Which needs all there own version bounded runtime and probably some extra
DLL to distribute.

Cor
 
Alain said:
I have visual studio 2005 and i need to create a VB application.
However, i do not want to use dotnet features because it will force me
to delivery also the dotnet framework to each application user.
Click to expand...

The only way to do this is to write "UnManaged" code in C++ (or,
/possibly/, C#). There is *no way* to avoid the Framework if you're
using Visual Basic.

Regards,
Phill W.
 
Phill,
C# requires the Framework also. I suspect you are thinking C#'s unsafe code.
Unsafe code is still managed code.

--
Hope this helps
Jay B. Harlow [MVP - Outlook]
..NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley - http://www.tsbradley.net


| Alain Roger wrote:
|
| > I have visual studio 2005 and i need to create a VB application.
| > However, i do not want to use dotnet features because it will force me
| > to delivery also the dotnet framework to each application user.
|
| The only way to do this is to write "UnManaged" code in C++ (or,
| /possibly/, C#). There is *no way* to avoid the Framework if you're
| using Visual Basic.
|
| Regards,
| Phill W.
 
VB.NET requires the .NET framework.
There is no way around that.
If you don't want to require the .NET framework then you shouldn't be
developing with the .NET framework. However, these days pretty much every
language has some kind of library that must be distributed along with it...
 
Phill W. said:
The only way to do this is to write "UnManaged" code in C++ (or,
/possibly/, C#). There is *no way* to avoid the Framework if you're using
Visual Basic.

Regards,
Phill W.
Click to expand...

But I use Visual Basic and there is no Framework. Visual Basic has been
around for years. I think you meant Visual Fred

GalenS
 
Galen said:
But I use Visual Basic and there is no Framework. Visual Basic has been
around for years. I think you meant Visual Fred
Click to expand...

I was, indeed, referring to Visual B-blunt (now I've actually tried this
latest "offering", even "B#" isn't appropriate).

However, you /cannot/ integrate VB "Proper" (that's v6 or earlier) with
Visual Studio 2005 - they are totally disparate products.

If you use the "Visual Basic" that comes with VS'2005, you will be
writing Managed Code that requires the 20MB+ Framework.
If you are writing in VB "Proper", you will be writing unmanaged code
that only needs around 6MB of Run-Time libraries but which is considered
Dean and Buried by Our Friends in Redmond.

Regards,
Phill W.
 
You can't use VB without its runtime or .net toolkit

It uses it to draw windows, paint controls, communicate with the low-level
stuff in windows etc.

You would have to write this program in C or Assembler and make sure (if in
C) it is UNMANAGED and there is only ONE code file
 
Back
Top