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.

C-Sharpener For VB can automatically convert VB to C# (or as some developers like to spell it VB 2 CSharp ). It is a Visual Studio .NET addin and converts all VB.NET project related files including the project file itself.

You need Visual Studio .NET 2003 or 2005 (Standard, Professional, or Team edition) installed on your computer to run C-Sharpener For VB because it is a Visual Studio .NET Addin. C-Sharpener For VB does not support Visual Studio .Net 2005 Express edition because the Express edition does not support Visual Studio .NET Addins.

C-Sharpener For VB is really a full parser that emits C# instead of MS Intermediate Language. It does full syntactic and semantic analysis including a full symbol tree of all symbols in the code and referenced assemblies. Some conversion problems can only be solved with this level of technology.

If you purchase C-Sharpener For VB, we will give you minor version upgrades for free. For instance, if you license version 1.1 and we release 1.2, you can upgrade for free. If we were to release 2.0, then you would get a substantial discount coupon for the new major release.

C-Sharpener For VB does not convert vbscript. However, it does convert all Visual Basic .NET code in code-behind (*.vb) pages.

There is a new option to automatically convert VB.Net methods with optional parameters to C# overloaded methods. Improved handling of web references so that a web reference with a non-default name converts correctly.

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!

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.

Microsoft didn't get its Standard C++ act together until Visual C++ 2003. (a.k.a. version 7.1) If you must use older versions of VC++, you're stuck with either the C API, or the ancient 1.7.1 release of MySQL++. This version is an unofficial third-party contribution which is known to have bugs. If it works, I'm happy for you. If it breaks, you get to keep both pieces. Microsoft is giving away a limited but functional version of Visual C++ 2005 which works just fine with MySQL++.

Assuming that you have successfully installed Fast Formatter and you have any edition (except the Express edition) of Visual Studio .NET 2005 installed, the menu option should automatically appear as described in the tutorial. If it doesn't appear, then please try the following: Turn on the checkbox to the left of Fast Formatter and click the OK button. The menu option should now appear.

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...

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.

You will need to download and install additional components. Please see the Visual Studio Developer Center for more information. No, each release of Visual Studio is tied to a specific version of the .NET Framework. The Express Editions can only be used to create applications that run on the .NET Framework 2.0.

Yes. Eiffel for .NET can be used in exactly the same way as classic Eiffel and no extra language constructs are required to produce applications. Since there are some elements of the .NET language which have no equivalents in Eiffel, such as the ability to define custom attributes, these have been extended to Eiffel for .NET so that the full features of .NET can be used. Eiffel Software (a division of ISE) is the world leader in Eiffel pure object-oriented programming tools.

browse the list, and near the end check the "VideoGrabberNET control" component, click "OK" now the TVideoGrabber component appears in the ToolBox, select it and place it on the form (wait a few seconds before the control appears) double click on the button, and put this code in the button1_click event: "axVideoGrabberX1.StartPreview();"

It is very hard for us to support every Windows compiler, so we try to choose the most current and popular compilers. We are depreciating our support for Visual Studio 6.0 and .NET 2003 in favor of Visual Studio 2005, and in the future, 2008. Moving to new compilers also means we can take advantage of new features and make the build process even easier. For example, we now support building on 64-bit Windows and Windows Vista using Visual Studio 2005.

Please see Limitations and Workarounds (PDF file) for more details. You may also want to look at some sample converted projects.

For the record, we see value in both the VB.NET and C# languages. However, if C# is your preferred language, you want to convince others to switch from VB. You can use the reasons below to convince your managers or co-workers. Your code quality will improve because C# catches potential errors (example: variable use allowed before initialization and dead code) that are permitted in VB.NET. If your project is a mix of VB.

First, be sure to see the README pertaining to Windows development available in the OEChem section of the download page, which describes the required compiler versions. In the MSVC distribution, the Makefile at openeye/examples/oechem/ contains the recommended compilation flags for use with MS Visual Studio/C/C++ (although most developers will not use make). As of OEChem 1.3.3, example project files are provided with the distribution.

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

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.

One of the biggest advancements in Visual Studio .NET is that the environment, like the underlying .NET CLR, is not tied to any one language. Microsoft ships C#, C++, Visual Basic, and ECMAScript/JScript/JavaScript support in the box, and will ship its Visual J# .NET add-on later in 2002. But hundreds of companies are porting various programming languages to .NET and the Visual Studio .NET environment, including Delphi/Object Pascal, Perl, PHP, and many more.

It is not planned to release a version of Help Publisher that works with Visual Studio .NET 2002. You can of course use still use Help Publisher for FrontPage or Dreamweaver to produce Help files. Later in the year a new version of Help Publisher will be released that will support Visual Studio 2005.