I am planning to use a List in my application but when I was searching for System.Collections.Generic, it only has System.Collections. I tried to look it up in the "add reference" and its not there.
Could anybody tell me where I can add the reference for this.
Thanks for those who can help me
No. 2003 works with .net 1.1 and Generics were introduced in 2.0. You'll need Visual Studio 2005 or later.
Generics were introducted in .Net 2 . So if you work with .Net 2 or later it's supported
Related
Using dotnetbar advTree and their support is already out of business
I need to enumerate through all nodes in AdvTree.
The problem is that I'm using vs.net 2010 pro and my project is .net fw 4.0 (full)
This is not supported in my version:
Private Shared Iterator Function
Anyone can advise how to make it work in vb.net 4.0? :)
https://www.devcomponents.com/kb2/?p=1357
Tried their sample and not supported :(
sorry for asking this, but I'm really newbie to this. I just receive a code from my boss and it is a code with VB 6.0 version, he then ask me to convert into the latest version of VB. Now I get confused because when I google I found out that the latest version is VB 6.0 . So I get confused now.
Can anyone correct me if I'm wrong and if theres any latest version,how can i convert it? Is there any converter tools like developerfussion? TQ
I don't recommend a direct translation. VB 6.0 was the last release for the classic visual basic. After that it became in VB.net, which is not the same, is a 100% object oriented programming language but, you could be able to convert it by hand. Since VB.net is OOP and VB 6 is not you can transcript from VB 6.0 to VB.net using the procedural way, loosing all of the OOP advantages. The other thing you can do is re-write the program from scratch to VB.net, which is going to take a while but it will worth it. The latest version for Visual Studio is 2013.
Your boss may sugest a convertion from visual basic 6 to vb.net. You have several tools to do that. You can use the free visual studio 2008 Express (open and convert the code), or you can try the mobilize vb upgrade tool (free until 10.000 lines of code).
https://www.mobilize.net/solution/msdn
This limit of loc is quite small, exclude the comments but includes all the code and the design code.
You have lots of help here using the
https://stackoverflow.com/questions/tagged/vb6-migration
I just want to know if VB.NET and VB 2010 are the same.
I'm just wondering.
VB 2010 is the latest version of VB.Net. Microsoft dropped the ".Net" part of VB with the VB 2005 release.
Wikipedia has all you need to know about VB.net: Wikipedia Page
VB.NET is any version of Visal Basic since version 7, where the language moved to the .NET platform and became object oriented.
2010 isn't a version of the VB language, it's sometimes used to describe the version that comes with Visual Studio 2010, which is VB version 10.
As specified on the wiki page for VB.NET VB 2010, or VB 10.0 is a new version of the language commonly refered to as VB.NET.
as the time changed visual basic became more advanced. Before it used a p code compiler. but all the versions after vb 6.0 IDE it stopped using msvb60.dll and shifted to .NET framework which is now called VB.NET. But Microsoft removed the .NET after VB 2005 final release. Also it used a VBC.exe which is the new Visual Basic compiler. There was a lot of criticiscm after this because it was not compatible with Win 98 and previous versions.
Visual Basic .NET (VB.NET) implemented on the .NET Framework. Microsoft launched VB.NET in 2002 as the successor to its original Visual Basic language. Although ".NET" portion dropped in 2005,"Visual Basic .NET" to refer to all Visual Basic languages releases since 2002.
There is Visual Basic and Visual Basic .NET. Visual Basic .NET runs on the .NET framework and the former does not.
Basically yes, Vb 10 is just the newer version
Yes they are the same, but VB.Net runs with .NET framework.
Yes they are the same. Bassicaly VB 2010 is using .NET framework
Vb.net is the same as VB 2017. In your case it's 2010. Just more features
VB 2010 , because nobody is needed to know .net when they know vb
but in vb.net you also have to learn .net,
This version is also the latest
you can also have vb2010 express for free here
http://www.microsoft.com/visualstudio/eng/downloads#d-2010-express
(OR)
get the paid version like pro edition here (trial only)
http://www.microsoft.com/en-us/download/details.aspx?id=2890
VB.NET is the language that you can use on the .NET framework. Before .NET framework evolved, Microsoft had a separate product called Visual Basic, and in 2002 when Microsoft came with .NET framework then they discontinued Visual Basic as independent product, and combined it in the .NET framework.
Basically .NET framework supports 50+ languages (Visual Basic is one of them, and C# is another commonly known language) which you can use to develop variety of applications. Over the years, Microsoft improved .NET framework, so thus the VB language to make it more smart.
The VB 2010 that you are asking is the Visual Basic language that came with the Visual Studio 2010.
VB 2010 is a part of the VB .NET family. VB.NET uses the .NET language runtime, while VB6 and previous VB does not. VB .NET is object-oriented, and the classic VB is event-driven.
Is there any code conversion tool for converting Delphi to Visual Basic? Please advice.
Thank you very much.
Not that I'm ware of. There are tools to convert Delphi to C# or Visual Basic to Delphi. But not the other way around. It's probably because Delphi has a lot more features then Visual Basic to make it a difficult transition.
You can do it by hand. But it'll take a while.
If you consider moving to VB.NET (and .NET platform in general butnot VB6), these questions might give you some ideas/options:
What tools exist to convert a Delphi 7 application to C# and the .Net framework?
Is there an easy way, to Port a Win32 App in Delphi 2009 to .NET ?
Migrating a Delphi 7 application to .NET
Delphi to .NET + C#
Delphi’s interoperability with .NET
You can try migrating the application from Delphi (Win32) to Delphi.NET or Delphi Prism
Once this step is complete you can consider migrating to VB.NET or C#
But it really depends on the technologies used by your original application (e.g. BDE, 3rd party components), level of interaction with WinApi and so on.
Delux Software has one.
I am less than a week into my Visual Basic education. I have downloaded Visual Studio 2008 and am teaching myself Visual Basic 2008 in hopes of landing a particular contract position.
In the meantime, a friend of mine told me that it is not recommended to write a Windows Service with Visual Basic. Is that true? Could he be referring to some much older version than 2008? Does the .NET version come into play?
What is at stake is that the company that my friend works for is going to completely re-write a component of their flagship product at great cost and expense and simply abandon their existing VB code. If the only hang-up is getting it to run as a service then they could save a lot of money if Visual Basic could, in fact, run reliably as a service.
You can write .NET services in any CLR language, including VB.NET --- your friend was thinking of VB6 and earlier.
(I do recall some fairly crazy kludges that allowed services to be written in VB6, but for all practical purposes, services written in VB6 weren't really a viable solution...)
There is no reason that Visual Basic .Net can't write a windows service. You can select a project which will create a windows service under the "Windows" projects in the Visual Basic section.
Writing a Windows Service in VB.NET (using any version of Visual Studio >= 2003) is just as effective as writing a Windows service in any other language.
Your friend may have been thinking of Visual Basic 6...or he's partial to another .NET language.
In either case...you should be fine to keep going on your path the way you are.
Your friend may be referring to Visual Basic, not VB.NET.
While VB.NET has syntax that is similar to Visual Basic and some convenience functions are still present, they are two entirely different languages and environments.
Your friend is correct in stating that Visual Basic (meaning 6 and earlier, not VB.NET) is a poor choice of a language for a service (or any new application), but VB.NET is every bit as legitimate as C# or any other CLR language.
It may be useful to refer to what you're learning as "VB.NET" or "Visual Basic .NET", rather than just "Visual Basic".
.NET certainly allows you to use Visual Basic to write a Windows Service. I believe there is even a default project template to do so. Here is an tutorial as such: http://www.vbdotnetheaven.com/UploadFile/mahesh/Winservvb11172005233242PM/Winservvb.aspx
All .NET code is converted to an intermediary language that is executed, thus all .NET languages can be used to write a windows service.