Cant find system.windows.forms
-
I cant find it for import in VB.NET2010 In references somehow? Am I missing files? :confused:
-
I cant find it for import in VB.NET2010 In references somehow? Am I missing files? :confused:
-
DutchComputerKid wrote:
Am I missing files?
Who can say? Have you created your project using the project wizard or are you trying to do it all by hand?
Well, I have not, I'm new to VS2010. Just started a new form project, and tried to use some code. :doh: How do I start that wizard?
-
Well, I have not, I'm new to VS2010. Just started a new form project, and tried to use some code. :doh: How do I start that wizard?
-
I cant find it for import in VB.NET2010 In references somehow? Am I missing files? :confused:
From Visual Studio; * File | New Project * Choose "Windows Application" If you are missing other references (System.Windows.Forms will already be included), you can add them by right clicking on the project in the "solution explorer", choose "Add reference". Without Visual Studio; * Create a .vbproj project file to list references and designate an entry-point. That file also lists all your other source-files.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
-
From Visual Studio; * File | New Project * Choose "Windows Application" If you are missing other references (System.Windows.Forms will already be included), you can add them by right clicking on the project in the "solution explorer", choose "Add reference". Without Visual Studio; * Create a .vbproj project file to list references and designate an entry-point. That file also lists all your other source-files.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
Yeah I downgraded to .NET 2003. Hope that is more like VB6 without those annoyingly long odd function names, ugh.
-
Yeah I downgraded to .NET 2003. Hope that is more like VB6 without those annoyingly long odd function names, ugh.
Don't Downgrade to 2003 as it uses framework 1.1 which is not supported commonly. Use 2005 or more. 2.0 framework is inclided in all recent frameworks. You won't find similarities with VB6, There are a lot of differences. Migration is very old and you may not find any resources now.