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.

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.

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. Eiffel brings quite a few unique and powerful features to .NET. Most noticeably it is the only .NET language to offer multiple inheritance and genericity since the first version of the .NET Framework. These two mechanisms are an indispensable aid to creating fully reusable software in a truly object-oriented way. Eiffel for .

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.

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.

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!

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.

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

In the end, no. Support for multiple inheritance and the inclusion of the base library classes currently does result in generated assemblies which are larger than those generated by other .NET languages; however, there are no significant performance differences at run-time.

Type devenv.exe /? to get a full list of options. Contributed from George Shepherd's Windows Forms FAQ

EiffelEnvision brings strengths in several areas that result in significant benefits to the developer: Eiffel's "code once, run on many platforms" feature provides "future proofing" for companies using .NET: their users can migrate applications to and from different platforms, and can also use component libraries across platforms. Eiffel brings quite a few unique and powerful features to .NET. Most noticeably it is the only .NET language to offer multiple inheritance and genericity.

By integrating our installation technology directly into Visual Studio .NET, we have created a new installation authoring model. From the first line of code that's written, you will have a working installation. You can now test the installation as you test the application. The result is higher quality products, easier internal testing, earlier beta availability, and a significantly more efficient development process.

Wise is an innovative company always looking for ways to use new technologies to solve customer's installation problems. We immediately saw this as an opportunity to change the way installations are created, and are the first and only installation tool vendor to capitalize on this opportunity.

The macro editor is not a part of Wise for Visual Studio .NET because Visual Studio has it's own macro editor that can be used to automate Wise installations. Source control integration has also been removed as it is not longer necessary due to our interface with the Visual Studio .NET source control. The Import Visual Basic Product Wizard has been removed because the integration eliminates the need for this function.

The normal 30 day return policy applies for Wise for Visual Studio .NET. The exception to this is if you buy the Wise for Visual Studio .NET bundle-the Microsoft Visual Studio .NET portion of the bundle is not returnable.

There are two main reasons. Speed and functionality. If your application needs to deliver real time mathematical results, you need speed. If your application needs to implement special, less known mathematical algorithms, not covered in standard math libraries, you need functionality. In either case MtxVec is a good choice.

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.

skmMenu can be downloaded in one of two flavors - as a stand-alone binary (the skmMenu.dll assembly), or as a source-code project. The compiled binary is compiled for the .NET Framework version 1.1 and was compiled using Visual Studio .NET 2003. To use skmMenu on a Web site using the .NET Framework version 1.0, you will need to donwload the source code version and compile it with Visual Studio .NET 2002. To accomplish this, do the following: Manually add in the downloaded .cs and Menu.