Re: Can VB 2005 app work on a non-.NET2.0 machine?
- From: "Michael D. Ober" <obermd.@.alum.mit.edu.nospam>
- Date: Sun, 12 Feb 2006 15:13:55 GMT
In other words, in the OPINION of TedF, Microsoft will drop .NET sometime in
the future. In the meantime, VB 6 won't fully support 64-bit versions of
Windows while VB 2005 will.
Mike Ober.
"TedF" <NoReply@xxxxxxxxxx> wrote in message
news:%23SOBlZ5LGHA.2092@xxxxxxxxxxxxxxxxxxxxxxx
willjust that you provide sources for your assertion that .NET will be
dropped
Common sense and me is the source, very reliable source.
.
"Michael D. Ober" <obermd.@.alum.mit.edu.nospam> wrote in message
news:eExHf.7178$5E3.2079@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
You obviously failed logic 101. I never said that .NET will not be
dropped - just that you provide sources for your assertion that .NET
ofbe
dropped, especially since the .NET 2.0 runtime is built into SQL Server
2005.
Mike.
"TedF" <NoReply@xxxxxxxxxx> wrote in message
news:eU3UoZzLGHA.3012@xxxxxxxxxxxxxxxxxxxxxxx
What makes you think .net is going to have longer life
than VB ?
If they dropped VB, the most powerful programming
language, why wouldn't they dump limping, sluggish .net.
It is common sense, MS main intention is to con people
out of their money and waste their time and money.
They are just like little kids that like to kill, ruin, and
hurt things.
"Michael D. Ober" <obermd.@.alum.mit.edu.nospam> wrote in message
news:hWoHf.7053$5E3.764@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Please provide sources to back your contention that ".net is going to
be
dropped very soon anyway." I suspect they are mis-reading the fact
that
Vista and Longhorn will have the framework built in as a "dropping"
Imessage.NET.
Mike Ober.
"TedF" <NoReply@xxxxxxxxxx> wrote in message
news:%23jkS0lpLGHA.3164@xxxxxxxxxxxxxxxxxxxxxxx
You have to carry the 20 MB .net Framework with its many bugs
where ever you go.
We had to carry 1.5 MB and thought it was too much.
My advice is try use different programming language, .net
is going to be dropped very soon anyway.
"ADquestioner" <ADquestioner@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
news:3AA317D5-9E9F-4B2E-A221-A21ED5991AC3@xxxxxxxxxxxxxxxx
Hi.
I've created an application using VB 2005. I've noticed that when
Frameworkinstall
it on other machines, I am required to first install .NET
app).2.0
on
them in order for my application to work (it's a windows forms
itThis
is what I expected.
However, is there a way for me to package my VB 2005 app so that
thiscan
.netframeworkbe
Frameworkinstalled on an XP or W2K3server WITHOUT needing to install .NET
2.0 on them? i.e. can I package just some of the crucial
2.0
dlls into a package that is specific only to my VB app. I ask
andbecause
we have a very tight security policy in our production environment
placeit
would take months to get the testing/QA approval/ChangeRequest in
to
move to .NET 2.0.
Thanks for any advice you can offer!
.
- Follow-Ups:
- References:
- Re: Can VB 2005 app work on a non-.NET2.0 machine?
- From: TedF
- Re: Can VB 2005 app work on a non-.NET2.0 machine?
- From: Michael D. Ober
- Re: Can VB 2005 app work on a non-.NET2.0 machine?
- From: TedF
- Re: Can VB 2005 app work on a non-.NET2.0 machine?
- From: Michael D. Ober
- Re: Can VB 2005 app work on a non-.NET2.0 machine?
- From: TedF
- Re: Can VB 2005 app work on a non-.NET2.0 machine?
- Prev by Date: Re: best place to learn .net
- Next by Date: Re: best place to learn .net
- Previous by thread: Re: Can VB 2005 app work on a non-.NET2.0 machine?
- Next by thread: Re: Can VB 2005 app work on a non-.NET2.0 machine?
- Index(es):
Relevant Pages
|