Considering going to VB .Net

[Tim]

I have been using for the last few years, VB 6 Professional. I'm considering
getting .Net now.

Will I still be able to keep VB 6 installed, or will VB .Net totally replace it?
Also, is it a LOT different than VB6?? any personal views there?

 

[Armin Zingler]

I have been using for the last few years, VB 6 Professional. I'm
considering getting .Net now.

Will I still be able to keep VB 6 installed, or will VB .Net totally
replace it?

You can keep VB6 installed.

Also, is it a LOT different than VB6?? any personal views
there?

The concept is *completely* different. However, The syntax is similar.

One of a million links: ;-)

http://msdn.microsoft.com/library/d...tiontovisualbasic70forvisualbasicveterans.asp

 

[Tim]

Oh wow, this should be interesting........ lol

Ok, another question. Including the design mode interface, as well as programs
compiled to an EXEcutable format, does VB.Net take advantage of the XP Themes
(such as those nice looking buttons?)

Thanks again

Tim

 

[Armin Zingler]

Oh wow, this should be interesting........ lol

Ok, another question. Including the design mode interface, as well
as programs compiled to an EXEcutable format, does VB.Net take
advantage of the XP Themes (such as those nice looking buttons?)

You think that's the most important question? ;-)) Yes, themes can be
adding a manifest file.

 

[Armin Zingler]

You think that's the most important question? ;-)) Yes, themes can
be adding a manifest file.

Hey, who stole my letters? ;-( Should be: Yes, themes can be added by using
a manifest file.

 

[Tim]

haha No, that's not the main question I had. Just that.... well I had
figured with XP being out long before .Net was released, the compiler would add
that information to the EXE itself to automatically take advantage of it.

Now then, as far as VB6 is concerned, I can add manifest files and do the same
thing with them. I can even include it inside the EXE and throw away the
Manifest file (although that's done after compilation by editing the resources
of the compiled EXE). I was just hoping, in this one question (of many I'm
sure), that VB.Net would do this for me, or at least give me a "check box" to
enable that function.

Thanks again for the response, I appreciate it!

Tim

 

[Jay B. Harlow [MVP - Outlook]]

Tim,
As Armin stated.

With .NET 1.0 your only option is to add a manifest file.

With .NET 1.1 you can use the manifest file or you can use
Application.EnableVisualStyles. Due to a quick with EnableVisualStyles you
need to follow it with Application.DoEvents.

http://msdn.microsoft.com/library/d...msApplicationClassEnableVisualStylesTopic.asp

Hope this helps
Jay

Oh wow, this should be interesting........ lol

Ok, another question. Including the design mode interface, as well as programs
compiled to an EXEcutable format, does VB.Net take advantage of the XP Themes
(such as those nice looking buttons?)

Thanks again

Tim

You can keep VB6 installed.


The concept is *completely* different. However, The syntax is similar.

One of a million links: ;-)

http://msdn.microsoft.com/library/d...tiontovisualbasic70forvisualbasicveterans.asp

 

[Bloke at the pennine puddle]

Slightly unrelated question. I've got VB .NET 2002. I've unstalled
..NET framework through WindowsUpdate. Can VB .NET 2002 access
everything within the .NET 1.1 framework or is it a mandatory upgrade
to VB .NET 2003?

 

[Armin Zingler]

haha No, that's not the main question I had. Just that.... well
I had figured with XP being out long before .Net was released, the
compiler would add that information to the EXE itself to
automatically take advantage of it.

Now then, as far as VB6 is concerned, I can add manifest files and do
the same thing with them. I can even include it inside the EXE and
throw away the Manifest file (although that's done after compilation
by editing the resources of the compiled EXE). I was just hoping, in
this one question (of many I'm sure), that VB.Net would do this for
me, or at least give me a "check box" to enable that function.

Thanks again for the response, I appreciate it!

As Jay stated meanwhile, there's also a "programmatic" solution to enable
visual styles... I forgot because I don't use them... Should be named
EnableVisualMessingAround... ;-)

 

[Herfried K. Wagner [MVP]]

Hello,

Slightly unrelated question. I've got VB .NET 2002. I've unstalled
.NET framework through WindowsUpdate. Can VB .NET 2002 access
everything within the .NET 1.1 framework or is it a mandatory upgrade
to VB .NET 2003?

VB.NET 2002 won't work without the .NET Framework 1.0. VB.NET doesn't work
with .NET 1.1, you must upgrade to use .NET 1.1.

 

[Herfried K. Wagner [MVP]]

Hello,

does VB.Net take advantage of the XP Themes
(such as those nice looking buttons?)

NET 1.0:

Set the controls' 'FlatStyle' properties to 'System', then add an
application manifest:

Tools

http://www.msjogren.net/dotnet/eng/tools/default.asp
-> tool "ThemeMe"

MSDN:

VS.NET Addin for using XP visual styles
http://tinyurl.com/37yk

Using XP Visual Styles in Windows Forms apps
http://tinyurl.com/37yi

..NET 1.1:

http://msdn.microsoft.com/msdnmag/issues/03/03/WindowsForms/default.aspx

 

[Nak]

or is it a mandatory upgrade to VB .NET 2003?

Yup, afraid so :-(

Nick.

--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
"No matter. Whatever the outcome, you are changed."

Fergus - September 5th 2003
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\