Is it possible to have visual studio 2010 automatically add namespaces to classes within folders just like c#?
No this is not possible with the VB.Net project system. I would encourage you to share this opinion with the Visual Basic IDE team. They closely monitor suggestions and I know this has come up in the past (although I don't know if there is a current outstanding request for it).
http://connect.microsoft.com
Related
Is it benificial to download Visual Studio Community for VBA programming?
Or is it better just to run Visual Basics out of a word document
VBA and VB aren't the same thing.
VBA is Visual Basic for Applications and is derived from VB. VBA is encapsulated within Microsoft Office and is primarily event driven, whereas Visual Basic is a fully fledged OOP language that's used within the Visual Studio IDE.
You can create VSTO add-ins for office using VB within Visual Studio - but unless you have a specific reason to I would stick with using VBA as the language has been developed with Office automation in mind, and so the objects and the built in IDE providing features such as IntelliSense are already configured to help you achieve what you need
Ultimate point here is that there's no point re-inventing the wheel. Stick with VBA.
I need to make a windows app. Should I use VB or VB.net? What is the real difference actually? I downloaded visual studio for vb and right now I have "microsoft visual basic 2010 express". I'm assuming if I want to use VB.net it'll say "microsoft visual basic.net 2010 express". Where do I get that from though?
COM-based VB (i.e., "VB6") is obsolete and no longer sold.
VBA is only part of another app or product (such as Excel, Word, etc.) that hosts it and is not appropiate for a stand-alone app.
VB.Net is current, available for purchase (as part of Visual Studio), and supported.
So use VB.Net.
Visual Basic 2010 Express is the IDE to write VB.NET code. You already have the correct program.
As you're starting now - why not use the newest Visual Studio Express 2012?
We have a large chunk of legacy code in VB that I want to unit test, so step one if building interfaces. In C#, visual studio has the cool little Refactor -> Extract Interface function. VB Doesn't, though?
Is there a good way to do this in VB?
Extract Interface function. VB Doesn't, though?
Yes. Unfortunately, Microsoft Visual Studio does not support refactor functionality for VB.NET.
You can install third party tools such as ReSharper, though.
For more information, also have a look at this question on SO: Refactoring options in Visual Studio 2010 differ between C# and VB
In Visual Studio 2010 express (using vb.net) I've somehow set two forms to use the same class.
Basicly I have two designer files with 1 implementation each. For some reason both designer files are calling the same implementation file, and I can't find any settings to correct the problem. Help!
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.