Got a question about .NET? Check out the .NET FAQ!
Yes! The freely downloadable Microsoft Platform SDK includes a pre-release compilerfor targeting the Intel Itanium.
Visual C++ 2005 ("Whidbey") will include fully supported compilers for targeting bothAMD64 and Itanium. The mainstream 32-bit compiler will also generate managedcode that runs on the 64-bit .NET CLR.
Porting to a 64-bit platform gives your application several advantages. Thebiggest advantage, literally, is a much larger address space. In addition, bothAMD64 and Itanium have access to larger general purpose registers, and more of them. This usually means better performance. And by porting now, your applicationwill be one of the front-runners for the upcoming generation of computing!
Visit the 64-bitProgramming page on the MSDN Visual C++ Developer Center.
No. Unlike the mainstream 32-bit x86 compiler, the 64-bit compilers do not supportinline assembly.
However, there are some alternatives for 64-bit applications. Compiler intrinsics are provided for almost every machine instruction. Assembly code may also be written in another file, assembled, and linked that with the C/C++ application.
Managed code runs within the context of the .NET common-language run-time environment(CLR). It is not compulsory to use managed code, but there are many advantagesto doing so. A managed code program written with C++, for example, canoperate with the CLR to provide services such as memory management, cross-languageintegration, code access security, and automatic lifetime control of objects.
Managed Extensions for Visual C++ are a syntax extension to the standard C++ language. These new keywords make it easy for new and existing applications to add support forthe .NET Framework.
The /clr compiler option instructs Visual C++ to generate managed code that will runin the context of the Common Language Runtime (CLR).
The .NET Framework is a new computing platform designed to simplify application developmentin the highly distributed environment of the Internet. Software running on the .NETFramework can communicate with software running anywhere else through SOAP and canuse standard objects locally or distributed across the Internet. Consequently, thedeveloper experience is made consistent so that you can focus on features rather thanon plumbing. You can find out more at the .NETFramework FAQ.
Visual C++ enables developers to optionally incorporate the .NET Framework into theirapplications using the /clr compiler option.
Enabling your C++ application with .NET technologies will allow you to leverage themany powerful features of the .NET Framework without rewriting your code. Theseinclude the Base Class Libraries, improved versioning and deployment, code and datasecurity, and a variety of other features. Adding .NET to your existing C++code is also the fastest and most cost effective way to leverage future WinFX capabilitiesfrom your existing applications. Incorporating the .NET Framework today is thebest way to prepare for Longhorn tomorrow.
Any application that compiles clean with the /TP compiler option (compile as C++ code)can be compiled with /clr. Not all source code will compile cleanly and mayrequire programmer attention to correct warnings and errors.
In Visual C++ 2005 ("Whidbey"), the process of retargeting existing source code with/clr is made easier and more powerful, with less programmer attention required.
It depends. Purely managed code (no specific use of CLR data types) willgenerally run slower, but this is not always the case. For example, the CLR-targetedQuake II port runs approximately 5 to 15% slower on most platforms, but runs slightlyfaster on Intel Centrino Pentiums.
Microsoft recommends that developers selectively retarget portions of their applicationsto the CLR where it makes sense, and to tune the managed/unmanaged boundaries whenand if performance issues arise.
Several companies with large C++ source-code investments are using Visual C++ to implementnew .NET-based features. Microsoft (DirectX), Riverdeep (PrintShop), and Autodesk(AutoCAD) are three companies who use Visual C++ to incorporate the .NET Framework,and enable their applications with .NET capabilities.
C++ has a complete roadmap for taking advantage of .NET Framework for C++ applications:
C++ images can be pure native code, pure MSIL or mixed-mode containing both native and MSIL, allowing incremental migration to .NET
The C++/CLI features in Visual C++ "Whidbey" are an evolution of the Managed Extensionsfor Visual C++ .NET 2002 and 2003. CLR features are more tightly integratedwith existing C++ syntax and semantics, and provide a cohesive systems language formaking the most of the entire architecture.
Customer feedback directed the Visual C++ team to overhaul the original work withManaged Extensions to devise a more robust and more elegant syntax for Visual C++Whidbey.
Visual C++ for Devices is the only Microsoft solution for developing nativeapplications on Windows CE devices.
There is no official support for Visual C++ development for .NET applications using the Compact Frameworks. However, applications that you build using the /clr:safe option and that use only CLR and BCL features support by the Compact Frameworks will be able to run on CE devices.
In Visual C++ 6.0, Professional and Enterprise customers could get the Microsoft Assembler(MASM) by downloading VC++ 6.0 Processor Pack. Today MASM ships with VisualStudio .NET Professional and Enterprise as part of Visual C++. ML.EXE is locatedin the VC7\bin directory.
Yes. Visual C++ .NET can generate both managed and unmanaged applications and components.
VSIP Developer Community Center
Register as a VSIP affiliate (free) and download the VSIP SDK Extra which has thenewest MSCCI interface in it.
Absolutely, although this often means forgoing some of the great services providedby Windows and .NET developer platform, including Win32, MFC, the .NET Framework, DirectX, andinterop with Visual Basic and C#. An application using only pure ISO C++ functionality willgenerally be portable to any compiler and platform with an ISO C++ compliantcompiler.
Visual C++ allows you to take full advantage of .NET while at the same time givingyou the most efficient and easiest way to interoperate with existing code. Italso allows you to leverage your knowledge of C++ to .NET, rather than having to learna new language.
What you get is the combination of a language you know and love, a great managed-unmanaged interop story, complete .NET support, and .NET features found ONLY with Visual C++ (such as IJW, OpenMP, and templates).
Visual C++ "Whidbey" will offers a variety of high performance computing functionality. Of particular note are the following features:
ClassWizard has been replaced with several new wizards that individually provide morecontrol for adding member variables, message handlers, methods, properties, and events.
Currently, some IntelliSense information is contained in the .ncb file. Sometimes this file becomes corrupted, which means that IntelliSense no longer works. Simply delete this file, which will trigger a reparse of your project to generatea new .ncb file.
Symbol browsing was moved to the 'Find Symbol' feature in Visual Studio .NET 2002.Inheritance browsing and caller / callee browsing is not available in Visual Studio.NET 2002.
In Visual C++ "Whidbey", we're adding these features back. In addition, they willnow work without the need to create a BSC file or even compile your code.
To get a file of a non-standard extension viewed as a C++ file in the VS editor:
In VS .NET 2002, locate the registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\7.0\Languages\FileExtensions
In VS .NET 2003, locate the registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\7.1\Languages\FileExtensions
Search for the ".cpp" folder under "FileExtensions" and copy the value for the "(Default)" key.Add a new folder under "FileExtensions" for your desired extension and set the value of the "(Default)" key to the one you just copied.
To get C++ IntelliSense information on a file of a non-standard extension in the VS editor, you need to add the extension to the string in the following registry key:
For VS .NET 2002:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\7.0\Languages\Language Services\C/C++\NCB
Default C/C++ ExtensionsFor VS .NET 2003:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\7.1\Languages\Language Services\C/C++\NCB Default C/C++ Extensions
Open the .rc files in the editor using Open File (Ctrl-O). You can tile theeditor windows vertically and then drag and drop from one window to another. Alternately,you can create a new solution with both these projects and do the same operation throresource view window.
In Visual C++ "Whidbey", the compiler and IDE will take advantage of SMP machinesto compiler faster.
Yes, we will support unicode resource files in Visual C++ "Whidbey". You will just have to save the .rc file as Unicode and set the Character Set property of the project.
In general, Microsoft is committed to implementing the complete ISO C++ standard. However, Microsoft is particularly committed to delivering features that customersneed. As of yet, the demand for the export feature in Standard C++ has beenminimal. The complexity of the export feature is significant and customer feedbackhas shown that resources applied elsewhere now would solve more practical issues.Over time, we will continue to listen to customer requests and reevaluate whetherimplementing export is the best use of our resources.
Check out this article for a complete answer:
ATL Server is a new set of native C++ classes that allow developers to create high-performancenative code Web applications and XML Web services. Many of the classes can also beused in client applications or components that have a need for features such as performancemonitoring support, caching, and thread pooling.
Most MFC-based applications represent significant investments in development thatwould be thrown away if a rewrite to another language were undertaken. Microsoftrecommends that customers evaluate this cost against the much simpler route of extendingexisting MFC applications to take advantage of the .NET Framework. With relativelylittle work, an MFC application can be compiled wholly or partially to MSIL, and extendedwith new features using any variety of CLR languages, including C++ and C#.
In Whidbey and beyond MFC remains a core feature of the professional Visual C++ toolkit. While MFC is not always the best or most modern library for writing new applications,it continues to offer features that are not available elsewhere. Microsoft willcontinue to maintain and extend MFC to make it more secure and robust, and to enableit to interoperate better with newer technologies and libraries. For example,new classes and features in Whidbey enable existing MFC applications to be extendedand augmented with capabilities built on the Microsoft .NET Framework.
Microsoft has no plans to discontinue support for MFC. New features willin most cases enable MFC applications to better interoperate with the .NET Framework.
Currently there is no explicit library support for Windows Forms in MFC (Visual C++.NET 2002, 2003).
Visual C++ Whidbey will support Windows Forms interop with MFC, through the introductionof new MFC classes. You will be able to do the following in an MFC application:
MFC applications will be compiled easily with /clr compiler option and be able to take full advantage of the .NET Framework.
Yes, this is possible. It generally requires some work by the programmer, dueto known and documented issues with the compiler.
Read:
In Visual C++ Whidbey it will be much easier to recompile a MFC application with /clr. While ANSI-codepage MFC applications can be complied with /clr, we advise you to convert to UNICODE, because all .NET Framework strings are UNICODE based, and interop with a UNICODE MFC application becomes much easier. MFC /clr applications will use the DLL version of MFC and not static library version.
Yes, you can install Visual C++ .NET on a computer that is running Visual C++ 6.0and use both, system requirements permitting. Different versions of Visual Studio.NET will also coexist nicely on a single machine.
The functionality previously available in Professional and Enterprise versions ofthe individual language products is now available in the Professional and Enterpriseversions of Visual Studio .NET. In addition, a new Visual Studio .NET Enterprise ArchitectEdition is available with tools specifically designed for software architects buildingenterprise software, including Microsoft Visio Enterprise Architect Edition.
Visual C++ .NET 2003 is the current version. It ships as "Visual C++ .NET 2003Standard Edition", and with all editions of Visual Studio .NET 2003.
This version was formerly codenamed "Everett".
"Whidbey" is the code name for the next version of Visual C++. The "Whidbey" product will officially be named "Visual C++ 2005".
The version following Visual C++ .NET 2003 will be "Visual C++ 2005", and is currently codenamed "Whidbey". Whidbey will include several new features that enable more powerful and more elegant development of .NET CLR-based applications. Additional features include support for developing 64-bit applications, and a new C-Runtime Library (CRT) that helps write more secure applications.
These platforms are not supported at design time (Visual Studio will not install on these platforms). However, programs may be built using Visual C++ that will run on Windows 98 and Windows ME.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。