Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why is it necessary to “import” a Visual J++ 1.1 project?

April 26, 2017import necessary project visual j

0

Posted

Why is it necessary to “import” a Visual J++ 1.1 project?

1 Answer

0

Posted

Projects in Visual J++ 6.0 work differently than they do in earlier versions. The “import” process converts a Visual J++ 1.1 project into a Visual J++ 6.0 project. While the new projects are improved in many ways over the Visual J++ 1.1 projects, there are certain Visual J++ 1.1 projects that will not import properly into Visual J++ 6.0. Described below is the import process, along with some possible problems and how to work around them. See the “Directory-Based Projects” help topic in MSDN for a more general description of the differences between projects in Visual J++ 1.1 and Visual J++ 6.0. How do I import a Visual J++ 1.1 project? There are two ways to import a Visual J++ 1.1 project, via the project file (.dsp) or the workspace file (.dsw). Open the project .dsp file. One .dsp file is created per Visual J++ 1.1 project. Its name is derived from the project name. The .dsp file contains all the project-specific information associated with the project. To import a Visual J++ 1.1 proj