AnsweredAssumed Answered

vrf Beeping VEE

Question asked by VRFuser on Jun 27, 2004
  • Comment • 6
Hi Rufus and the vrf,

> If you're using .net you'll have to make sure each machine
> that uses your
> code has the ".net framework"

A final clarification:

With VEE 7, both Development and Runtime installers will install the .NET framework for you, unless it is already installed.

VEE 7 _will not run_ without the .NET Framework, because a lot of the new features in 7 depend on the Framework, e.g. the new Property pane, the enhanced Notepad and Descriptions, etc.

Also note that only the free .NET Framework is needed; Visual Studio .NET is _not_ needed for VEE 7, not even to use the new .NET Framework Scripting features in VEE 7.

VS .NET is only needed if you want to develop in VB .NET, C#, COBOL, etc (actually it's not even needed for those if you're a Rugged Individualist who uses the Command Prompt for all your development needs

Best Regards,



Scott Bayes
Software Technical Support

Agilent Technologies, Inc.
815 14th Street S.W.
Loveland, CO, U.S.A. 80537

970 679 3799 Tel
970 635 6867 Fax

> -----Original Message-----
> From: Rufus Warren [mailto:rwarren@amti.net]
> Sent: Friday, June 25, 2004 8:46 AM
> To: BAYES,SCOTT (A-Loveland,ex1); PDL-LISTS,VRF (A-Lists,unix1)
> Subject: RE: [vrf] RE: Beeping VEE
>
>
> If you're using .net you'll have to make sure each machine
> that uses your
> code has the ".net framework"
>
> -----Original Message-----
> From: BAYES,SCOTT (A-Loveland,ex1) [mailto:scott_bayes@agilent.com]
> Sent: Thursday, June 24, 2004 4:48 PM
> To: VRF
> Cc: PDL-LISTS,VRF (A-Lists,unix1)
> Subject: [vrf] RE: Beeping VEE
>
> Hi Shawn, vrf-ers,
>
> > no parameters. And in the example I had to add
> > "Microsoft.VisualBasic." in front of "Interaction.Beep()". I don't
> > remember having to specify an explicit namespace when an
> unambiguous
> > name is already referenced. What's up with that?
>
> As far as I know, it doesn't matter whether the name is
> unambiguous or not,
> it matters whether you've imported the namespace in the .NET Assembly
> References... dialog.
>
> Detlef's app arrived with 2 namespaces imported from the VisualBasic
> assembly. The one that was necessary for the formula syntax
> to work was
> Microsoft.VisualBasic. If I went back through the references
> dialog and
> unchecked the namespace in the Import .NET Namespaces dialog,
> the program
> gave an error "Variable was not found: Interaction".
> Rechecking it caused
> the error to go away.
>
> Once you've imported namespaces, I'm not sure what happens
> with an ambiguous
> reference that could originate from more than one namespace.
>
> In general, life is usually easier with .NET if you import all the
> namespaces you'll need, especially if typing is not your bag.
>
> > NO WAY! Check this out. If I run it as opened, it doesn't
> work. If I
> > then open the FOB & drill down to Beep, click Create, paste
> it in and
> > get rid of the original THEN IT WORKS! What the heck is up with
> > THAT???
> > There's no
> > difference!
>
> The F&O Browser creates a fully qualified path to the method
> which works
> independent of the Import Namespaces setting.
>
> No idea why Detlef's program arrived in your mailbox with the
> namespace not
> imported however; on my system it was imported and worked
> right from the
> start.
>
> Best Regards,
>
>
> Scott Bayes
> Software Technical Support
>
> Agilent Technologies, Inc.
> 815 14th Street S.W.
> Loveland, CO, U.S.A. 80537
>
> 970 679 3799 Tel
> 970 635 6867 Fax
>
> > -----Original Message-----
> > From: Shawn Fessenden [mailto:shawn@testech-ltd.com]
> > Sent: Thursday, June 24, 2004 1:20 AM
> > To: PDL-LISTS,VRF (A-Lists,unix1)
> > Subject: [vrf] RE: Beeping VEE
> >
> >
> > > ???.NET framework1.0/1.1???Beep()???????????????????:
> > >(a) ??Win32 API:
> > >    [DllImport("kernal32.dll")]
> > >    public static extern bool Beep(int freq, int duration);
> >
> > That's the one.
> >
> > > was very interesting to search for
> >
> > I guess! How exactly did you find this? In the SDK
> documentation, all
> > I can find is VB Beep with no parameters.
> >
> > Wait a sec. So how does one go about *using* this? I still got one
> > Beep with no parameters. And in the example I had to add
> > "Microsoft.VisualBasic." in front of "Interaction.Beep()". I don't
> > remember having to specify an explicit namespace when an
> unambiguous
> > name is already referenced. What's up with that?
> >
> > NO WAY! Check this out. If I run it as opened, it doesn't
> work. If I
> > then open the FOB & drill down to Beep, click Create, paste
> it in and
> > get rid of the original THEN IT WORKS! What the heck is up with
> > THAT???
> > There's no
> > difference!
> >
> > Oh, now it *does* work. Now if I reboot, open it again and
> click go it
> > doesn't work. Now if I close it, reopen it then IT DOES!!!
> >
> > Iyeyey. I'm going to bed.
> > -SHAWN-
> >
> >
> > ---
> > You are currently subscribed to vrf as: scott_bayes@agilent.com To
> > subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
> > To unsubscribe send a blank email to
> > "leave-vrf@it.lists.it.agilent.com".
> > To send messages to this mailing list,  email "vrf@agilent.com". 
> > If you need help with the mailing list send a message to
> > "owner-vrf@it.lists.it.agilent.com".
> >
>
> ---
> You are currently subscribed to vrf as: rwarren@amti.net To
> subscribe send a
> blank email to "join-vrf@it.lists.it.agilent.com".
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list,  email "vrf@agilent.com". 
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
>
>

---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list,  email "vrf@agilent.com". 
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".

No one else has this question

Outcomes