Borrow the Visual Studio .NET 2003 Professional CD's from our SCC Computer Lab. If you don't bring them back you can't enroll again. Comment: If you are only going to take ITSE 1431 then the Standard Edition is OK. If you will continue studying VB .NET you need the Professional edition or better.

I recommend a fast computer with lots of hard disk space and lots of memory. Note that if you want to run all the features of VB .NET you need to have Windows 2000 Professional or Windows XP Professional.

J. Henshaw asks "Is it possible to run both VB6 and VB.Net on the same machine,or do I have to remove VB6 to be able to use VB.NET", and the answer is a definite yes. You can run them both on the same machine. Many people, including myself, run VB6 on the same machine as their installation of Visual Basic .NET. If you look at this KB article from Microsoft Support, you will even see that it recommended to run VB6 and VB.NET on the same machine when upgrading projects from one to another.

The percentage of the project that will be converted is typically more than 99%. However, the percentage can vary greatly depending on the structure of your code. For instance, if Option Strict is On then it is significantly easier to convert your code because C# is more type strict. Please see Limitations and Workarounds (PDF file) for more details. You may also want to look at some sample converted projects.

Paul Vick, Technical Lead on VB.NET, and the author of the Visual Basic .NET Language Specification, discusses the new short-circuiting boolean operators added in Visual Basic .NET 2002.

The answer for all of these examples is the same, you can use the classes and methods in System.Diagnostics.Process to accomplish these tasks and more. Example 1. Running a command line application, without concern for the results: Private Sub Button1_Click(ByVal sender As System.Object, _ Example 2. Retrieving the results and waiting until the process stops (running the process synchronously): Private Sub Button2_Click(ByVal sender As Object, _ Example 3.

In VS2003, debug info for unmanaged code is turned off by default. This is why you will not see the call stack including code in the System DLLs. To enable debugging for unmanaged code go to your project properties dialog and turn on as shown here: Contributed...

No. Rules extensions can be built and compiled on a separate computer, then copied to the extensions folder on the MIIS server. Installing the debugger on the MIIS computer is a good idea, since it will improve the troubleshooting experience. Top

Microsoft Visual Studio .NET 2003 solution build runner is build on the base of NAnt runner, described before. Solution task is used to run the build. Projects files are expected to be wellformed XML. You may configure this runner to run NUnit tests.

Yes, VBA exists in Office 2003 as it has in previous versions of Office. New XML functionality in Office Professional 2003 has been made available to developers through additions to the Office object model.

A6: To Install, copy the cab file over to your mobile device My Documents and open it up. If you have problems or questions contact support@gooeynet.net A7: Version 2.2 of the Shoppinglist does have the ability to track coupons as well as the price of an item on a store by store basis.

See the article A Utility to Convert VS.NET 2003 Project Files on The Code Project . Contributed from George Shepherd's Windows Forms FAQ

Yes! SpeechStudio provides tutorials for C++, VB, VB.NET and C#. You can use any language that supports automation.

The service has been tested with a C# client auto-generated from WSDL by the wsdl.exe tool. It should work fine from any .NET language.

Well, there is a compatibility problem. You can run a project from 2002 on 2003, but not visa versa. Once a 2002 is opened in 2003 it can't be opened in 2002. Of course, there are work-a-rounds but that beyond an intro class. Note: This class is about VB .NET 2003.

Yes. Dependency Walker will work with any 32-bit or 64-bit Windows module, regardless of what language was used to develop it. However, many languages have their own way to specify dependency relationships between modules. For example, COM modules may have embedded type libraries and registration information in the registry, and .NET modules may use .NET assemblies. These techniques are all implemented as layers above the core Windows API.

Assuming that you have successfully installed C-Sharpener For VB, the menu option should automatically appear. If it doesn't appear, then try the following: Turn on the checkbox to the left of C-Sharpener For VB and click the OK button. The menu option should now appear.

Visual Basic 2008 Express includes a migration wizard that will help import existing Visual Basic 6.0 projects. You may need to make some manual adjustments to the code you port over, but the migration wizard is a good first step towards moving your code forward.

Yes. STATISTICA can be controlled from within other applications, such as Visual Basic, using the STATISTICA Command Language (SCL). Programs written in SCL can be executed from within Visual Basic using the SHELL command. This allows for the complete integration of STATISTICA into your custom application or other applications such as ms Excel, ms Access, or ms Word. See the STATISTICA Development Environment for information about how to manage STATISTICA data files from within Visual Basic.

C-Sharpener For VB only converts from VB.NET to C#. If you want to convert Visual Basic 6 or earlier, we recommend that you first upgrade from VB6 to VB.NET with Microsoft's free VB to VB.NET Upgrade Wizard. After that, switch to C-Sharpener For VB to complete the VB.NET to C# conversion. This two step process seems to lead to the most reliable results.

Yes. You can use the Visual Studio Team Foundation Server MSSCCI Provider Beta 2, but be sure to disable strong name validation.

The programs are written in Visual Basic 6.0 and thus requires its run time files. However all of our downloads include these support files so you don't need to install them separately.

Wise for Visual Studio .NET is a specially designed Wise product that operates within the Visual Studio interface, with the full functionality of the Wise installation authoring environment. Wise for Visual Studio .NET™ is the only full-featured installation product embedded directly into Microsoft® Visual Studio® .NET. Our participation in the Visual Studio Integration Program and our close partnership with Microsoft gives us exclusive access to Microsoft technology.

This project is my hobby and the last thing I want to do in my spare time was use a language or environment I don't enjoy (I code on Macs during the day, and that's enough pain ^_^). I like C#, and I love Visual Studio. Just about any argument you can create against it can be countered, so don't even try. If you don't like it, you don't have to use it; I know that this is certainly my philosophy with other languages/environments!

Visual Basic 2008 Express is designed for hobbyists, first-time developers, and students looking for a fun and easy way to build Windows applications.

The Express products are not officially supported. But you may find help by posting your question in the Express Edition Forums.

First you need a CommonDialog control on your form. In this example I've called it "dlgCommonDialog and in the form's Load event I've added:-