In the "To prepare..." paragraph it's now more generic, but I still see the following on the Web Forms page:
In the next release of Visual Studio, all the language products share the same Web technologies. Regardless of whether you choose Visual Basic or Visual C++®, the product functionality is the same. Therefore, you can choose your favorite language to build Web Forms further increasing productivity.
"Regardless of whether you choose..." without mentioning VFP implies that it is not a valid choice.
>This was an oversight. I spoke to the person who wrote these pages and he apologizes for any confusion and promises to fix this paragraph to accurately reflect the fact that all of the Visual Studio languages make great COM components.
>
>>Will somebody finally buy a f*cking clue at MSDN, or feel free to buy them a f*cking clue and mail it to them, about VFP's ability to operate in the middle tier? This is from the new Web Services information on the next version of Visual Studio.
>>
>>Getting Ready for Web Services
>>To prepare for using Web Services, we recommend that you build your application on a multi-tier architecture. The recommended approach for new application development is to author middle-tier business components in Visual Basic 6.0 or Visual C++ 6.0 and to expose them as COM components. Developers will be able to easily convert these middle-tier components to Web Services.
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement