| Author |
Is 16-bit possible in VB.NET
|
|
| Tom Edelbrok 2005-02-25, 8:55 pm |
| We have been using VB6 for a long time now and have many applications. Some
of these applications call an industrial process control API that requires
certain fields to be input as 16-bit integers.
Now we are converting everything to VB.Net 2003 and read that integers are
32-bit and longs are 64-bit. Is it not even possible to make a 16-bit
anymore? I think our API calls (to functions in a DLL) will blow up if we
pass in 32-bit values to arguments requiring 16 bits.
Thanks in advance,
Tom Edelbrok
| |
|
| Almost everybody in this newsgroup is using VB6 or lower. While you may get
a stray answer to VB.NET questions here, you should ask them in newsgroups
devoted exclusively to .NET programming. Look for newsgroups with either the
word "dotnet" or "vsnet" in their name.
For the microsoft news server, try these newsgroups...
microsoft.public.dotnet.general
microsoft.public.dotnet.languages.vb
microsoft.public.vsnet.general
--
Chris Hanscom - Microsoft MVP (VB)
Veign's Resource Center
http://www.veign.com/vrc_main.asp
--
"Tom Edelbrok" <anonymous@anonymous.com> wrote in message
news:qdPTd.4374$hN1.4304@clgrps13...
> We have been using VB6 for a long time now and have many applications.
Some
> of these applications call an industrial process control API that requires
> certain fields to be input as 16-bit integers.
>
> Now we are converting everything to VB.Net 2003 and read that integers are
> 32-bit and longs are 64-bit. Is it not even possible to make a 16-bit
> anymore? I think our API calls (to functions in a DLL) will blow up if we
> pass in 32-bit values to arguments requiring 16 bits.
>
> Thanks in advance,
>
> Tom Edelbrok
>
>
| |
| Ken Halter 2005-02-26, 3:55 am |
| "Tom Edelbrok" <anonymous@anonymous.com> wrote in message
news:qdPTd.4374$hN1.4304@clgrps13...
> We have been using VB6 for a long time now and have many applications.
> Some of these applications call an industrial process control API that
> requires certain fields to be input as 16-bit integers.
>
> Now we are converting everything to VB.Net 2003 and read that integers are
> 32-bit and longs are 64-bit. Is it not even possible to make a 16-bit
> anymore? I think our API calls (to functions in a DLL) will blow up if we
> pass in 32-bit values to arguments requiring 16 bits.
>
> Thanks in advance,
>
> Tom Edelbrok
fwiw, not a .Net group but.... VB6 Integers are VB.Net Shorts (the last time
I checked). When I read the subject line I assumed you wanted to run a .Net
app on Win3.1 or something <g> That "thing" called an Upgrade wizard should,
at least, help you with type conversions.. just create a VB6 project and
declare a few variables (don't need to use them... just declare them) and
let that "wizard" do whatever it does to that project. The end result should
be .Net compatible types.
--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..
| |
|
| dim Bob as int16
BT3
"Tom Edelbrok" <anonymous@anonymous.com> wrote in message
news:qdPTd.4374$hN1.4304@clgrps13...
> We have been using VB6 for a long time now and have many applications.
Some
> of these applications call an industrial process control API that requires
> certain fields to be input as 16-bit integers.
>
> Now we are converting everything to VB.Net 2003 and read that integers are
> 32-bit and longs are 64-bit. Is it not even possible to make a 16-bit
> anymore? I think our API calls (to functions in a DLL) will blow up if we
> pass in 32-bit values to arguments requiring 16 bits.
>
> Thanks in advance,
>
> Tom Edelbrok
>
>
| |
| Bob Butler 2005-02-26, 3:55 pm |
| "BT3" <honeypot@epmctc.com> wrote in message
news:blUTd.90980$GT.15920@okepread01
> dim Bob as int16
I think I resent that!
<g>
--
Reply to the group so all can participate
VB.Net: "Fool me once..."
| |
| Dick Grier 2005-02-26, 3:55 pm |
| Short of Int16, I think Bob is OK.
--
Richard Grier (Microsoft Visual Basic MVP)
See www.hardandsoftware.net for contact information.
Author of Visual Basic Programmer's Guide to Serial Communications, 4th
Edition ISBN 1-890422-28-2 (391 pages) published July 2004. See
www.mabry.com/vbpgser4 to order.
| |
|
| Ha, didn't even notice that. Brain thinking int16, meant short of course.
"Dick Grier" <dick_grierNOSPAM@msn.com> wrote in message
news:%23vdbUpCHFHA.3536@TK2MSFTNGP14.phx.gbl...
> Short of Int16, I think Bob is OK.
>
> --
> Richard Grier (Microsoft Visual Basic MVP)
>
> See www.hardandsoftware.net for contact information.
>
> Author of Visual Basic Programmer's Guide to Serial Communications, 4th
> Edition ISBN 1-890422-28-2 (391 pages) published July 2004. See
> www.mabry.com/vbpgser4 to order.
>
>
|
|
|
|