Visual J# .NET 2003 FAQs
Home

Q1: What is Visual J# .NET?

Visual J# .NET is a development tool for Java-language developers who want to build applications and services on the Microsoft .NET Framework. Visual J# .NET provides the easiest transition for Java-language developers into the world of XML Web services, and dramatically improves the interoperability of Java-language programs with existing software written in a variety of other programming languages.

Visual J# .NET includes technology that enables customers to migrate Java-language investments to the .NET Framework. Existing applications developed with Visual J++® can be easily migrated to execute on the .NET Framework, interoperate with other .NET-connected applications and languages, and incorporate new .NET functionality such as ASP.NET, ADO.NET, and Windows® Forms. Further, developers can use Visual J# .NET to create entirely new .NET-connected applications.

Q2: What's new for Visual J# .NET 2003?

Visual J# .NET gains some exciting features in 2003.

1) Support for Mobile Web applications. Build broad-reach applications that render dynamically to over 200 mobile device types.

2) Support for Crystal Reports. Integrate rich reporting capabilities into your Visual J# .NET 2003 applications with Crystal Reports support built right into the Toolbox.

3) Targeting of the .NET Framework 1.1. Includes enhancements in performance and scalability, support for ASP.NET Web Forms, ASP.NET Mobile Web Forms, ADO.NET, Windows Forms, XML Web services, and full cross-language integration.

4) Product Availability. Visual J# .NET 2003 (formerly a downloadable add-in to Visual Studio .NET) is now packaged 'in-the-box' with Visual Studio .NET 2003. The Standard Edition is also now available as a stand-alone product for purchase, and is designed for the student or hobbyist developer.

5) Visual J# .NET 2003 also gains a number of other improvements found throughout the Visual Studio .NET 2003 family of products. These include integrated development environment (IDE) enhancements, performance gains, expanded documentation, and a number of other improvements that make Visual Studio .NET 2003 the best environment in which to develop your applications.

Q3: What are the differences between Visual J# .NET 2003 Std Edition and Visual Studio .NET 2003 Pro Edition?

Visual J# .NET 2003 Standard is intended for hobbyist or non-professional developers. It does not include the following features found in Visual Studio .NET 2003 Professional and higher editions:

1) The 'server' node in the Server Explorer. Developers will commonly use this feature to visually design server-side solutions.

2) Other languages. Visual Studio .NET Professional and higher editions include Visual C# .NET, Visual Basic .NET, and Visual C++ .NET in addition to Visual J# .NET.

3) Source code control integration.

4) Enhanced debugging support.

5) Visual data tools.

Extra wizards. Numerous additional wizards ranging from the Control Creation wizard to the Windows Service wizard are not present in Visual J# .NET Standard Edition.

Q4: How can I get more information on Visual J# .NET?

A number of resources offer additional information on Visual J# .NET. The Visual J# .NET community on GotDotNet.com is available for developers seeking information directly from the Microsoft J# team. Additionally, a number of newsgroups can provide more information about Visual J# .NET. Check out microsoft.public.
dotnet.vjsharp.

Q6: Once I load my existing projects into Visual J# .NET 2003, can I go back to using Visual J# .NET 2002?

If you use Visual J# .NET 2003 to open a project that was developed using Visual J# .NET 2002, you will be prompted to upgrade the project to the new 2003 format. This will create a new project file that will only be accessible by Visual J# .NET 2003. It is advised that you create a backup of the Project folder if you need to maintain the old (2002) version of the application.

Q7: Can Visual Studio .NET 2002 and Visual Studio .NET 2003 be installed on the same computer?

Yes. Both Visual Studio .NET 2002 and Visual Studio .NET 2003 can be installed on the same computer as long as system requirements are met. This makes it easy for you to maintain your 2002 applications while you continue development on your 2003 applications.

Q8: Can Visual J++ 6.0 be installed alongside Visual Studio .NET?

Yes. Visual J++ 6.0 can be installed on the same machine as Visual Studio .NET 2002 and/or Visual Studio .NET 2003 as long as system requirements are met. This makes it easy to maintain your Visual J++ 6.0 applications while you continue development on your Visual J# .NET projects.

Q9: Can Visual Studio .NET 2002 apps be installed alongside Visual Studio .NET 2003 apps?

Yes. The .NET Framework supports side-by-side deployment. This means that different versions of applications may co-exist on the same machine.

Q10: How do I pose a question or send feedback to the J# community?

The primary way to ask the community questions is to post to the public J# USENET newsgroup at microsoft.public.
dotnet.vjsharp. Alternatively you can post to the public J# discussion forum on GotDotNet.com. For technical support, please consult Microsoft Product Support Services (PSS). For questions, please use the newsgroup or the discussion forum.

Q11: Can I write Java 2 Enterprise Edition (J2EE) applications with Visual J# .NET?

We use no Sun Microsystems technology in this product, nor do we produce bytecode class files. You can use Visual J# .NET to write classes using the Java-language syntax and then compile them using a third-party Java development tool. Applications written and compiled with Visual J# .NET target the .NET Framework exclusively.

Q12: Why would I want to use Visual J# .NET?

If you are a developer who is comfortable using the Java language and you want to start building third-generation applications on a true XML Web services platform, then Visual J# .NET will appeal to you. If you are an existing Visual J++ customer, then Visual J# .NET provides the easiest path for you to move your code to the .NET environment.

Even if you aren't interested in the benefits of XML Web services, there are a number of powerful benefits in the .NET Framework, such as ASP.NET, ADO.NET, and Windows Forms. With Visual J# .NET, you can use the Java language to take advantage of any feature in the .NET Framework.

Q13: I am a Visual J++ developer. What are you recommending that I do?

1)Continue to develop using Visual J++ and surface your applications and components as COM objects, which are callable from .NET.

2)Open projects in Visual J# .NET and start building true .NET-connected applications.

3)Use the Java Language Conversion Assistant (JLCA) to move existing Java source code to C# and .NET-connected technologies and applications. (msdn.microsoft.com
/vstudio)
The path you choose depends on the kinds of applications you have today and where you want to place investments tomorrow.

Q14: Will apps written with Visual J# .NET 2003 run on a Java Virtual Machine?

Visual J# .NET 2003 is not a tool for developing applications intended to run on a Java virtual machine. Applications and services built with Visual J# .NET 2003 will run only in the .NET Framework; they will not run on any Java virtual machine. Visual J# .NET 2003 has been developed independently by Microsoft. It is neither endorsed nor approved by Sun Microsystems, Inc.

Q15: What is the symbol in the name 'J#'?

The '#' is not the 'hash' (or pound) symbol as many people believe. Rather, it is actually the musical sharp symbol. However, the actual sharp symbol is not present on the standard keyboard, so it's easier to use the hash ('#') symbol. The name of the language is, of course, pronounced 'jay sharp.'

Home